> Correct me if I'm wrong but 5.2.x hasn't been declared stable yet. My bad... I read "beta" as good enough to release unless we stumble across something serious. Should we be actively scouring jira for things to fix?
5.2.2 2 5.1.0.5 1 5.1.0.8 1 5.0.20 1 Unscheduled 426 Critical 2 Major 226 53% Minor 184 43% Trivial 17 4% Apparently jira needs to be triaged. Writing new code is fun, but I guess I'll take a pass either fixing/moving things out of critical/major Can I have rights in Jira to modify/assign defects? Thanks, Josh On Thu, Oct 14, 2010 at 9:06 AM, Massimo Lusetti <[email protected]> wrote: > On Thu, Oct 14, 2010 at 5:52 PM, Josh Canfield <[email protected]> wrote: > >> What is the argument against making 5.2 the branch? It's been voted as >> stable, if there are significant problems that need to be fixed I'm happy to >> do that, but if its stable then checking something in for 5.2 should be the >> exception, not new features. >> >> The benefit of *not* working in a sandbox is eyes. I want people using this >> stuff ASAP so we can start the process of proving its stable in environments >> I can't account for. If we want to have a quicker release cycle then we need >> to commit to our stable votes and move on. > > Correct me if I'm wrong but 5.2.x hasn't been declared stable yet. > > Cheers > -- > Massimo > http://meridio.blogspot.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
