Skip to content
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

2.0.0 release plan #5950

Closed
tk0miya opened this issue Jan 14, 2019 · 15 comments
Closed

2.0.0 release plan #5950

tk0miya opened this issue Jan 14, 2019 · 15 comments
Milestone

Comments

@tk0miya
Copy link
Member

tk0miya commented Jan 14, 2019

Hi maintainers,

Sphinx-1.8.0 was released at Sep 13, 2018. As discussed in #4484, and according to our time based release policy, this March is time to release. What do you think about this schedule?

  • mid or end of February: beta release
  • mid or end of March: final release

Note: issues marked as 2.0.0: https://github.com/sphinx-doc/sphinx/milestone/33

@jschueller
Copy link
Contributor

could #5959 be marked too ?

@tk0miya
Copy link
Member Author

tk0miya commented Jan 18, 2019

@jschueller Please wait a little while more. I'll take a look later. I'm mainly working for sphinx at weekend now.

@jschueller
Copy link
Contributor

take your time, and thank you : )

@tk0miya
Copy link
Member Author

tk0miya commented Jan 24, 2019

mid or end of February: beta release

I'd forgotten to mention about feature freeze. After the beta release, only bug fixes are allowed to the release. Any new features should be moved to next minor release; 2.1.x.

So please post a PR until the beta release if you have some idea or patches.

@tk0miya tk0miya added this to the 2.0.0 milestone Feb 9, 2019
@tk0miya
Copy link
Member Author

tk0miya commented Feb 9, 2019

Hello maintainers,

  • mid or end of February: beta release

February has come! As proposed, I'd like to ship beta release soon. How about your work? If there are no problems, I will do it on next weekend (Feb 16th or 17th).
Please let me know if you're still in work. we can postpone the release a week or more.

@tk0miya
Copy link
Member Author

tk0miya commented Feb 16, 2019

This weekend is X-DAY. How are you? If no objection, I'll release a bete package within a day. Please let me know your status.
Thanks,

@tk0miya
Copy link
Member Author

tk0miya commented Feb 17, 2019

I'd like to add #6040 to 2.0 release. It must be useful for python developers. But it is still in review. As my proposal, is it possible to merge it after the beta release. And it will be released as beta2. What do you think?

@tk0miya
Copy link
Member Author

tk0miya commented Feb 17, 2019

I'm starting to release the beta package from now on.

@tk0miya
Copy link
Member Author

tk0miya commented Feb 17, 2019

2.0.0b1 is released now. Thank you for all your work!
https://pypi.org/project/Sphinx/2.0.0b1/

From now on, 2.0 branch is used for 2.0.0 final release. Please don't merge new features and breaking changes to this branch. Only stable changes are allowed.
For improvement, please use master branch. It is used for 2.1.0.

Note: I noticed there are no branches for 3.0. So any breaking changes are not allowed at this moment.

@tk0miya
Copy link
Member Author

tk0miya commented Feb 26, 2019

Note: I give up to merge #6040 into 2.0 branch because it needs more review and discussion.

@tk0miya
Copy link
Member Author

tk0miya commented Mar 18, 2019

I will release 2.0.0b2 within a day. And I will release 2.0.0 final within a week if no critical bugs reported.
Any comment?

@tk0miya
Copy link
Member Author

tk0miya commented Mar 20, 2019

@tk0miya
Copy link
Member Author

tk0miya commented Mar 27, 2019

I will release 2.0.0b2 within a day. And I will release 2.0.0 final within a week if no critical bugs reported.

I'll do it in within 24hrs. Do you have any blockers?

@tk0miya
Copy link
Member Author

tk0miya commented Mar 28, 2019

I start packaging from now on!

@tk0miya
Copy link
Member Author

tk0miya commented Mar 28, 2019

done.
Thank you all for your work!

@tk0miya tk0miya closed this as completed Mar 28, 2019
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants