Rob van Maris wrote:
<Gerard van Enk:>The maintenance plan is a plan which describes what to do after the release is done.I would like to see a maintenance plan in which the release team commits itself to maintenance releases on a very regular basis. I.e. every couple of weeks and following major bugfixes, and consistently for an extended period, at least until the first maintenance releases for the next milestone release are released. Lacking this, there has never been a release of 1.5 that meets production quality requirements so far.
Well we're using it on our servers :)
Yes. But the only problem is time. People can commit themselves on to the release and maintaince plan, but spent time on it is something different.Is something going to be done about this?
See my reply to michiel in this thread for some kind of proposal for a new release-strategy.
Gerard
