Mentioning 3.0: After the release of version 2.5. I would prefer a complete overhaul of the API to get rid of some old stuff. This would the break compatibility but make new projects more effective. Hence we would then have the old 2.x branch - on which we would still have bugfixes and the new 3.x branch with a clean API. How about that?
But let's now concentrate on getting the release done first. Regards, Rainer -----original message----- from: Jan Glaubitz <[email protected]> to: dev <[email protected]> subject: Re: [VOTE] Releasing version 2.5.0 Hi Rainer, I’m using the 2.5 snapshot in production so its an easy +1 from me. But one thing: why not remove all that deprecated stuff and call it 3.0? - jan > Am 14.02.2020 um 10:25 schrieb Rainer Döbele <[email protected]>: > > Hello everybody, > > over the last 12 months we have collected many significant improvements and > bugfixes. > From my point of view, the we should now proceed and start the release > process for version 2.5.0. > > Please give us your vote on whether to start the release process. > > > Vote open for 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > Regards > Rainer >
