At 09:58 AM 3/4/2003, Peter Dimov wrote:
>Beman Dawes wrote:
>> At 04:01 PM 3/3/2003, Mark Rodgers wrote:
>>
>> >Is it time we introduced beta releases into the release procedure?
>> It >seems to me that it would be a good idea to tar up 1.30.0 RC and
>> give >everyone a chance to try it out and
Beman Dawes wrote:
> At 04:01 PM 3/3/2003, Mark Rodgers wrote:
>
> >Is it time we introduced beta releases into the release procedure?
> It >seems to me that it would be a good idea to tar up 1.30.0 RC and
> give >everyone a chance to try it out and report feedback without
> having to >use CVS.
At 04:01 PM 3/3/2003, Mark Rodgers wrote:
>Is it time we introduced beta releases into the release procedure? It
>seems to me that it would be a good idea to tar up 1.30.0 RC and give
>everyone a chance to try it out and report feedback without having to
>use CVS. I know CVS puts me off.
>
>Ques
Is it time we introduced beta releases into the release procedure? It seems
to me that it would be a good idea to tar up 1.30.0 RC and give everyone a
chance to try it out and report feedback without having to use CVS. I know
CVS puts me off.
Questions include
How much of a hassle would it be
At 06:45 PM 3/1/2003, David Abrahams wrote:
>Beman Dawes <[EMAIL PROTECTED]> writes:
>
>> The tag is RC_1_30_0
>
>Didn't we agree that we were going to tag the trunk and generally do
>any merges from the trunk to the branch? This tag appears to be on
>the branch AFAICT.
There was a lot of discuss
Beman Dawes <[EMAIL PROTECTED]> writes:
> The tag is RC_1_30_0
Didn't we agree that we were going to tag the trunk and generally do
any merges from the trunk to the branch? This tag appears to be on
the branch AFAICT.
--
Dave Abrahams
Boost Consulting
www.boost-consulting.com
The tag is RC_1_30_0
I'm going to take a break for the rest of the weekend, and then we should
get together a list of what needs to be done before the actual release.
Thanks,
--Beman
___
Unsubscribe & other changes: http://lists.boost.org/mailman/li
At 01:01 PM 3/1/2003, David Abrahams wrote:
>David Abrahams <[EMAIL PROTECTED]> writes:
>
>> Beman Dawes <[EMAIL PROTECTED]> writes:
>>
>>> OK, I've finally shipped my ACCU talk slides and can concentrate on
>>> 1.30.0. Sorry for the delays.
>>
>> Beman, it appears that you didn't tag the trunk at
David Abrahams <[EMAIL PROTECTED]> writes:
> Beman Dawes <[EMAIL PROTECTED]> writes:
>
>> OK, I've finally shipped my ACCU talk slides and can concentrate on
>> 1.30.0. Sorry for the delays.
>
> Beman, it appears that you didn't tag the trunk at the branch point,
> which will make multiple merges
Beman Dawes <[EMAIL PROTECTED]> writes:
> OK, I've finally shipped my ACCU talk slides and can concentrate on
> 1.30.0. Sorry for the delays.
Beman, it appears that you didn't tag the trunk at the branch point,
which will make multiple merges to the branch more difficult. Do you
want me to do it
OK, I've finally shipped my ACCU talk slides and can concentrate on 1.30.0.
Sorry for the delays.
One issue surfaced mid-week; some Win32 compilers (VC++, possibly others)
are silently failing to compile certain source lines terminated with a CR
only. (The traditional Apple Mac line termination
Dave is working on some Python changes; he says they will be ready in "a
few more days".
Please be patient.
--Beman
___
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
I think we are about ready. Dave Abrahams has asked that we hold off
branching for a couple of more days so he can verify some Boost.Python
issues are cleared, so we will wait as a courtesy to him.
In the meantime, for people who submitted patches in the last couple of
weeks, you might want to
13 matches
Mail list logo
