Re: cvs tagging for 3.0

I have been tagging the various tools each time I created a release 
candidate. For the lsb-build pieces the official versions are tagged 
lsb_build_base_3_0_3, lsb_build_cc_3_0_3, and lsb_build_c++_3_0_3. The 
appbat files are tagged appbat_3_0_0 and the lsbsi file are tagged 
lsbsi_3_0_1. The different check tools are tagged similarly (ie. 
appchk_3_0_3).

Regards,

Marvin Heffler
Linux Standard Base
IBM Linux Technology Center
11501 Burnet Road, Zip 905-7A017
Austin, TX 78758
(512) 838-0953    T/L 678-0953

[email protected] wrote on 07/07/2005 10:28:50 PM:

> 
> Now that we've got a final build of 3.0 we need to
> tag the tree.  I'm sure we actually have a policy
> but with several people responsible for several
> different parts of the tree (spec/runtime-test/tools)
> it would be really good to be sure that we uniformly
> tag the cvs tree as the various part release. 
> Except for test, which I haven't looked at, I know
> we did this right for 2.x, because I'm able to check
> out a 2.x branch with a single tag.
> 
> Who's doing the tagging, and what's the tag going
> to be? (note Andrew already tagged the runtime-test
> tree, so we may have somethig to follow).
> 
> 
> 
> _______________________________________________
> lsb-spec mailing list
> [email protected]
> http://mail.freestandards.org/mailman/listinfo/lsb-spec

_______________________________________________
lsb-spec mailing list
[email protected]
http://mail.freestandards.org/mailman/listinfo/lsb-spec