<TITLE>Development Notes</TITLE>
-<BODY text="#000000" bgcolor="#55bbff" link="#111188">
+<link rel="stylesheet" type="text/css" href="mesa.css"></head>
+
+<BODY>
<H1>Development Notes</H1>
corresponding Python scripts.
</li>
<li>
- Find an existing extension that's similar to the new one and search
- the sources for code related to that extension.
- Implement new code as needed.
- In general, new state variables will be added to mtypes.h. If the
- extension is rather large, try to implement it in a new source file.
+ Add a new entry to the <code>gl_extensions</code> struct in mtypes.h
+</li>
+<li>
+ Update the <code>extensions.c</code> file.
+</li>
+<li>
+ From this point, the best way to proceed is to find another extension,
+ similar to the new one, that's already implemented in Mesa and use it
+ as an example.
</li>
<li>
- If hew extension adds new GL state, the functions in get.c, enable.c
+ If the new extension adds new GL state, the functions in get.c, enable.c
and attrib.c will most likely require new code.
</li>
</ul>
Here's the GNU indent command which will best approximate my preferred style:
</p>
<pre>
- indent -br -i3 -npcs infile.c -o outfile.c
+ indent -br -i3 -npcs --no-tabs infile.c -o outfile.c
</pre>
</p>
<p>
-Global vars not allowed.
+Global variables are not allowed.
</p>
<p>
</pre>
-<H2>Writing a Device Driver</H2>
+<H2>Making a New Mesa Release</H2>
<p>
-XXX to do
+These are the instructions for making a new Mesa release.
</p>
+<H3>Get latest source files</H3>
+<p>
+Use git to get the latest Mesa files from the git repository, from whatever
+branch is relevant.
+</p>
-<H2>Making a New Mesa Release</H2>
-
+<H3>Verify and update version info</H3>
<p>
-These are the instructions for making a new Mesa release.
+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 <a href="relnotes.html">relnotes.html</a>.
</p>
<p>
-Be sure to do a "cvs update -d ." in the Mesa directory to
-get all the latest files.
+Update the MESA_MAJOR, MESA_MINOR and MESA_TINY version numbers in
+configs/default.
+Also update the VERSION line in the top-level Makefile.
</p>
<p>
-Update the version definitions in src/mesa/main/version.h
+Make sure the values in src/mesa/main/version.h are correct.
</p>
<p>
-Create/edit the docs/RELNOTES-X.Y file to document what's new in the release.
-Update the docs/VERSIONS file too.
+Update the docs/news.html file and docs/download.html files.
</p>
<p>
-Edit configs/default and change the MESA_MAJOR, MESA_MINOR and MESA_TINY
-version numbers.
+Check in all updates to git.
</p>
<p>
-Edit the top-level Makefile and verify that DIRECTORY, LIB_NAME and
-DEMO_NAME are correct.
+Tag the files with the release name (in the form <b>mesa_X_Y</b>)
+with: <code>git tag -a mesa_X_Y</code>
+Then: <code>git push origin mesa_X_Y</code>
</p>
+
+<H3>Make the tarballs</H3>
<p>
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.
+<code>ln -s Mesa Mesa-7.5</code>
+This is needed in order to make a correct tar file in the next step.
</p>
<p>
make tarballs
</pre>
+<p>
+After the tarballs are created, the md5 checksums for the files will
+be computed.
+Add them to the docs/relnotes-X.Y.html file.
+</p>
+
<p>
Copy the distribution files to a temporary directory, unpack them,
compile everything, and run some demos to be sure everything works.
</p>
+<H3>Update the website and announce the release</H3>
+<p>
+Follow the directions on SourceForge for creating a new "release" and
+uploading the tarballs.
+</p>
+
<p>
-Upload the *.tar.gz and *.zip files to ftp.mesa3d.org
+Basically, to upload the tarball files with:
+<br>
+<code>
+rsync -avP ssh Mesa*-X.Y.* USERNAME@frs.sourceforge.net:uploads/
+</code>
</p>
<p>
-Update the web site.
+Update the web site by copying the docs/ directory's files to
+/home/users/b/br/brianp/mesa-www/htdocs/ with:
+<br>
+<code>
+sftp USERNAME,mesa3d@web.sourceforge.net
+</code>
</p>
<p>
projects / mesa.git / blobdiff