Cliff has been doing so. Frankly, I suspect that many ASF projects need to
clean up their releases to conform with the currently solidifying ASF-wide
guidelines, but the Incubator PMC is more aware of them, and more diligent
in applying them.
From the perspective of being involved in one of the podlings that has
attempted several release attempts, I can confirm your statement
above. When I was trying to get our releases out, I would try to
compare our release distribution to other ASF released project and see
what common across those projects assuming that the common bits would
the stuff that is required. What I found out is that asf policy is
not uniformly applied across all the java based projects. I think
that the latest distributions coming out of the incubator should
actually be what new projects should try to model. And I think this
is largely bases on the fact that there are SOOO many different eyes
from different communities involved in the incubation process. I
think that it's something that you kinda of loose once your graduated.
So in short, I think the incubator is doing a great job, and perhaps
the other graduated projects could benifit from release reviews from
the incubator folks.
A checklist, with illustrating examples, added to a release document would
probably be helpful to ensuring that when a release comes up for vote, there
are fewer -1s cast.
agreed!
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Regards,
Hiram
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
