I 100% agree with you -- we just need someone with the time and inclination
to act as a Webware release manager.
Any volunteers? The first step would be just to review the open bugs and
patches on SourceForge and write up a short proposal for what to put into
the next release and when to do the release. It could just be "release
what's in CVS" because to me it seems very solid and definitely better than
the last release.
(I asked for and got a volunteer to do this a couple of months ago, but that
person kinda disappeared so we need another volunteer.)
Stuart Donaldson wrote:
> Perhaps I don't understand the essence of the project, as I
> am very new to
> Webware. However I would strongly recommend having some sort
> of release
> cycle planned out to get to known-stable releases.
> There is a big advantage in having a "stable" release that
> users should
> be able to deploy knowing that an implicit level of support
> is available
> by having a common platform, rather than the hit-or-miss base you get
> depending on which day you check something out of CVS.
> Also, having a roadmap identifying features and bugs to be addressed
> in the next release will give a lot of visibility to potential users
> of the product to know what is planned, and when the core developers
> are expecting features and bugs to be addressed.
> "Staying current with CVS" works well for developers actively
> to the product, or those wanting to stay on the bleeding edge. However
> if I am looking to develop an application I want to deploy to multiple
> sites, I now have a large potential compatibility mess on my
> hands without
> identified releases.
> Anyway, thanks for the response. Please forgive any
> "soap-box" appearance
> to this message.