> On Jun 13, 2018, at 2:17 PM, Paul King <pa...@asert.com.au> wrote: > > > > On Wed, Jun 13, 2018 at 5:11 PM, David Dawson > <david.daw...@simplicityitself.com > <mailto:david.daw...@simplicityitself.com>> wrote: > I would vote 2. > > Actually, i would vote 3) abandon 2.6 immediately. > > We identified a few major things that were broken in the previous alpha > release of > 2.6 but only due to trivial packaging issues, hence the plan to do one more > release.
How about an option #4. If you are planning to do one more release of 2.6.0 anyway just drop the 'alpha' from the name and announce that it is the first and last 2.6.x release expected. - Keith > > Also, Jesper identified a few things that can easily be aligned from 3.0 in > a very short period of time. I am happy to wait for his thumbs up before > proceeding. > > I am also keen on releasing another alpha of 3.0 at the same time as the 2.6 > alpha. > I believe that will make our life easier when answering future > support-oriented questions > about 2.6 on the mailing list going forward. > > So, doing one more alpha release of 2.6 has minimal impact on 3.0 timing and > leaves > us in as clean a state as can be hoped for when retiring a previously planned > branch. > > Cheers, Paul. > ---------------------- Keith Suderman Research Associate Department of Computer Science Vassar College, Poughkeepsie NY suder...@cs.vassar.edu
