Update of /cvsroot/monetdb/buildtools/doc
In directory sc8-pr-cvs16.sourceforge.net:/tmp/cvs-serv28356/doc
Modified Files:
HowToRelease.rst
Log Message:
propagated changes of Friday 15 Feb 2008 - Monday Feb 18 2008
from the MonetDB_1-22 branch to the development trunk
Index: HowToRelease.rst
===================================================================
RCS file: /cvsroot/monetdb/buildtools/doc/HowToRelease.rst,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- HowToRelease.rst 8 Feb 2008 22:33:30 -0000 1.3
+++ HowToRelease.rst 18 Feb 2008 15:33:22 -0000 1.4
@@ -14,6 +14,9 @@
- A release is a major time investment of several people. Cooperation
of all developers is essential to live up to our charter: to deliver
state-of-the-art database technology to the community.
+- In particular, a new release should not be worse than any previous one,
+ i.e., all features and tests that did work before (and are still
+ supported) must still work flawlessly with the new release.
- Strictly adhere to bug fixes and feature updates. Nothing
is a bug fix unless it is covered by a bug report.
- Remember that after every release there will be uncountable
@@ -29,6 +32,8 @@
- Prepare a draft release note to finalize the scope of the release
and inform those affected/responsible for parts to fix errors and
prepare/update documentation.
+- Decide on and fix the desired version numbers for all packages involved in
+ the release.
- All other developers leave the stable branch.
- Get all the bug fixes (and new features for a major release) in long
before continuing with the rest of the steps.
@@ -37,6 +42,11 @@
- Regularly try building the release on Windows during this stage.
This includes trying to create installers and trying out the
installers.
+- A major (and very time consuming) task of the release manager is to
+ continuously remind the developers to indeed care about and fix their
+ bugs. This task consists mainly of reading aloud both the nightly testing
+ result emails and the daily TestWeb status to each involved developer
+ personally.
Preparation of a Major Release
------------------------------
@@ -57,6 +67,10 @@
``dft_netcdf=no``).
- Create a tag on the head of the new branch for propagation purposes
(e.g. ``cvs tag MonetDB_1-16_sync``).
+- Update the nightly testing setup to use the new branch for nightly
+ testing.
+- Where necessary, update the "TestWeb" pages of the MonetDB web site to
+ point to the new branch's nighly testing results.
After this, it's **bug fixes only** on the new branch.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Monetdb-checkins mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/monetdb-checkins
