Right. I wasn't sure if there were 10 issues to backport or 150. If there are only a few isolated fixes to apply, then I'd be comfortable with just applying them, testing and releasing. If there are a ton of fixes, which might have overlapping effects, then lets spend a day or so with a tagged rc and have everybody test the same finished product before we ship it.
Ian On Tuesday, October 1, 2013, Jesse wrote: > Nope, I don't think we've ever done minor rc's, this is a bit more of a > significant release though. > Back-fill would just be putting all the updated plugin native code back > into each platform, as well as making sure any relevant js changes went > back into cordova-js before being tagged+built. Kind of a hassle, with no > easy way of making sure things aren't missed, other than mobile-spec. > > > > @purplecabbage > risingj.com > > > On Tue, Oct 1, 2013 at 12:32 PM, Ian Clelland > <iclell...@chromium.org<javascript:;> > >wrote: > > > Have we done RCs for minor releases before? I don't recall any for 3.0.1 > to > > 3.0.9, and I can't see anything in my email archives from 2.6.1 or 2.8.1. > > > > Not that it's a bad idea; I just don't think it's a formality that has > been > > observed in the past. > > > > How much back-fill are you expecting? > > > > > > > > > > On Tue, Oct 1, 2013 at 2:50 PM, Jesse > > <purplecabb...@gmail.com<javascript:;>> > wrote: > > > > > As soon as we are done with 3.1.0 it would be a good time to go back > and > > > back-fill for a 2,9,1 release. > > > > > > Who's with me? > > > Do we need to do an RC? If so, a quick one? > > > > > > Cheers, > > > Jesse > > > > > > @purplecabbage > > > risingj.com > > > > > >
