At first glance this sounds like a sane approach but didn't we start
with this same approach with 1.5.0? I know it was kind of required to
do it for 1.5.0 but we did go off track with delivery. I believe to be
successful at making a deadline for 1.5.1 we need to consider the
following. Do we think the initial stablization is going to take weeks
or months? While we stablize what will be the rules of doing CMRs to
1.5.1? What will be the rules for doing CMRs to 1.5.1 after stablization?
On 10/8/2010 5:13 PM, Jeff Squyres wrote:
> As we discussed on the call last week, since there is already a bit of a divergence between the trunk and the v1.5 branch, how's this for a wild idea:
> What if we re-sync the entire trunk to the v1.5 branch, stabilize that,
> and call it v1.5.1?
> The assumption here is that it will be [far] easier to just re-sync the trunk to the v1.5 branch than to try to bring over stuff in a piecemeal fashion.
> There's a *bunch* of new stuff on the trunk that is not on the v1.5 branch -- there's more than enough "meat" to call it a new release.
> *** Put differently: is there anything on the trunk that is *not* ready to go to the v1.5 series?