It sounds like we have general consensus on going with 3.1.x for bug fixes only. I've updated JIRA as such and moved issues around. I will mention that while i was going through the release work for 3.1.3/3.2.1 I realized that the minor exception to this rule of "bug fixes only" on the 3.1.x line would be changes to the release process which I would hope we could keep as similar as possible for as long as possible. I'd hate to have different scripts/instructions for one version as opposed to another - that will not make the job of release manager nice.
Thanks, Stephen On Mon, Jul 18, 2016 at 9:02 PM, Dylan Millikin <dylan.milli...@gmail.com> wrote: > +1 from me as well. Sounds good. > > On Thu, Jul 14, 2016 at 2:14 PM, Ted Wilmes <twil...@gmail.com> wrote: > > > It does for me too, +1. > > > > --Ted > > > > On Wed, Jul 13, 2016 at 3:44 PM, Hadrian Zbarcea <hzbar...@gmail.com> > > wrote: > > > > > +1. It does to me. > > > Hadrian > > > > > > > > > On 07/13/2016 04:29 PM, Stephen Mallette wrote: > > > > > >> Since we don't really follow semantic versioning for releases, I > thought > > >> we > > >> should discuss the 3.1.x code line. We've been steadily adding > features > > >> right up to our current 3.1.3 release which we will vote on shortly. I > > >> think it's pretty awesome that we've managed to maintain that older > line > > >> of > > >> code for as long as we have and I think we've evolved it in a very > > >> sensible > > >> way. > > >> > > >> I think we should continue to maintain 3.1.x after the 3.1.3 release, > > >> which > > >> would mean a 3.1.4 release at some point, but we should strictly limit > > the > > >> changes there to bug fixes and not do any "new features" on that line > of > > >> code (i.e the tp31 branch). As it stands, I don't see any open "bugs" > > for > > >> the 3.1.3 in JIRA so as of right now, we wouldn't have much planned > for > > >> 3.1.4. > > >> > > >> Does that make sense for everyone? > > >> > > >> > > >
