Tobias Polzin | 28 Nov 11:14 2005

Policy for Release Candidates


I would like the mantis developers to rethink their release candidate

Background (AFAIK): RC2 and RC3 had serious bugs (filter not functional rsp.
showing private issues) that made them unsuitable for use in a "not-test"
environment. This bugs were fixed quickly in the CVS-head (or in the
branch), but the distributed package still contained the bug.

Consequence: For this reason it may be impossible for many users to update
and test the newest release candidate, which is not desireable.

My wish: In case of serious bugs in release candidates put high priority to
the task of distributing a new RC with the bugs fixed, even if the fix is
temporary. Either in form of a new RC or of a RC with the same RC number but
with an increased build number.

My suggestion: Fix the bugs (even with temporary quick-fixes that have to be
refactored until the final release) in the CVS-head and release a new RC.

Regards and thanks for mantis!


10 GB Mailbox, 100 FreeSMS/Monat
+++ GMX - die erste Adresse für Mail, Message, More +++

This email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!