Re: [boost] 1.30.0 release schedule

2003-02-05 Thread Beman Dawes
At 11:31 AM 1/28/2003, Beman Dawes wrote:

The tentative release schedule for 1.30.0 looks like:

   January 31 - Finish commits of major new components.
   February 14 - Branch for release.
   By end of February - Final release.

This schedule is still looking good.

I'm taking a mini-vacation Thursday through Tuesday (the 11th), so there 
won't be any Win32 regression tests during that time:-(

One last test tonight is running now, and I'll try to get one off tomorrow 
morning. It looks like several people have checked in fixes since this 
morning, and I've fixed a problem with the differential report.

In the meantime, the tests for several other platforms are running nicely.

--Beman


___
Unsubscribe  other changes: http://lists.boost.org/mailman/listinfo.cgi/boost


RE: [boost] 1.30.0 release schedule

2003-01-28 Thread Rozental, Gennadiy
January 31 - Finish commits of major new components.
Could be shift this date for 2 days, So we coould use an extra weekend?

Gennadiy.
___
Unsubscribe  other changes: http://lists.boost.org/mailman/listinfo.cgi/boost



RE: [boost] 1.30.0 release schedule

2003-01-28 Thread Beman Dawes
At 01:02 PM 1/28/2003, Rozental, Gennadiy wrote:

January 31 - Finish commits of major new components.
Could be shift this date for 2 days, So we coould use an extra weekend?

Yes, if you need it. Will anything you commit break compatibility with 
existing code?

The point of Finish commits of major new components is that we have some 
time to test major changes or new libraries before the actual branch for 
release.

The most important major component I'm aware of is the Spirit Library. Joel 
and his team are working hard to meet the January 31 target date.

--Beman


___
Unsubscribe  other changes: http://lists.boost.org/mailman/listinfo.cgi/boost


RE: [boost] 1.30.0 release schedule

2003-01-28 Thread Beman Dawes
At 03:19 PM 1/28/2003, you wrote:

 Yes, if you need it. Will anything you commit break
 compatibility with existing code?

No. It's just fix for Boost.Test unit-test to make it compartible with
regression testing and one new feature. I asked to make sure.

No problem. Thanks for checking.

--Beman


___
Unsubscribe  other changes: http://lists.boost.org/mailman/listinfo.cgi/boost