From 65b79057b96e621de1bbd7b9c81cdbcee6bfa5b1 Mon Sep 17 00:00:00 2001
From: Brian Paul
-Global vars not allowed. +Global variables are not allowed.
@@ -109,31 +109,22 @@ Function name examples: -
-XXX to do -
- - -These are the instructions for making a new Mesa release.
+-Be sure to do a "cvs update -d ." in the Mesa directory to -get all the latest files. +Use "cvs update -dAP " to get the latest Mesa files from CVS.
--Update the version definitions in src/mesa/main/version.h -
+Create/edit the docs/RELNOTES-X.Y file to document what's new in the release. +Add the new RELNOTES-X.Y file to relnotes.html. Update the docs/VERSIONS file too.
@@ -142,15 +133,33 @@ Edit configs/default and change the MESA_MAJOR, MESA_MINOR and MESA_TINY version numbers. ++Make sure the values in src/mesa/main/version.h is correct. +
+Edit the top-level Makefile and verify that DIRECTORY, LIB_NAME and DEMO_NAME are correct.
++Update the docs/news.html file and docs/contents.html files. +
+ ++Check in all updates to CVS. +
+ ++Tag the CVS files with the release name (in the form mesa_X_Y). +
+ + +Make a symbolic link from $(DIRECTORY) to 'Mesa'. For example, -ln -s Mesa Mesa-6.3 This is needed in order to make a correct -tar file in the next step. +ln -s Mesa Mesa-6.3 +This is needed in order to make a correct tar file in the next step.
@@ -159,17 +168,26 @@ Make the distribution files. From inside the Mesa directory: make tarballs +
+After the tarballs are created, the md5 checksums for the files will +be computed. +Add them to the docs/news.html file. +
+Copy the distribution files to a temporary directory, unpack them, compile everything, and run some demos to be sure everything works.
+-Upload the *.tar.gz and *.zip files to ftp.mesa3d.org +Follow the directions on SourceForge for creating a new "release" and +uploading the tarballs.
-Update the web site. +Update the web site by copying the docs/ directory's files to +/home/users/b/br/brianp/mesa-www/htdocs/
-- cgit v1.2.3