Subject: Re: [boost] [1.50.0] Beta schedule
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2012-05-22 11:52:52
I'm confused.. How is it that people don't understand that as soon as
a release it out the door.. It's then time to merge libraries from
trunk to release until the "release branch is closed" announcement
goes out. Why is it that people want to wait until right before the
release is close to do the merges?
On Tue, May 22, 2012 at 10:39 AM, Tim Blechmann <tim_at_[hidden]> wrote:
>>>> I'm about to post a separate message discussing the length of beta
>>> may I add boost.context to 1.50 too?
>> By the time we're talking about a beta,
>> it's usually much too late for new libraries.
> frankly, one thing is talking about a beta, the other thing is
> announcing the beta schedule with the words `release is now closed' ...
> this simply gives people no time to plan in advance in order to merge
> stuff *before* the beta process starts
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo