We are still in alpha, so bugs with severity S1-S3 are eligible (and S4 with a risk assessment) Severity is something like this (but as a project we probably need to define the categories for Maven core)
S1: blows up for everyone, no workaround S2: blows up under certain circumstances, no workaround. Also feature does not work, no workaround. S3: blows up but there is a workaround. Most other bugs S4: cosmetic issues On Sat 4 Mar 2017 at 12:34, Christian Schulte <[email protected]> wrote: > Am 03/02/17 um 22:55 schrieb Stephen Connolly: > > I'd like to declare feature freeze for alpha-2 on March 9th. > > > > If a feature does not land in alpha-2 it will not be in beta-1 (i.e. > Only bug fixes or rip out features that are causing S1/S2 issues will be in > the diff from alpha-2 to beta-1) > > > > I am aiming beta-2 approx 2 weeks after alpha-2 and the GA approx 2 > weeks after that. > > Should we include > > <https://issues.apache.org/jira/browse/MNG-6173> > > FIX-3.5.0? It has just been reported. It also has an IT pull request. If > no one objects, I'll create a branch and later merge it to master. > > Regards, > -- > Christian > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Sent from my phone
