Re: discusion about releases involving new features

Hi Tsvetelin,

I agree that the documentation isn't keeping up with the releases.
Unfortunately the documentation is often takes longer than the code
changes, and isn't as much fun.

I think when T2.4 gets out there will be a big focus on catching up
with the documentation. I think Howard is intending to complete his
book after this release.  If it is any consolation I still think Tapestry
is better documented than 9 out of 10 open source projects.

Regarding a feature specification/plan this sounds like a good idea. There
has been some move towards this on tapestry/wiki.

I think voting on this stuff is a good idea, and now we have the apache
voting rules in place we have the process in place to do this.

Determining release dates for Tapestry will be quite difficult, being an
open source project every one is contributing their time outside of work.
What people can do at any time is going to be a big variable, coupled
with getting through the beta/release candidate cycle, it going to be
hard to predict. Maybe we can aim for per Quarter resolution for release
dates, e.g. T2.3 in 2003 Q1

With your own project release plans are you dependent on future Tapestry
features, bug fixes, or are you after a road map.

regards Malcolm Edgar

At 05:30 PM 14/01/2003 +0200, tsvetelin wrote:
>I would like to suggest something about releases involving new features.
>It's very nice to see a new tapestry release almost every month, but it's
>dificult for us (people who use tapestry) to follow new features, because
>there isn't enough information.
>
>I would like to discuss the following scenario:
>Making a feature specification/plan for a new release and setting a deadline
>for approving it. After the deadline the contributors must vote this spec
>and after that it must be publish in tapestry/wiki page and sent to
>developers mailing list. After the deadline no changing of this spec should
>be possible. Optional - a deadline could be established for the new release.
>
>If this process is accepted, we could easily follow tapestry development and
>we could make our specific project release plans and long-term development
>plans. That will save a lot of our time.
>
>Best regards
>Tsvetelin Saykov
>
>
>
>-------------------------------------------------------
>This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
>are you planning your Web Server Security? Click here to get a FREE
>Thawte SSL guide and find the answers to all your  SSL security issues.
>http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
>_______________________________________________
>Tapestry-developer mailing list
>[email protected]
>https://lists.sourceforge.net/lists/listinfo/tapestry-developer



-------------------------------------------------------
This SF.NET email is sponsored by: Take your first step towards giving 
your online business a competitive advantage. Test-drive a Thawte SSL 
certificate - our easy online guide will show you how. Click here to get 
started: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0027en