Called by: Gerard van Enk Total tally on this call : +7
YEA (7) : Pierre van Rooden, Rico Jansen, Rob Vermeulen, Nico Klasens, Rob van Maris, Daniel Ockeloen, Jaco de Groot
ABSTAIN (1) : Michiel Meeuwissen
NAY (0) :
VETO (0) :
No votes, assumed abstained (7): Eduard Witteveen, Marcel Maatkamp, David van Zeventer, Johannes Verelst, Kees Jongenburger, Vincent van der Locht, Mark Huijser
Vote passed.
The release team consists of Geard van Enk, Daniel Ockeloen, and Michiel Meeuwissen.
Gerard van Enk wrote:
CALL FOR:
The final releaseplan for the next version of MMBase.
This is majority call, with a margin of 3 votes.
Please pay attention: two votes must be made: 1 for releaseplan and 1 for the releaseteam (releaseteam at least requires 3 members).
LINKS:
Attached document.
START OF CALL: 2003-12-12 16.00
END OF CALL: 2003-12-18 0:30
I agree with the proposed releaseplan:
[_] +1 (YEA)
[_] +0 (ABSTAIN )
[_] -1 (NAY), because :
[_] VETO, because:
I'd like to be part of the releaseteam
[_] +1 (YEA)
[_] +0 (ABSTAIN, if you don't know yet)
[_] -1 (NAY)
Gerard
------------------------------------------------------------------------
NOTE: This is the final version of the release plan for the next release of MMBase. After this document has been approved by the commitors on the developers list, nothing in this document can be changed without a new vote.
MMBase-1.7.0 Release Plan =========================
Objective
=========
The objective of the proposed MMBase release is to provide a stable MMBase-version, which can be used in a production environment.
Changes ======= MMBase-1.7.0 includes major new features over MMBase-1.6.x, some of which are related to the following projects:
- Field Types - Storage - Taglib 2 - MMCI 1.2 - Documentation - Database Search Queries
More information about these new features will be added to the releasenotes.
A start has been made to make MMBase more modular. Some parts already
available in the previous version, have been moved into an
application. Also some new functionality has been added as an
application. The following applications will be distributed with MMBase-1.7.0:
- Cloud Context Security (including editors) - Media - Email - Bugtracker - Community - RMMCI - Editwizards
For more information about these applications see the releasenotes or the documentation.
Other important changes/new features included in this release are:
- Apps 1 applications needed by a certain application can be added to
the requirements tag inside the application file. These applications
will be installed before installing the application needing the
other applications. - A CharacterEncodingFilter has been added.
- The 'default' part has been removed from the config directory path.
- A testmodule has been added for automated testing.
An almost complete list of changes can be found in the releasenotes or the documentation.
Important bugfixes included are: - Tomcat shutdowns properly (all threads are started as daemon threads now)
Release criteria ================ All (big) changes need to be stable, documented and tested.
Bugs: ----- All bugs from the bugtracker have to be checked and the ones which are important for the release must have a high priority. All bugs with a high priority must be fixed before the release. New bugs found during the release proces will only be fixed if there's a bugreport. For more information see bugtracker: <http://www.mmbase.org/bug>
Additional criteria =================== The release needs to tested and found stable with:
OS: - Linux - Windows 2000, XP - Sun Solaris - MacOS X
JDK:
- Sun JDK1.4.x
- IBM JDK1.4.x
- Blackdown JDK1.4.x
Servlet Engines: - Apache Tomcat 4.1.x - Orion 2.0.x - Resin - Jetty
Databases: - MySQL - Informix - Hsqldb - PostgreSQL
Testing =======
Testprocedure
-------------
Because there aren't testcases for every part of MMBase the following
test procedure must be used before MMBase can be found stable on a certain platform/jdk/servletengine/etc:
- clean installation must succeed (with empty database)
- jsp-editors must be functioning - example applications must deploy successfully and must be working
(most applications can be tested using an example from the
mmexamples dir) - example editwizards must be functioning
- all examples must work
Upgrade ------- Upgrading existing MMBase installation must be tested before MMBase-1.7.0 can be released. If there are any issues regarding upgrading existing MMBase installations they must be described in an upgrade manuel (if they can't be fixed).
Big clouds ---------- Because some problems (like performance problems) are likely only to occur with big clouds, it's necessary MMBase-1.7.0 will be tested with some big clouds. We need support for this from organizations running big MMBase installations.
Todo
====
A complete list of todo items will be added to cvs. This list must
contain all things needed to be done before the release can take
place. Also this document will contain a list of people/organizations
willing to test certain os/jdk/database/servlet application
combination.
Releases ======== There will be at least 2 release candidates before the final release.
Code freeze:
Start Date: 20-12-2003 End Date: 19-01-2004
The freeze will almost last a month, because a lot of people will take
some time off during the last weeks of december. Also it's necessary
because there are a lot of bugs that need to be fixed. During this code freeze most outstanding bugs must be fixed and
stability must be tested. If there are more problems found during the freeze, or fixing the most
important bugs takes more time, the duration of the freeze may be
extended.
RC 1:
Tag Date: 23-12-2003 Release Manager: Gerard van Enk
The first RC will be made in the first week of the freeze, this way non-developers can help testing and they can report bugs which need to be fixed during the freeze. It can also be used for testing in different environments (os, jdk, application server, etc). CVS will be tagged after creating this rc and the tagname will be 'MMBase-1_7_0_rc1'.
Branch:
Date: 19-01-2004
The branch will be used to create last Release Candidate and after the 1.7.0 release it will be used for minor releases. The name of the branch will be 'MMBase-1_7'.
RC 2:
Tag Date: 21-01-2004 Release Manager: Gerard van Enk
This RC will be used to determine any showstoppers and decide if there
are more Release Candidates needed. CVS tagname will be 'MMBase-1_7_0_rc2'.
Final Release:
Code Freeze/Tag Date: 26-01-2004 Release Manager: Gerard van Enk
The final build. Before this release can take place all documentation
needs to be finished, all known bugs need to be resolved (or added to
the 'know issues' part in the releasenotes.txt) and the community must
approve the final release. CVS tagname after the release will be 'MMBase-1_7_0_Final'.
Maintenance Plan
=================
The maintenance plan is a plan which describes what to do after the
release. Normal development continues on cvs-head, but it's possible
bugs will be found in this release and cvs-head isn't stable enough to
be released. These bugs must be fixed in the branch which is
created for this release and a minor release will be done (after being
proposed to the community). In any case, no backwards-incompatible
changes should be made in this branch! New functionality from cvs-head may only be backported to this branch
after a vote by the commitors.
The release team (see below) is responsible for taking care of the maintenance plan.
Release Team ============ The release team will be composed of the committers that give the binding +1 on the release plan and release proposal. It must have at least 3 members.
The release team will coordinate the execution of the release plan, dispatch bugs to volunteers, review commits, and act as a lead in the release process.
One of the team members will act as "Release Manager" and will be responsible for building the release candidates, making the
announcements about the release progress, announce the final release
on Freshmeat, etc.
After the release is done, the release team is responsible for the maintenance plan.
-- Pierre van Rooden Mediapark, C 107 tel. +31 (0)35 6772815 "Never summon anything bigger than your head."
