Hi Dennis,
comments below..
On 01/30/2016 12:17 PM, Dennis E. Hamilton wrote:
[BCC AOO PMC]
Carl, I notice that you are running two concurrent proposals.
Personally, I am conflicted about this.
I think this is admirable and worthy work. However, it is going to Maven as
effectively a distribution from the project, and that implies an associated
release. At the same time, we really want this to be a low-friction process.
The lurking question is, what is the minimum that needs to be done to satisfy
the ASF-important ceremonial requirements. See
<http://apache.org/dev/release.html>.
I'm told there are projects where the PMCs use lazy consensus. AOO has never
been one of them and the existing policies and practices do introduce a level
of formality for what are AOO releases.
If we were to conduct a release vote, it would be necessary to have a majority
of binding +1 votes by a margin of 3. That means basically that there is
enough information for folks to independently review the source and confirm
that the specified build process works. That also means, by the way, that
there is a source-only release packaging with no included jars, etc., that
there are external digests and digital signatures by the release manager (i.e.,
you), and there staging somewhere as a release candidate.
I am copying the PMC on this and requesting that all discussion be here, and
not there, so all committers and interested parties can contribute to the
discussion. We would also need to know that at least 3 PMC members are
prepared to carry out what is required for casting a binding release vote.
While we wrestle with this, I request that you suspend the Groovy UNO Extension
discussion for now and we continue this for the simple case of the Java
Bootstrap Connector. I am assuming that this is the simpler case to work
through a release process if we determine that we need to do so.
- Dennis
[cmarcum]
No problem.
I suspended the Groovy UNO extension proposal.
My hope was to do this through the project but I understand the
procedures and how this could cause more work for others than necessary
since it's only a small developer tool and not a primary project artifact.
I am more than willing to submit this individually if it makes more sense.
In a larger sense this conversation could also apply to the future
builds of the AOO-Netbeans plugin that is made available through
NetBeans.org.
Best regards,
Carl
-----Original Message-----
From: Carl Marcum [mailto:cmar...@apache.org]
Sent: Saturday, January 30, 2016 06:42
To: dev@openoffice.apache.org
Subject: [PROPOSAL][DEVTOOLS] Stage Java BootstrapConnector to Maven
Repository
Hi All,
I would like to create Maven bundles of the source, classes, and javadoc
of the recently added BootstrapConnector [1] and stage them on the
Apache Nexus Maven Repository using groupId "org.openoffice" so this
would be from the project.
If the project consensus is that a VOTE is necessary I will call for one
after staging and prior to publishing, or if not, I will do another
PROPOSAL for release.
This jar allows bootstrapping the office by passing a string
representing the path to the office executable to the bootstrap method.
This code has been available for download from the Forum since 2008 [2].
I have obtained permission from the author to use the code by our
project and under the AL 2.0 license and documented it with the AOO PMC.
If there are no objections to the above proposal by midnight GMT
Wednesday February 3rd, then I will invoke Lazy Consensus and proceed
to implement the above proposal.
Another option to this is that I publish them as an individual with a
different groupId if this is preferred.
[1]
https://svn.apache.org/repos/asf/openoffice/devtools/bootstrap-
connector/trunk/
[2] https://forum.openoffice.org/en/forum/viewtopic.php?t=2520
Thanks,
Carl
---------------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
