Sphinx: 2.0.0 release plan

Created on 14 Jan 2019  路  15Comments  路  Source: sphinx-doc/sphinx

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

task

Most helpful comment

done.
Thank you all for your work!

All 15 comments

could #5959 be marked too ?

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

take your time, and thank you : )

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.

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.

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,

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?

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

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.

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

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?

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?

I start packaging from now on!

done.
Thank you all for your work!

Was this page helpful?
0 / 5 - 0 ratings