Re: Build Tag Naming Conventions

Matt Small wrote:
> I have been noticing some instabilities of late in release33 version of the
> cvsclient. I'm hoping that 3.3.1 will take care of it, so I got that jar off
> the downloads page. Now I am trying to get the source, but I'm a little
> confused about which tag to check out is BLD200203040100 the one I want or
> should I get QBE200203010100-BLD200203041529. Can you all let me in on the
> naming convention of the tags/builds for future reference (what does QBE
> mean)? Also, is 3.3.1 the best version to go with for a production system?
> Release 33 has all the features I need so I am really looking for the most
> stable.
> 
> Thanks alot, great product. 
> 
> Matt
> 

The most stable branch is probably the release33 branch which currently 
contains the code for 3.3.1 release (I think just today there were 
merged changes that contain 3.3.2 fixes)

the QBE branches are created when a Q-build is not approved by our QA. 
The qhole code base is thatn branched and the showstoppers are then 
fixed. the format is QBEYYYYMMDDHHMM (year, month,day...) the same 
format goes for the tags. each daily build is tagged with the BLD tag.. 
that way everyone can recreate the any particular build.

BTW what are these "instabilities?"

Milos