starred/cypht
1
0
Fork 0
mirror of https://github.com/cypht-org/cypht.git synced 2026-04-25 13:05:53 +03:00
Code Issues 137 Projects Releases Packages Wiki Activity

[GH-ISSUE #879] Release Cypht 2.0 #507

New issue
Closed
opened 2026-02-25 21:35:12 +03:00 by kerem · 21 comments
kerem commented 2026-02-25 21:35:12 +03:00
Owner
Copy link

Originally created by @marclaporte on GitHub (Jan 31, 2024).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/879

After 1.4.x, we will go to 2.0 because there are many big changes.

The main ones:

So let's clean this out: https://github.com/cypht-org/cypht/pulls, stabilize and release!

Originally created by @marclaporte on GitHub (Jan 31, 2024). Original GitHub issue: https://github.com/cypht-org/cypht/issues/879 After 1.4.x, we will go to 2.0 because there are many big changes. The main ones: - https://github.com/cypht-org/cypht/pull/828 - https://github.com/cypht-org/cypht/pull/625 - https://github.com/cypht-org/cypht/pull/855 So let's clean this out: https://github.com/cypht-org/cypht/pulls, stabilize and release!
kerem closed this issue 2026-02-25 21:35:12 +03:00
kerem commented 2026-02-25 21:35:12 +03:00
Author
Owner
Copy link

@marclaporte commented on GitHub (Mar 8, 2024):

Two blockers for Cypht 2.0:

<!-- gh-comment-id:1985932365 --> @marclaporte commented on GitHub (Mar 8, 2024): Two blockers for Cypht 2.0: - https://github.com/cypht-org/cypht/pull/855 - https://github.com/cypht-org/cypht/pull/921
kerem commented 2026-02-25 21:35:12 +03:00
Author
Owner
Copy link

@marclaporte commented on GitHub (Mar 22, 2024):

Also, we plan to have JMAP working for the basics: https://github.com/cypht-org/cypht/issues/180

And some more advanced features will be for later (ex.: Cypht 2.1)
https://github.com/cypht-org/cypht/issues/931

<!-- gh-comment-id:2014873213 --> @marclaporte commented on GitHub (Mar 22, 2024): Also, we plan to have JMAP working for the basics: https://github.com/cypht-org/cypht/issues/180 And some more advanced features will be for later (ex.: Cypht 2.1) https://github.com/cypht-org/cypht/issues/931
kerem commented 2026-02-25 21:35:12 +03:00
Author
Owner
Copy link

@marclaporte commented on GitHub (Mar 30, 2024):

The milestones are done except for JMAP: https://github.com/cypht-org/cypht/milestone/2

We have 4 non-draft MRs that it would make sense to add:
https://github.com/cypht-org/cypht/pulls?q=is%3Apr+is%3Aopen+draft%3Afalse

<!-- gh-comment-id:2028378200 --> @marclaporte commented on GitHub (Mar 30, 2024): The milestones are done except for JMAP: https://github.com/cypht-org/cypht/milestone/2 We have 4 non-draft MRs that it would make sense to add: https://github.com/cypht-org/cypht/pulls?q=is%3Apr+is%3Aopen+draft%3Afalse
kerem commented 2026-02-25 21:35:12 +03:00
Author
Owner
Copy link

@ConnectGrid commented on GitHub (Apr 3, 2024):

This is exciting! Thanks for your hard work on this!

<!-- gh-comment-id:2033517464 --> @ConnectGrid commented on GitHub (Apr 3, 2024): This is exciting! Thanks for your hard work on this!
kerem commented 2026-02-25 21:35:12 +03:00
Author
Owner
Copy link

@marclaporte commented on GitHub (Apr 13, 2024):

We have 6 non-draft MRs that it would make sense to add:
https://github.com/cypht-org/cypht/pulls?q=is%3Apr+is%3Aopen+draft%3Afalse

<!-- gh-comment-id:2053787126 --> @marclaporte commented on GitHub (Apr 13, 2024): We have 6 non-draft MRs that it would make sense to add: https://github.com/cypht-org/cypht/pulls?q=is%3Apr+is%3Aopen+draft%3Afalse
kerem commented 2026-02-25 21:35:12 +03:00
Author
Owner
Copy link

@marclaporte commented on GitHub (Apr 15, 2024):

@josaphatim @kroky Let's clean this list and release 2.0!
https://github.com/cypht-org/cypht/pulls?q=is%3Apr+is%3Aopen+draft%3Afalse

<!-- gh-comment-id:2057955443 --> @marclaporte commented on GitHub (Apr 15, 2024): @josaphatim @kroky Let's clean this list and release 2.0! https://github.com/cypht-org/cypht/pulls?q=is%3Apr+is%3Aopen+draft%3Afalse
kerem commented 2026-02-25 21:35:12 +03:00
Author
Owner
Copy link

@kroky commented on GitHub (Apr 16, 2024):

@josaphatim let me know if you need help on any of the items.

<!-- gh-comment-id:2059159443 --> @kroky commented on GitHub (Apr 16, 2024): @josaphatim let me know if you need help on any of the items.
kerem commented 2026-02-25 21:35:12 +03:00
Author
Owner
Copy link

@marclaporte commented on GitHub (Apr 25, 2024):

The remaining PRs are not blockers so we can release Cypht 2.0 any time!

<!-- gh-comment-id:2077115947 --> @marclaporte commented on GitHub (Apr 25, 2024): The remaining PRs are not blockers so we can release Cypht 2.0 any time!
kerem commented 2026-02-25 21:35:12 +03:00
Author
Owner
Copy link

@Baraka24 commented on GitHub (Apr 25, 2024):

The remaining PRs are not blockers so we can release Cypht 2.0 any time!

We are now experiencing Cypht 2.0 for good notes.

<!-- gh-comment-id:2078043337 --> @Baraka24 commented on GitHub (Apr 25, 2024): > The remaining PRs are not blockers so we can release Cypht 2.0 any time! We are now experiencing Cypht 2.0 for good notes.
kerem commented 2026-02-25 21:35:12 +03:00
Author
Owner
Copy link

@marclaporte commented on GitHub (Apr 30, 2024):

I did a round of testing on Cypht master, and I can tell you there are a huge number of "paper cut bugs"
https://en.wikipedia.org/wiki/Paper_cut_bug

Why it is buggy:

  • We added tons of new features since 1.4.x
  • Major changes like moving to Bootstrap 5 and new account manage back-end and front-end
  • Most recently active developers are new to the code base
  • We don't yet have a good dev/testing/qa feeback loop (we'll work on this later)

