[BCC AOO PMC] >From the Chair,
There is now a comprehensive policy on releases from Apache projects, <http://www.apache.org/legal/release-policy>. This has been brewing for a couple of months and has now been ratified by Apache Legal. The most-cautionary aspect, not the only one, has to do with what a binding +1 vote must signify as part of release approval: <http://www.apache.org/legal/release-policy#release-approval>. This becomes a critical matter for the AOO PMC. It is also valuable for non-binding +1 votes to also account for some level of that requirement. The condition on approval is tied to the importance of the release source code and its usability, even though compiled packages and their authenticity are of immense importance to the Apache OpenOffice community. The policy is freshly-minted. I doubt that complete adherence is expected over-night. I do think that serious striving for achievement of the level of quality and accountability that is reflected in the policy will need to be demonstrated. This striving will doubtless need to be accounted for in reports to the board until the AOO release process is fully aligned with what is expected under the policy. I invite discussion here on dev@ on how to make our release processes explicit and evident to all potential contributors, with an eye to having a systematic approach that aligns with the release policy and also reflects the informal Maturity Model for Apache projects. -- Dennis E. Hamilton [email protected] [email protected] +1-206-779-9430 https://keybase.io/orcmid PGP F96E 89FF D456 628A X.509 certs used and requested for signed e-mail --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
