starred/cypht

Fork 0

mirror of https://github.com/cypht-org/cypht.git synced 2026-04-25 04:56:03 +03:00

[GH-ISSUE #1624] 🎂 [RELEASE] Cypht 2.5.0 #687

New issue

Closed

opened 2026-02-25 21:35:40 +03:00 by kerem · 6 comments

kerem commented

2026-02-25 21:35:40 +03:00

Owner

Originally created by @marclaporte on GitHub (Aug 21, 2025).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/1624

Originally assigned to: @Shadow243, @christer77, @mercihabam, @Baraka24 on GitHub.

🎂 RELEASE

We had a good release cadence:

2024-04-30 2.0.0
2024-05-20 2.0.1
2024-06-18 2.1.0
2024-08-15 2.2.0
2024-08-29 2.3.0
2024-09-16 2.4.0

And then we lost it. It has been 11 months since 2.4.0: https://github.com/cypht-org/cypht/releases/tag/v2.4.0

I know I have been talking about the release of Cypht 2.5.0 for many months in https://gitter.im/cypht-org/community and in https://github.com/cypht-org/cypht/wiki/Monthly-Community-Meetings

https://openhub.net/p/cypht/commits/summary reports 656 commits by 33 contributors modifying 349 files in the last 12 months. So activity level is very high (given the overall size of the project) but 11 months is way too long. It should be 2-3 months between stable releases. For at least 6 months, I thought we could release 2.5.0 within 4-5 weeks, but I was mistaken. There were bugs and yet more bugs to fix. But now, I think we really are 4-5 weeks away. I sure hope to be right this time.

Since 2.4.x, Cypht master has undergone refactoring of major parts by two devs (Merci Jacob and then Victor Emanouilov to address some consequences of previous refactor). These efforts are to build a better long term future but they cause side effects, and many small subsequent adjustments. We also added many features (and thus more bugs).

We have done significant work on Tiki-Cypht interoperability: https://doc.tiki.org/Cypht
So how to evolve Cypht as a standalone app while making it easier to integrate within Tiki, and eventually other apps. For example, I could imagine one day integrating Cypht within Dolibarr.

Beyond Merci and Victor (mentioned above), thank you to Steven, Josaphat, Baraka and Christer for the many contributions in the last 12 months.

For the foreseeable future, all PRs are to be reviewed by @kroky.

So now, we need Cypht master to be at least as stable as 1.4.x and 2.4.x. Then

we spin out 2.5.0 (from master)
use Cypht 2.5.x for Tiki 29.x, 28.x and 27.x LTS (so will need to align a lot of code in Tiki)

From then on, we get back to stable releases every few months (2.6.0, 2.7.0, etc.)

Somewhere in 2026 (Q3 or Q4), we for Cypht 3.0

Originally created by @marclaporte on GitHub (Aug 21, 2025). Original GitHub issue: https://github.com/cypht-org/cypht/issues/1624 Originally assigned to: @Shadow243, @christer77, @mercihabam, @Baraka24 on GitHub.    ## 🎂 RELEASE  We had a good release cadence: - 2024-04-30 2.0.0 - 2024-05-20 2.0.1 - 2024-06-18 2.1.0 - 2024-08-15 2.2.0 - 2024-08-29 2.3.0 - 2024-09-16 2.4.0 And then we lost it. It has been 11 months since 2.4.0: https://github.com/cypht-org/cypht/releases/tag/v2.4.0 I know I have been talking about the release of Cypht 2.5.0 for many months in https://gitter.im/cypht-org/community and in https://github.com/cypht-org/cypht/wiki/Monthly-Community-Meetings https://openhub.net/p/cypht/commits/summary reports 656 commits by 33 contributors modifying 349 files in the last 12 months. So activity level is very high (given the overall size of the project) but 11 months is way too long. It should be 2-3 months between stable releases. For at least 6 months, I thought we could release 2.5.0 within 4-5 weeks, but I was mistaken. There were bugs and yet more bugs to fix. But now, I think we really are 4-5 weeks away. I sure hope to be right this time. Since 2.4.x, Cypht master has undergone refactoring of major parts by two devs (Merci Jacob and then Victor Emanouilov to address some consequences of previous refactor). These efforts are to build a better long term future but they cause side effects, and many small subsequent adjustments. We also added many features (and thus more bugs). We have done significant work on Tiki-Cypht interoperability: https://doc.tiki.org/Cypht So how to evolve Cypht as a standalone app while making it easier to integrate within Tiki, and eventually other apps. For example, I could imagine one day integrating Cypht within Dolibarr. Beyond Merci and Victor (mentioned above), thank you to Steven, Josaphat, Baraka and Christer for the many contributions in the last 12 months. - https://github.com/cypht-org/cypht/graphs/contributors?from=8%2F17%2F2024 - https://openhub.net/p/cypht/contributors?query=&time_span=&sort=twelve_month_commits For the foreseeable future, all PRs are to be reviewed by @kroky. So now, we need Cypht master to be at least as stable as 1.4.x and 2.4.x. Then - we spin out 2.5.0 (from master) - use Cypht 2.5.x for Tiki 29.x, 28.x and 27.x LTS (so will need to align a lot of code in Tiki) From then on, we get back to stable releases every few months (2.6.0, 2.7.0, etc.) Somewhere in 2026 (Q3 or Q4), we for Cypht 3.0

kerem

2026-02-25 21:35:40 +03:00

closed this issue
added the
release
label

kerem commented

2026-02-25 21:35:41 +03:00

Author

Owner

@marclaporte commented on GitHub (Aug 27, 2025):

I created a 2.5 milestone and added some blockers and notable issues and PRs:
https://github.com/cypht-org/cypht/milestone/6

@marclaporte commented on GitHub (Aug 27, 2025): I created a 2.5 milestone and added some blockers and notable issues and PRs: https://github.com/cypht-org/cypht/milestone/6

kerem commented

2026-02-25 21:35:41 +03:00

Author

Owner

@marclaporte commented on GitHub (Oct 1, 2025):

I think we have solved all the blockers: https://github.com/cypht-org/cypht/milestone/6

The big blocker was: https://github.com/cypht-org/cypht/pull/1635

So now, let's polish up!

@marclaporte commented on GitHub (Oct 1, 2025): I think we have solved all the blockers: https://github.com/cypht-org/cypht/milestone/6 The big blocker was: https://github.com/cypht-org/cypht/pull/1635 So now, let's polish up!

kerem commented

2026-02-25 21:35:41 +03:00

Author

Owner

@marclaporte commented on GitHub (Oct 1, 2025):

@ulfgebhardt is doing one more round of his thorough testing. Once these issues are solved, let's package 2.5.0!

@marclaporte commented on GitHub (Oct 1, 2025): @ulfgebhardt is doing one more round of his thorough testing. Once these issues are solved, let's package 2.5.0!

kerem commented

2026-02-25 21:35:41 +03:00

Author

Owner

@marclaporte commented on GitHub (Oct 21, 2025):

@Shadow243 Today, we identified a few minor bugs, but no blockers for 2.5.0

Let's release 2.5.0 somewhere between 2025-10-27 and 2025-10-31 (your choice).

And after, we'll be ready for quick fixes 2.5.1, 2.5.2, ...

Please coordinate with @kroky

@marclaporte commented on GitHub (Oct 21, 2025): @Shadow243 Today, we identified a few minor bugs, but no blockers for 2.5.0 Let's release 2.5.0 somewhere between 2025-10-27 and 2025-10-31 (your choice). And after, we'll be ready for quick fixes 2.5.1, 2.5.2, ... Please coordinate with @kroky

kerem commented

2026-02-25 21:35:41 +03:00

Author

Owner

@marclaporte commented on GitHub (Oct 30, 2025):

Congrats to all contributors!

https://github.com/cypht-org/cypht/releases/tag/v2.5.0

Now let's get Cypht 2.5.x in Tiki 29.x (I expect a lot of backports of Tiki-Cypht code)

@marclaporte commented on GitHub (Oct 30, 2025): Congrats to all contributors! https://github.com/cypht-org/cypht/releases/tag/v2.5.0 Now let's get Cypht 2.5.x in Tiki 29.x (I expect a lot of backports of Tiki-Cypht code)

kerem commented

2026-02-25 21:35:41 +03:00

Author

Owner

@Shadow243 commented on GitHub (Oct 30, 2025):

Now let's get Cypht 2.5.x in Tiki 29.x (I expect a lot of backports of Tiki-Cypht code)

The PR is ready for review 8914

@Shadow243 commented on GitHub (Oct 30, 2025): > Now let's get Cypht 2.5.x in Tiki 29.x (I expect a lot of backports of Tiki-Cypht code) The PR is ready for review [8914](https://gitlab.com/tikiwiki/tiki/-/merge_requests/8914)