So 2.0 will be buggy. How will we stabilize things in the coming months with 2.1, 2.2, 2.3, etc.?

  • 6 to 8 developers will be assigned to work part time on Cypht for at least the next 8 months. They are pretty new to Cypht, so it will be a learning experience, and to improve our development capacity for future versions.
  • This team will fix all appropriately reported paper cut bugs, and fix the non-paper cut bugs according to priorities (Is it easy to fix, is it a commonly-used feature, etc.)
<!-- gh-comment-id:2084098307 --> @marclaporte commented on GitHub (Apr 30, 2024): I did a round of testing on Cypht master, and I can tell you there are a huge number of "paper cut bugs" https://en.wikipedia.org/wiki/Paper_cut_bug Why it is buggy: - We added tons of new features since 1.4.x - Major changes like moving to Bootstrap 5 and new account manage back-end and front-end - Most recently active developers are new to the code base - We don't yet have a good dev/testing/qa feeback loop (we'll work on this later) So 2.0 will be buggy. How will we stabilize things in the coming months with 2.1, 2.2, 2.3, etc.? - 6 to 8 developers will be assigned to work part time on Cypht for at least the next 8 months. They are pretty new to Cypht, so it will be a learning experience, and to improve our development capacity for future versions. - This team **will fix all appropriately reported paper cut bugs**, and fix the non-paper cut bugs according to priorities (Is it easy to fix, is it a commonly-used feature, etc.)
kerem commented 2026-02-25 21:35:12 +03:00
Author
Owner
Copy link

@kroky commented on GitHub (Apr 30, 2024):

Cypht 2.0 is out:
https://github.com/cypht-org/cypht/releases/tag/v2.0.0

Commit messages matter, wow - I'd never be able to generate such a nice changelog text. Nicely done mentioning all the contributors as well.

@marclaporte, feel free to describe the bigger changes in more detail on the top of the release message.

<!-- gh-comment-id:2087372066 --> @kroky commented on GitHub (Apr 30, 2024): Cypht 2.0 is out: https://github.com/cypht-org/cypht/releases/tag/v2.0.0 Commit messages matter, wow - I'd never be able to generate such a nice changelog text. Nicely done mentioning all the contributors as well. @marclaporte, feel free to describe the bigger changes in more detail on the top of the release message.
kerem commented 2026-02-25 21:35:12 +03:00
Author
Owner
Copy link

@marclaporte commented on GitHub (Apr 30, 2024):

@marclaporte, feel free to describe the bigger changes in more detail on the top of the release message.

Done

