-
-
Notifications
You must be signed in to change notification settings - Fork 170
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Release 5.0.0 #429
Comments
I created #430 to document how to go about new releases. |
We do not need to merge this, but I want to see if anything breaks before a new icalendar release is out. See collective/icalendar#429
I have run the core Plone 6.0 tests with a checkout of |
Releasing ... |
Documentation is up-to-date. |
Uhh.... |
A new release v5.0.0 has been made and can be used now. |
Thanks a lot! Wonderful job! |
@geier - let's discuss the next release of the project and what is necessary for it.
I think, I would release
v5.0.0
as we have some nice new features with it and the changelog is growing.I do not think that holding the changes back will benefit people who are not installing the alpha release
5.0.0a1
either way because how would you know? I would't check all my 100 dependencies for alpha releases.I am happy to get into a fast-release cycle eventually implementing pushing new releases automatedly (other issue/PR).
What are your (everyone's) thoughts on this? Are there any concerns?
Related:
The text was updated successfully, but these errors were encountered: