openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis E. Hamilton" <orc...@apache.org>
Subject RE: [PROPOSAL][DEVTOOLS] Stage Java BootstrapConnector to Maven Repository
Date Mon, 08 Feb 2016 19:46:03 GMT
> -----Original Message-----
> From: Carl Marcum [mailto:cmarcum@apache.org]
> Sent: Friday, February 5, 2016 03:56
> To: dev@openoffice.apache.org
> Subject: Re: [PROPOSAL][DEVTOOLS] Stage Java BootstrapConnector to Maven
> Repository
> 
> On 02/04/2016 03:48 PM, Dennis E. Hamilton wrote:
 [ ... ]
> >   1. You could put together a release, using a tagged/branched piece
> of the AOO SVN sufficient to what you want to do.  So there's a
> persistent source-tree location and r-number that nails it down.
> >
> >   2. Then you could take that much through the release process, being
> the release manager yourself.  It might be awkward the first time,
> making it beneficial that this is a pretty simple addition.  After that
> effort, and presumably without more than 2 release candidates, the issue
> will be having a binding +1 majority of at least three to accomplish the
> release.
> >
> >   3. Being able to obtain a release vote that includes binding voters
> successfully building from the released source is a little worrisome.
> My suggestion is to go through (2) regardless, but I am not doing the
> work [;<).  If all technical objections are satisfied, and it is simply
> a lack of votes, my personal recommendation would be to do a downstream
> release relying on the release bundle, but having it be dependent on AOO
> code, as identified, but not being an AOO release.  The problem is then
> how that is that to be identified so there is no confusion with an AOO
> release.
> >
> > That's a lot of armchair quarter-backing.
> >
> > What are your further thoughts on this, Carl?  Bueller?
> >
> >   - Dennis
> 
> Hi Dennis,
> 
> I understand how the recently released Java UNO jar to Maven needed to
> coincide with a AOO release due to the source being in AOO source.
> 
> For devtools like this bootstrap connector and the netbeans-integration
> plugin, their source is under the devtools dir which is beside AOO trunk
> and therefore not branched and tagged with AOO I don't believe.
> 
> For the netbeans plugin submitted to NetBeans.org, past releases by my
> were discussed on dev@ and then by lazy-concensus proposal.  with it's
> own trunk, branches, and tags directory structure.
> 
> Could this not be similar?
> 
[orcmid] 

Made me look!

Well, being in the AOO SVN but under devtools/ and separate from the AOO trunk/, branches/
and tags/ source trees is perfect.

I do think we need to treat releases as releases though, since we're talking about publishing
in public, if I understand it, and that is different than work-in-progress and experimentation.

I think the Apache Release process should be applied.  

I see you've been busy there.  Is what you are doing aligned with that prospect?

I think releasing will also get more attention to this work.

If release fails for non-technical but procedural reasons, that is not on you and there are
always alternatives in that case.

 - Dennis

> Thanks,
> Carl
> 
[ ... ]


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org


Mime
View raw message