X-Git-Url: https://git.libre-soc.org/?a=blobdiff_plain;f=docs%2Fdevinfo.html;h=8887dd02624a8ca5eb602aab861bdeddd8b193f6;hb=9a7f84d6b28e180ef79349b36de9a5d58a1e2dc9;hp=1f54a92d0f5705698e3fc4b93a6791a7b646f81d;hpb=73f6f7ed91a9d9620fa2ee7bb6d89a894ee6b6a8;p=mesa.git diff --git a/docs/devinfo.html b/docs/devinfo.html index 1f54a92d0f5..8887dd02624 100644 --- a/docs/devinfo.html +++ b/docs/devinfo.html @@ -107,7 +107,7 @@ Global variables are not allowed. Function name examples: 

-	glFooBar()       - a public GL entry point (in dispatch.c)
+	glFooBar()       - a public GL entry point (in glapi_dispatch.c)
 	_mesa_FooBar()   - the internal immediate mode function
 	save_FooBar()    - retained mode (display list) function in dlist.c
 	foo_bar()        - a static (private) function
@@ -123,51 +123,43 @@ These are the instructions for making a new Mesa release.
 
 
Get latest source files

 

-Use "cvs update -dAP " to get the latest Mesa files from CVS.
+Use git to get the latest Mesa files from the git repository, from whatever
+branch is relevant.
 

 
 
 
Verify and update version info

 

-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.
+Create/edit the docs/relnotes-x.y.html file to document what's new in the release.
+Add the new relnotes-x.y.html file to relnotes.html.
 

 
 

-Edit the MESA_MAJOR, MESA_MINOR and MESA_TINY version numbers in
-configs/default and configure.ac.
+Update the MESA_MAJOR, MESA_MINOR and MESA_TINY version numbers in
+configs/default.
+Also update the VERSION line in the top-level Makefile.
 

 
 

-Make sure the values in src/mesa/main/version.h is correct.
+Make sure the values in src/mesa/main/version.h are correct.
 

 
 

-Edit the top-level Makefile and verify that DIRECTORY, LIB_NAME and
-DEMO_NAME are correct.
+Update docs/news.html.
 

 
 

-Update the docs/news.html file and docs/download.html files.
+Check in all updates to git.
 

 
 

-Check in all updates to CVS.
-

-
-

-Tag the CVS files with the release name (in the form mesa_X_Y).
+Tag the files with the release name (in the form mesa_X_Y)
+with: git tag -a mesa_X_Y
+Then: git push origin mesa_X_Y
 

 
 
 
Make the tarballs

-

-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.
-

-
 

 Make the distribution files.  From inside the Mesa directory:
 
@@ -177,7 +169,7 @@ Make the distribution files.  From inside the Mesa directory:
 

 After the tarballs are created, the md5 checksums for the files will
 be computed.
-Add them to the docs/news.html file.
+Add them to the docs/relnotes-X.Y.html file.
 

 
 

@@ -191,17 +183,30 @@ Follow the directions on SourceForge for creating a new "release" and
 uploading the tarballs.
 

 
+

+Basically, to upload the tarball files with:
+

+
+rsync -avP ssh Mesa*-X.Y.* USERNAME@frs.sourceforge.net:uploads/
+
+

+
 

 Update the web site by copying the docs/ directory's files to 
-/home/users/b/br/brianp/mesa-www/htdocs/
+/home/users/b/br/brianp/mesa-www/htdocs/ with:
+

+
+sftp USERNAME,mesa3d@web.sourceforge.net
+
 

 
 

 Make an announcement on the mailing lists:
-mesa3d-dev@lists.sf.net,
-mesa3d-users@lists.sf.net
+
+mesa-dev@lists.freedesktop.org,
+mesa-users@lists.freedesktop.org
 and
-mesa3d-announce@lists.sf.net
+mesa-announce@lists.freedesktop.org