Hyrum K. Wright wrote on Thu, 1 May 2008 at 12:48 -0500:
> Daniel Shahaf wrote:
> > Daniel Shahaf wrote on Thu, 1 May 2008 at 09:04 +0300:
> > > Kristian Kauper wrote on Thu, 1 May 2008 at 09:53 +1000:
> > > > Wow, I never expected such a quick resolution. Thanks everyone for
> > > > helping with this.
> > > >
> > > > > Committed r30868 and nominated for backport.
> > > >
> > > > I assume that this means it won't necessarily get into a 1.4.x line,
> > >
> > > Correct; I nominated it for backport to 1.5.x.
> > >
> > > > but if it does, will it be part of 1.4.7?
> > >
> > > If this fix is backported to 1.4 before 1.4.7 is released for testing
> > ^^^^^^^^^^^^^^^^^
> > *If* an 1.4.7 release is made, of course.
>
> Has it been nominated for 1.4.x? It would need to be if it were to be
> included in a future 1.4.7 release.
>
I nominated it for 1.5.x, but it has not been nominated for 1.4.x.
I didn't nominate it for 1.4.x because I didn't know what kind of
changes should be nominated for 1.4.x at this point.
What are the criteria for backporting changes to a minor release line
other than the youngest such line? (In other words, what are the
criteria for backporting to 1.4.x after 1.5.x has branched?)
Thanks,
Daniel
> I actually think we should think about doing a final release off the 1.4.x
> branch after we get 1.5.0 out the door. I suspect a number of people will be
> using 1.4 for a while yet, and since we still claim to support it, it'd be
> good if we actually followed up on that claim.
>
> -Hyrum
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-05-01 19:59:40 CEST