forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <>
Subject Re: release process
Date Mon, 12 Oct 2009 11:10:59 GMT
2009/10/12 David Crossley <>:
> Thorsten Scherler wrote:
>> IMO A should be the way to wrap up current development. Like pointed
>> out by David we need to have a release that  contains the work of the
>> last years since the release.
> It may require two releases in reasonably quick succession.
> Otherwise we risk holding up the release for more ages.

Or even a release every 2-3 months regardless of the state of
development. I think one of our mistakes has been to wait for features
to be finished before releasing. Then they've been redesigned,
rejigged and broken.

Look at Locationmap - it took us three years to get that code in, once
in it was tidied up and polished. The XML config system was put into
the last release as an undocumented feature and, as a result has seen
significant work and is now ready for official release (yet there has
been no release).

It used to be just David doing releases. We discussed and agreed more
frequent releases. So I an Ferdinand cut a release. From memory I
think that was the last release Forrest had. All good intentions, but
no action.

> The last release was much easier with those notes.

+1000 - the process isn't actually that hard. It only looks complex
because it is well documented. Ironically, as David says, it is this
documentation that makes the process easier.



Ross Gardler

OSS Watch - supporting open source in education and research

View raw message