On Tuesday, January 14, 2020 at 8:01:18 PM UTC-5, Michael Orlitzky wrote: > > > 1. Branch off the 9.0 release > 2. Drop compatibility in 9.1 > 3. Proceed as normal > 4. If there are any major bugs found in 9.1, backport the fix to > the 9.0 branch, and release a 9.0.1 that supports python-2.x. > > Mathematical bug fixes that merge clean and pass the tests could also > make the cut, but ideally step (4) would require little work. This would > buy users a few more months of python2 compatibility, and lets the rest > of us move on. >
I agree that there needs to be a 9.0 maintenance branch – if only to be the designated upstream for distributors that want to keep maintaining a py2 version of sage. > The main downside is that this relies solely on the release manager to > merge bugfix tickets twice, into both release branches. So if he thinks > this is a waste of time (understandable), then it's a non-starter. > The maintenance branch could also be maintained by another developer. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/c232c89b-b45a-4465-a9e9-03ca8a240c6d%40googlegroups.com.