<!-- gh-comment-id:2087683800 --> @marclaporte commented on GitHub (Apr 30, 2024): > @marclaporte, feel free to describe the bigger changes in more detail on the top of the release message. Done
kerem commented 2026-02-25 21:35:12 +03:00
Author
Owner
Copy link

@marclaporte commented on GitHub (Apr 30, 2024):

Commit messages matter, wow - I'd never be able to generate such a nice changelog text. Nicely done mentioning all the contributors as well.

Indeed! Which script does this?

<!-- gh-comment-id:2087684061 --> @marclaporte commented on GitHub (Apr 30, 2024): > Commit messages matter, wow - I'd never be able to generate such a nice changelog text. Nicely done mentioning all the contributors as well. Indeed! Which script does this?
kerem commented 2026-02-25 21:35:12 +03:00
Author
Owner
Copy link

@tarasis commented on GitHub (May 1, 2024):

It’s been Interesting to follow the release, and I hope to be able to contribute in future at least for CSS (I know little to no php).

for the release notes, it was great that everyone was credited. it would be useful though to separate fixes from features.

I know it’s more effort (I’d be happy to do it if you eanted), but as a user it’s much more helpful to be able to look and seen the new features, then the fixes rather than have them interspersed

<!-- gh-comment-id:2087927613 --> @tarasis commented on GitHub (May 1, 2024): It’s been Interesting to follow the release, and I hope to be able to contribute in future at least for CSS (I know little to no php). for the release notes, it was great that everyone was credited. it would be useful though to separate fixes from features. I know it’s more effort (I’d be happy to do it if you eanted), but as a user it’s much more helpful to be able to look and seen the new features, then the fixes rather than have them interspersed
kerem commented 2026-02-25 21:35:12 +03:00
Author
Owner
Copy link

@marclaporte commented on GitHub (May 1, 2024):

@tarasis Thank you for the kind words.

  1. We have tons of CSS work to do given the move to Bootstrap 5. Your help is most appreciated.
  2. I improved https://github.com/cypht-org/cypht/releases/tag/v2.0.0 to have a section for "Main changes". You are welcome to separate fixes from features, but I warn you that it's a lot of work. And there are ambiguous one. Ex.: A fix on a recently added feature. Is it a fix? Or just part of the new feature?
<!-- gh-comment-id:2087971813 --> @marclaporte commented on GitHub (May 1, 2024): @tarasis Thank you for the kind words. 1. We have tons of CSS work to do given the move to Bootstrap 5. Your help is most appreciated. 2. I improved https://github.com/cypht-org/cypht/releases/tag/v2.0.0 to have a section for "Main changes". You are welcome to separate fixes from features, but I warn you that it's a lot of work. And there are ambiguous one. Ex.: A fix on a recently added feature. Is it a fix? Or just part of the new feature?
kerem commented 2026-02-25 21:35:12 +03:00
Author
Owner
Copy link

@kroky commented on GitHub (May 1, 2024):

It is just a github feature aggregating all commit messages from previous tag. I think if developers add a bit of semantics to the commit messages like [ENH], [FEAT] and [FIX], it will be quite easy to aggregate the release notes by feature, enhancement or a fix.

<!-- gh-comment-id:2088016620 --> @kroky commented on GitHub (May 1, 2024): It is just a github feature aggregating all commit messages from previous tag. I think if developers add a bit of semantics to the commit messages like [ENH], [FEAT] and [FIX], it will be quite easy to aggregate the release notes by feature, enhancement or a fix.
kerem commented 2026-02-25 21:35:12 +03:00
Author
Owner
Copy link

@marclaporte commented on GitHub (May 1, 2024):

I hope to be able to contribute in future at least for CSS

@tarasis we could use some help here: https://github.com/cypht-org/cypht/issues/993

<!-- gh-comment-id:2088684216 --> @marclaporte commented on GitHub (May 1, 2024): > I hope to be able to contribute in future at least for CSS @tarasis we could use some help here: https://github.com/cypht-org/cypht/issues/993
kerem commented 2026-02-25 21:35:12 +03:00
Author
Owner
Copy link

@marclaporte commented on GitHub (May 5, 2024):

So 2.0 will be buggy.

I just officialized that Cypht 1.4.x is now an LTS version so end users don't have to rush to upgrade:
https://github.com/cypht-org/cypht/wiki/Lifecycle

<!-- gh-comment-id:2094964527 --> @marclaporte commented on GitHub (May 5, 2024): > So 2.0 will be buggy. I just officialized that Cypht 1.4.x is now an LTS version so end users don't have to rush to upgrade: https://github.com/cypht-org/cypht/wiki/Lifecycle
kerem commented 2026-02-25 21:35:12 +03:00
Author
Owner
Copy link

