Hi,

The whole point point of the release process is to:
1. Have legal overview by the PMC
2. Engage and involve the community

Why would we want to avoid either? As [1] says "Under no circumstances are 
unapproved builds a substitute for releases. If this policy seems inconvenient, 
then release more often."

I'd also note also at [1]:
"Deviations from this policy may have an adverse effect on the legal shield's 
effectiveness, or the insurance premiums Apache pays to protect officers and 
directors, so are strongly discouraged without prior, explicit board approval."

Thanks,
Justin

1. http://www.apache.org/dev/release.html
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Reply via email to