Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[wtp-pmc] Proposal for Shutting Down Future Releases


It's great that we made our date with WTP 0.7, but we are shipping freshly built code that may have problems that were introduced at the last minute. I'd therefore like to propose a policy for future releases.

I suggest that we allow a minimum of 1 week to elapse between the time we build our final release candidate and the time we declare it. This means that we automatically add 7 days to the date of the build before we officially release it. Furthermore, we do not rebuild it just to create the final version. We actually ship the 7-day old version, so it should be created with the final file names, etc. (No RC1, etc.  in the names).

During the 7 day period, we test the code and create a list of serious known problems. If we decide that this list is too long or bad, we fix the errors and reset the clock.

The benefit of this process is that we ship something with known quality. I believe it is better to do that than ship something with last minute changes, and hope for the best.

Arthur Ryman,
Rational Desktop Tools Development

phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@xxxxxxx
intranet: http://labweb.torolab.ibm.com/DRY6/

Back to the top