branch snapshot version tag

branch snapshot version tag

[Andrew Cagney]

Hmm,

The current branch snapshot process is setting the version tag 
(version.in) to YYYYMMDD.  This is a little unfortunate since snapshots 
taken from the trunk are also setting version.in to YYYYMMDD. Might be a 
good idea if I change it.

My first choice for the snapshot version.in would be 5.0.91-YYYYMMDD but 
due to a ``technical problem'' with the snapshot scripts that won't work.

That leads to my second and third choices.

	5.0.91.YYYYMMDD
or 
5.0.91_YYYYMMDD

Unless someone comes up with a compelling argument for why one of these 
is better than the other, I'll toss a coin and then tweek the snapshot 
process to generate the second one.

enjoy,
Andrew

Re: branch snapshot version tag

[H . J . Lu]

On Thu, Oct 18, 2001 at 01:01:57AM -0400, Andrew Cagney wrote:
> Hmm,
> 
> The current branch snapshot process is setting the version tag 
> (version.in) to YYYYMMDD.  This is a little unfortunate since snapshots 
> taken from the trunk are also setting version.in to YYYYMMDD. Might be a 
> good idea if I change it.
> 
> My first choice for the snapshot version.in would be 5.0.91-YYYYMMDD but 
> due to a ``technical problem'' with the snapshot scripts that won't work.
> 
> That leads to my second and third choices.
> 
> 	5.0.91.YYYYMMDD
> or 
> 5.0.91_YYYYMMDD

I don't think you can use `.' in tag. I always turn `.' into `_' and
use it as my cvs tag.


H.J.

Re: branch snapshot version tag

[Christopher Faylor]

On Wed, Oct 17, 2001 at 10:46:35PM -0700, H . J . Lu wrote:
>On Thu, Oct 18, 2001 at 01:01:57AM -0400, Andrew Cagney wrote:
>> Hmm,
>> 
>> The current branch snapshot process is setting the version tag 
>> (version.in) to YYYYMMDD.  This is a little unfortunate since snapshots 
>> taken from the trunk are also setting version.in to YYYYMMDD. Might be a 
>> good idea if I change it.
>> 
>> My first choice for the snapshot version.in would be 5.0.91-YYYYMMDD but 
>> due to a ``technical problem'' with the snapshot scripts that won't work.
>> 
>> That leads to my second and third choices.
>> 
>> 	5.0.91.YYYYMMDD
>> or 
>> 5.0.91_YYYYMMDD
>
>I don't think you can use `.' in tag. I always turn `.' into `_' and
>use it as my cvs tag.

Ditto.  I use '-' sometimes too for cygwin tags.  I actually thought that
'-' wasn't allowed and had been using '_' but somewhere along the line
I started using '-' by mistake and the tags have been working fine.

cgf

Re: branch snapshot version tag

[Andrew Cagney]

H,.J worote:

>>I don't think you can use `.' in tag. I always turn `.' into `_' and
>>use it as my cvs tag.

Then CGF wrote:

> Ditto.  I use '-' sometimes too for cygwin tags.  I actually thought that
> '-' wasn't allowed and had been using '_' but somewhere along the line
> I started using '-' by mistake and the tags have been working fine.

Er, I'm refering to the ``version tag'' stored in the file gdb/version.in.

 >> Hmm,
 >>
 >> The current branch snapshot process is setting the version tag
 >> (version.in) to YYYYMMDD.  This is a little unfortunate since snapshots
 >> taken from the trunk are also setting version.in to YYYYMMDD. Might 
be a
 >> good idea if I change it.
 >>
 >> My first choice for the snapshot version.in would be 5.0.91-YYYYMMDD 
but
 >> due to a ``technical problem'' with the snapshot scripts that won't 
work.
 >>
 >> That leads to my second and third choices.
 >>
 >> 5.0.91.YYYYMMDD
 >> or
 >> 5.0.91_YYYYMMDD

Andrew

Re: branch snapshot version tag

[Andrew Cagney]

> Hmm,
> 
> The current branch snapshot process is setting the version tag (version.in) to YYYYMMDD.  This is a little unfortunate since snapshots taken from the trunk are also setting version.in to YYYYMMDD. Might be a good idea if I change it.
> 
> My first choice for the snapshot version.in would be 5.0.91-YYYYMMDD but due to a ``technical problem'' with the snapshot scripts that won't work.
> 
> That leads to my second and third choices.
> 
>     5.0.91.YYYYMMDD
> or 5.0.91_YYYYMMDD
> 
> Unless someone comes up with a compelling argument for why one of these is better than the other, I'll toss a coin and then tweek the snapshot process to generate the second one.

Just so people are clear on this.  5.1 branch snapshot tarball will be 
named:

	gdb+dejagnu-5.0.90_20011020.tar.bz

and the startup message when that tar ball is built will be:

	$ gdb
	GNU gdb 5.0.90_20011020

enjoy,
Andrew

Re: branch snapshot version tag

[Andrew Cagney]

> Just so people are clear on this.  5.1 branch snapshot tarball will be named:
> 
>     gdb+dejagnu-5.0.90_20011020.tar.bz
> 
> and the startup message when that tar ball is built will be:
> 
>     $ gdb
>     GNU gdb 5.0.90_20011020

Tis done.

Andrew