Hi, Now that boostcon is over, what are the dates for 1.47? Thanks, Thomas
On Tue, May 24, 2011 at 1:44 AM, Thomas Heller <thom.heller@googlemail.com> wrote:
Hi,
Now that boostcon is over, what are the dates for 1.47?
Time to get going. How about: 1) Close branches/release right away to all commits except by permission. 2) Close branches/release Tuesday, May 31, to all commits except by release managers. 3) Aim for generating a beta release candidate starting Monday, June 6. In the meantime, the release managers (me especially!) need to take a serious look possible problems. Thoughts? --Beman
Message du 26/05/11 21:18 De : "Beman Dawes" A : "boost" Copie à : Objet : Re: [boost] [release] 1.4.7
On Tue, May 24, 2011 at 1:44 AM, Thomas Heller wrote:
Hi,
Now that boostcon is over, what are the dates for 1.47?
Time to get going. How about:
1) Close branches/release right away to all commits except by permission.
2) Close branches/release Tuesday, May 31, to all commits except by release managers.
3) Aim for generating a beta release candidate starting Monday, June 6.
In the meantime, the release managers (me especially!) need to take a serious look possible problems.
Thoughts?
This seems good to me. I would like to commit the attached patch. This was committed in trunk and is working now for the 3 of the 4 compilers that were failing. The last one has not run the regression since the last commit. Could I commit it now or I need to wait the last failing compiler run the regression tests? Best, Vicente
Beman Dawes wrote:
Time to get going. How about:
1) Close branches/release right away to all commits except by permission.
2) Close branches/release Tuesday, May 31, to all commits except by release managers.
3) Aim for generating a beta release candidate starting Monday, June 6.
In the meantime, the release managers (me especially!) need to take a serious look possible problems.
Thoughts?
--Beman
I don't think abruptly closing is a good idea. What about doing it like usual and let us have a last check during the WE. I'd like to check my docs quietly and it surely isn't going to happen in the week... Christophe
On 5/27/2011 4:04 AM, Christophe Henry wrote:
Beman Dawes wrote:
Time to get going. How about:
1) Close branches/release right away to all commits except by permission.
2) Close branches/release Tuesday, May 31, to all commits except by release managers.
3) Aim for generating a beta release candidate starting Monday, June 6.
In the meantime, the release managers (me especially!) need to take a serious look possible problems.
Thoughts?
--Beman
I don't think abruptly closing is a good idea. What about doing it like usual and let us have a last check during the WE. I'd like to check my docs quietly and it surely isn't going to happen in the week...
Agree with Christophe. This is very sudden. Give folks a week at least. Close the release branch June 6 to all commits except by permission, etc., etc. -- Eric Niebler BoostPro Computing http://www.boostpro.com
2011/5/27 Eric Niebler <eric@boostpro.com>:
On 5/27/2011 4:04 AM, Christophe Henry wrote:
Beman Dawes wrote:
Time to get going. How about:
1) Close branches/release right away to all commits except by permission.
2) Close branches/release Tuesday, May 31, to all commits except by release managers.
3) Aim for generating a beta release candidate starting Monday, June 6.
In the meantime, the release managers (me especially!) need to take a serious look possible problems.
Thoughts?
--Beman
I don't think abruptly closing is a good idea. What about doing it like usual and let us have a last check during the WE. I'd like to check my docs quietly and it surely isn't going to happen in the week...
Agree with Christophe. This is very sudden. Give folks a week at least.
I'll have to merge a few things as well. A week would work for me. Joachim -- Interval Container Library [Boost.Icl] http://www.joachim-faulhaber.de
On Fri, May 27, 2011 at 10:48 AM, Joachim Faulhaber <afojgo@googlemail.com> wrote:
2011/5/27 Eric Niebler <eric@boostpro.com>:
On 5/27/2011 4:04 AM, Christophe Henry wrote:
Beman Dawes wrote:
Time to get going. How about:
1) Close branches/release right away to all commits except by permission.
2) Close branches/release Tuesday, May 31, to all commits except by release managers.
3) Aim for generating a beta release candidate starting Monday, June 6.
In the meantime, the release managers (me especially!) need to take a serious look possible problems.
Thoughts?
--Beman
I don't think abruptly closing is a good idea. What about doing it like usual and let us have a last check during the WE. I'd like to check my docs quietly and it surely isn't going to happen in the week...
Agree with Christophe. This is very sudden. Give folks a week at least.
I'll have to merge a few things as well. A week would work for me.
I also think that a week from now is a good time window for everyone. Thomas
On 27-5-2011 10:59, Thomas Heller wrote:
On Fri, May 27, 2011 at 10:48 AM, Joachim Faulhaber <afojgo@googlemail.com> wrote:
2011/5/27 Eric Niebler<eric@boostpro.com>:
On 5/27/2011 4:04 AM, Christophe Henry wrote:
Beman Dawes wrote:
Time to get going. How about:
1) Close branches/release right away to all commits except by permission.
2) Close branches/release Tuesday, May 31, to all commits except by release managers.
3) Aim for generating a beta release candidate starting Monday, June 6.
In the meantime, the release managers (me especially!) need to take a serious look possible problems.
Thoughts?
--Beman I don't think abruptly closing is a good idea. What about doing it like usual and let us have a last check during the WE. I'd like to check my docs quietly and it surely isn't going to happen in the week... Agree with Christophe. This is very sudden. Give folks a week at least. I'll have to merge a few things as well. A week would work for me. I also think that a week from now is a good time window for everyone.
Agreed, June 6 for closing Release as Eric suggested would be perfect. Regards, Barend
On Thu, May 26, 2011 at 11:39 PM, Eric Niebler <eric@boostpro.com> wrote:
On 5/27/2011 4:04 AM, Christophe Henry wrote:
Beman Dawes wrote:
Time to get going. How about:
1) Close branches/release right away to all commits except by permission.
2) Close branches/release Tuesday, May 31, to all commits except by release managers.
3) Aim for generating a beta release candidate starting Monday, June 6.
In the meantime, the release managers (me especially!) need to take a serious look possible problems.
Thoughts?
--Beman
I don't think abruptly closing is a good idea. What about doing it like usual and let us have a last check during the WE. I'd like to check my docs quietly and it surely isn't going to happen in the week...
Agree with Christophe. This is very sudden. Give folks a week at least. Close the release branch June 6 to all commits except by permission, etc., etc.
OK, thanks. Will post schedule announcement later today. --Beman
On 27 May 2011 21:11, Olaf van der Spek <ml@vdspek.org> wrote:
On Fri, May 27, 2011 at 1:12 PM, Beman Dawes <bdawes@acm.org> wrote:
OK, thanks. Will post schedule announcement later today.
Aren't there guidelines for the release process such that choices like these don't have to be made every time?
Things don't always go to plan.
participants (9)
-
Barend Gehrels -
Beman Dawes -
Christophe Henry -
Daniel James -
Eric Niebler -
Joachim Faulhaber -
Olaf van der Spek -
Thomas Heller -
Vicente BOTET