From: Stuart Donaldson <stuartd@al...> - 2002-10-16 14:23:53
From: Ian Bicking [mailto:ianb@...]
Sent: Monday, October 07, 2002 7:38 PM
To: Stuart Donaldson
Subject: Re: [Webware-discuss] Is there a roadmap to the next WebWare
On Mon, 2002-10-07 at 7:38 pm, Ian Bicking wrote:
>On Mon, 2002-10-07 at 21:07, Stuart Donaldson wrote:
>> Please forgive the newbie questions, I'm new to WebWare, and just trying
>> get a feel for where the project is, and where it is going. The
>> presentation from Python10 indicated a release every 2 months, but from
>> outside it appears things are not going anywhere near that fast.
>> Is there a roadmap or timeframe for the next release available?
>No, not really. The CVS is pretty stable, and a lot of us run off of
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 contributing
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
Anyway, thanks for the response. Please forgive any "soap-box" appearance
to this message.
From: Ian Bicking <ianb@co...> - 2002-10-16 19:58:31
On Wed, 2002-10-16 at 09:23, Stuart Donaldson wrote:
> 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.
I agree a release would be a very good idea. But my experience with
Webware has usually been that if something works, then it keeps working
-- so if you check out a CVS copy and it works for you, then you can
stick with that checkout. There don't seem to be a whole lot of corner
cases, at least with the core functionality.