@marclaporte commented on GitHub (May 20, 2024):

Cypht 2.0.1 with a bunch of bug fixes: https://github.com/cypht-org/cypht/releases/tag/v2.0.1

<!-- gh-comment-id:2121357221 --> @marclaporte commented on GitHub (May 20, 2024): Cypht 2.0.1 with a bunch of bug fixes: https://github.com/cypht-org/cypht/releases/tag/v2.0.1
kerem commented 2026-02-25 21:35:12 +03:00
Author
Owner
Copy link

@marclaporte commented on GitHub (Aug 15, 2024):

Cypht 2.2.0: https://github.com/cypht-org/cypht/releases/tag/v2.2.0

<!-- gh-comment-id:2291121450 --> @marclaporte commented on GitHub (Aug 15, 2024): Cypht 2.2.0: https://github.com/cypht-org/cypht/releases/tag/v2.2.0
kerem commented 2026-02-25 21:35:12 +03:00
Author
Owner
Copy link

@marclaporte commented on GitHub (Sep 9, 2024):

Cypht 2.3.0: https://github.com/cypht-org/cypht/releases/tag/v2.3.0

<!-- gh-comment-id:2339337901 --> @marclaporte commented on GitHub (Sep 9, 2024): Cypht 2.3.0: https://github.com/cypht-org/cypht/releases/tag/v2.3.0
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
2.x
mta-sts-implementation
feat-compose-backspace-delete-recipients
release-2.5.1
add-tls3-support
1.4.x
enforce-coverage
release-2.4.2
strip_dns_prefetch_tags
fix_nightly_build
pr-title-validation-update
review-sent-email
revert-1339-fixed-tags-display
revert-1061-rem-cram-md5
sys-messages-revamp
revert-685-fixed-str-pos-warning-when-no-to
revert-590-empty-settings
release-1.3.0
revert-471-draft-add-warning
revert-454-feature/server-list-by-uniqid
php7.4-support
release-1.2.0
remove-mobile-media-queries
release-1.1.0
release-1.0.0
v2.7.0
v2.6.0
v2.5.1
v2.5.0
v1.4.7
v2.4.2
v2.4.1
v1.4.6
v1.4.5
v2.4.0
v2.3.0
v2.2.0
v1.4.4
v2.1.0
v2.0.1
v1.4.3
v2.0.0
v1.4.2
v1.4.1
v1.4.0
v1.3.0
v1.3.0-rc3
v1.3.0-rc2
v1.3.0-rc1
v1.1.0
v1.1.0-rc4
v1.1.0-rc3
v1.1.0-rc2
v1.1.0-rc1
v1.0.0
v1.0.0-rc8
v1.0.0-rc7
v1.0.0-rc6
v1.0.0-rc5
v1.0.0-rc4
v1.0.0-rc3
v1.0.0-rc2
v1.0.0-rc1
Labels
Clear labels   
2fa

   
I18N

   
PGP

   
Security

   
Security

   
account

   
advanced_search

   
advanced_search

   
announcement

   
api_login

   
authentication

   
awaiting feedback

   
blocker

   
bug

   
bug

   
bug

   
calendar

   
config

   
contacts

   
core

   
core

   
devops

   
docker

   
docs

   
duplicate

   
dynamic_login

   
enhancement

   
epic

   
feature

   
feeds

   
framework

   
github

   
github

   
gmail_contacts

   
good first issue

   
help wanted

   
history

   
history

   
imap

   
imap_folders

   
inline_message

   
installation

   
keyboard_shortcuts

   
keyboard_shortcuts

   
ldap_contacts

   
mobile

   
need-ssh-access

   
new module set

   
nux

   
pop3

   
profiles

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
refactor

   
release

   
research

   
saved_searches

   
smtp

   
strategic

   
tags

   
tests

   
themes

   
website

   
wordpress
No labels
2fa
I18N
PGP
Security
Security
account
advanced_search
advanced_search
announcement
api_login
authentication
awaiting feedback
blocker
bug
bug
bug
calendar
config
contacts
core
core
devops
docker
docs
duplicate
dynamic_login
enhancement
epic
feature
feeds
framework
github
github
gmail_contacts
good first issue
help wanted
history
history
imap
imap_folders
inline_message
installation
keyboard_shortcuts
keyboard_shortcuts
ldap_contacts
mobile
need-ssh-access
new module set
nux
pop3
profiles
pull-request
question
refactor
release
research
saved_searches
smtp
strategic
tags
tests
themes
website
wordpress
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/cypht#507
No description provided.