On Friday, 24 February 2017 17.45.28 WET Jean-Marc Lasgouttes wrote: > Hi there, > > A good subject before the week-end: what do we need to do before > declaring feature freeze for 2.3? Personally I have finished a cycle or > breaking/fixing the math editor and would like to refrain from doing new > big architectural changes. I only have two or three patches pending, > plus of course all the bugs that Guillaume keeps finding. > > Who has Work In Progress that should go to 2.3? How long do we need? > > JMarc
The only obvious itch that I would like to scratch is the xdg-open patch that I have to redo on each version to configure.py. A possible solution is to have specific component that is loaded for each platform for the programs that read and edit the supported document formats. That would allow me to have a simply file that configures the checkViewer without needing to patch it in a tedious and error prone process. Now regarding the other issue at hand and looking into history we have that: 2.2.0 -> 2016.05 2.1.0 -> 2014.04 2.0.0 -> 2011.04 1.6.0 -> 2008.11 1.5.0 -> 2007.07 1.4.0 -> 2006.03 First the obvious conclusion, those number are completely arbitrary. Each of those versions has been a major version on its own. And as usual I propose to go the way of gcc (not necessarily dropping the first .0 ;-) ). And use simply a major number and a minor number for the version. An yearly version on the other hand seems a good compromise. Again gcc is a good model. The next obvious question is who is the voluntary for the release manager role. A good/nice weekend for everyone, :-) -- José Abílio
