There has been a recent thread on [EMAIL PROTECTED] (which is a
mailing list every podling committer should be subscribed to) about
graduating Felix:
http://mail-archives.apache.org/mod_mbox/incubator-general/
200609.mbox/%
[EMAIL PROTECTED]
An interesting thing that came out of that discussion is not whether
a community has done a release but whether it really understands ASF
policy on what needs to be done in order to do a release. Some recent
events in our community have me concerned that we do not (such as
issues with file headers, questions on notice files, and the like).
There are some guidelines on the incubator site:
http://incubator.apache.org/incubation/Incubation_Policy.html
http://incubator.apache.org/guides/releasemanagement.html
http://incubator.apache.org/guides/sites.html
which are still in development but do provide good information.
Again, every committers should have read these.
I'd also add that is we as a community that are responsible for the
release. Not only compliance with legal and other ASF principles, but
the entire content that we turn out. The quality of our releases is
one of the biggest things that potential users will judge us all on.
However, quality is not just the code, it's the entire user
experience. Not just things like doco and website, but also how
someone's interaction with the community goes. We have had users
recently struggle with building project or running the samples, users
who have asked questions on the mailing lists that have gone
unanswered. We can't afford to let these things go, collectively we
need to be proactive about responding to them.
Ultimately the type of community we establish is determined by us.
Apache has preferences about the type of community its projects
should have (open, meritocratic, etc.) and one purpose of Incubation
is to make sure that podling communities fit with Apache. Whether we
do is what we will be evaluated on when we look to graduate.
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
