I have offered, on the PMC mailing list, to learn to be a release
manager if necessary or desirable. The more people we have who can do a
role, the better the chances of someone being available when needed.
However, I would have to function as keeper-of-the-checklist, and depend
on everyone doing what they can towards a release.
For example, I own three Apple computers, two iPhones and an Apple II.
None of those are good candidates for building AOO. :-)
I do think we should position ourselves to do a point release very
quickly if necessary to fix a security exploit that is out in the field
and affecting users. I hope that never happens, but if it does...
Patricia
On 3/17/2016 1:00 PM, Pedro Giffuni wrote:
Hello;
I don't know (or care) what donaldupre meant by that "holacracy"
thing but the ASF does have clear governance structures.
Concerning a Release Manager I found this:
http://www.apache.org/dev/release-publishing.html#release_manager
"The common practice at Apache is for a single individual to take
responsibility for the mechanics of a release."
Note that that common practice doesn't make it mandatory (although
pretty much a hint in the right direction). However the link also
states:
"Release managers do the work of pushing out releases. However, release
managers are not ultimately responsible."
I brought the subject the release management being done by a group of
people before the previous release based on some older document from
the apache httpd project, I will not repeat again that idea, but I think
that instead of focusing on find ing one brave sould to do everything,
the community would do better to focus on a *group* doing things.
If one person bears all the responsibilities including building for Mac,
Windows and Linux then it is going to be increasingly difficult
to find a new release manager each time.
What is also increasingly clear to me is that a release won't happen
immediately soon, even when technically we would be ready for one.
Pedro.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
