On 08/17/2010 09:59 AM, Hyrum K. Wright wrote:
> Howdy all.
>
> All of the wandiscians are having a face-to-face this week, and one of
> the ideas floated was a public-facing page on our website listing the
> items left to complete before the 1.7 release. In the past, we've had
> a STATUS-1.x in trunk, which has been useful for tracking the stages
> toward the release, and helping people who want to contribute know
> what needs to be done. By putting that document on the web, we can
> also use it to communicate to the people who are asking about the
> status of 1.7.
>
> We (Julian, Philip, Erik, and I) can seed this document with the
> results of our discussions this week, and with the release plan I
> posted a few weeks ago.
>
> Thoughts?
I'm no fan of spawning tons of little webpages whose meaningful lifespan is
relatively short. This is Subversion, so you can point folks directly into
the version control repository for stuff like that. However, if you can
make a case for a webpage that can have a much longer lifespan and serve us
far into the future, +1 from me. For example, I can see us maintaining a
subversion.apache.org/release-status.html page which serves multiple purposes:
"Status of Current Release"
### Describe the status of the next .0 release we're working toward.
### This is the stuff you guys are suggesting.
"Subversion Release Maintenance Policy"
### Explain our general policy of actively maintaining only one existing
### release line save for extremely critical security bug fixes that we
### might backport to even older release streams.
"Status of Prior Releases"
### Note the status of each of our pre-1.7 release streams (1.6.x is open
### for maintenance, with a 1.6.13 release due on ?/?/2010; all others
### are closed to changes excepting severe security bug fixes.)
The one downside I see to any of this is that history has shown the
Subversion developers to be pretty slack about updating web pages. I guess
we just don't tend to think most of the time in terms of "How can I better
help Joe Suitwearer understand how and to what degree the coding work I'm
doing is making an impact towards are next release?"
--
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on 2010-08-17 19:27:17 CEST