From 7e73b1afa2de1989251aee4ad2d609ff141f4a5e Mon Sep 17 00:00:00 2001 From: Brian Paul Date: Sat, 2 Oct 2004 15:26:25 +0000 Subject: a few more updates for the 6.2 release --- docs/cvs_branches.html | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) (limited to 'docs/cvs_branches.html') diff --git a/docs/cvs_branches.html b/docs/cvs_branches.html index 5f653b7830..cc07c58ae4 100644 --- a/docs/cvs_branches.html +++ b/docs/cvs_branches.html @@ -15,25 +15,25 @@ code while a CVS branch has the latest stable code.

-Currently (Nov 2003), the trunk is the Mesa 5.1 development code -while the mesa_5_0_branch branch has the stable Mesa 5.0.x code. +Currently (Oct 2004), the trunk is the Mesa 6.3 development code +while the mesa_6_2_branch branch has the stable Mesa 6.2.x code.

Mesa releases use an even/odd numbering scheme to represent stable/development releases. -For example, Mesa 5.0.x (0 is considered even) is a stable release while -Mesa 5.1.x is a development release. +For example, Mesa 6.2 (0 is considered even) is a stable release while +Mesa 6.3 is a development release.

To checkout a specific CVS branch pass -r and the branch tag after your CVS command. -For example cvs checkout -r mesa_5_0_branch Mesa will -checkout the 5.0.x branch and cvs update -r -mesa_5_0_branch will convert your current CVS tree to the 5.0.x +For example cvs checkout -r mesa_6_2_branch Mesa will +checkout the 6.2 branch and cvs update -r +mesa_6_2_branch will convert your current CVS tree to the 6.2 branch. Consult