 |
This is usually the best 'source' of the source. |
| | |
|
Firebird CVS tree currently has three main modules:
- interbase - for Firebird 1.0
- firebird2 - for Firebird 1.5 and 2.n
- vulcan - for Vulcan
Don't get caught trying to download code from the firebird module - it is incorrectly named and stores QA code for vulcan. |
| | |
|
Released code is always tagged. Typical tag format is thus:
R1_5_0 - Release 1.5.0
T2_0_0_Beta1 - Alpha, beta or RC of v2.0
B2_0_Release - A branch tag
As usual, the exception makes the rule. Firebird 1.0 doesn't use this tag naming convention, but it is clear enough what the tags mean.
|
| | |
|
It is recommended to start with tagged source. Building HEAD is liable to cause surprises for the inexperienced. |
| | |
| Branch tags start with a B. They are a bit special and are equivalent to the HEAD tag of a module. |
| | |
| Tags starting with a T or an R are normal tags. |
| | |
| CVS 'knows' what tags go with what code. For example, if the B2_0_Release code was checked out and tagged as T2_0_0_RC5 it would only tag B2_0_Release code. It would not get confused with HEAD. |
| | |
| All this means that checking out B2_0_Release or B1_5_Release means that you get the latest code for that branch. This is likely to be untested. On the other hand, checking out T2_0_0_Beta1 means you get the code that was QA'ed for the v2.0 beta 1 release. |
| | |
| | |
