I would let Python 2.7 die before
https://pythonclock.org/
2 months is not so long...

I think we could create this branch right now and start adding things for Py3.5+ only but it's only my opinion :)

@ppkt
Yes, I would have no problem to create a maintenance branch release for the 2.9.x series and adding new feature in the master branch (which would be the upcoming 3.0.0 release). I would love to start for the next major release. 😉

Of course, there are other ways to do it, like creating a dedicated 3.0.0-pre release branch, adding stuff there and then merge it to master when it's "ready".

Personally, I would prefer the first method (create a 2.9.x maintenance branch, master will be the upcoming 3.0.0 release). I think, it makes it a little bit easier.

Currently, we have a problem with Travis. For some reason, it doesn't finish its task and blocks our pull request(s). 😞 I'm not sure how to fix it...

@tomschr agree, I think separate branches for 2.9.x and 3.0.x would be great (so we could consider master as "stable" branch).

@ppkt Whatever works is fine for me. 😉 Let's see what @scls19fr has to say about that.

What would you prefer? Would you wait til January (as indicated in some other comment)? Or can we start right away? 😉

Submitting PR is always opened and discussion can occur on these PR.
We will see in January for merging them to master.
Maybe we should have a tag WIP (and/or Release 3.x.y) to just remember not to merge them.
I don't think we have enough human ressources for managing several branches (even if here several means 2 😄 )
In January we will create a 2.9.x branch before merging 3.x features to master.
So our 3.x.y development will be in master and we will have a 2.9.x branch if we need to go back (hoping that we won't need to do it)

Maybe we should have a tag WIP (and/or Release 3.x.y) to just remember not to merge them.

That would be one way. Another way would be to open PRs as "Draft" . If you do that, merging is disabled unless you change "Draft" to "Ready for review".

I never used previously PR as Draft but it seems to be a good idea as it will be a place to have discussion about changes we expect to be merged for 3.x.y.

@scls19fr, @ppkt any new ideas how to proceed? Should we create a 2.9.1 release before we switch to 3.0.0?

For the major 3 release, I've created the release 3 project. Would it make sense to create something similar for the 2.9.1 release?

As we are preparing a 2.10.0 in #237 soon, this issue is related to it.

@python-semver/reviewers
Once 2.10.0 is released, I would suggest to work on the semver3 after. IMHO, that gives us the chance to remove all the old stuff of Python2 and focus on one code base.

Any concerns or objections about this idea? 😉

I guess, this is solved by #246