openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis E. Hamilton" <>
Subject RE: Release Manager for 4.2.0?
Date Fri, 02 Sep 2016 16:05:29 GMT
I don't have a good place to put this, and 4.2.0 may not be the way to consider it, if we are
also counting on an early (this year) 4.2.0 to also provide important maintenance fixes and
any security catch-ups too.

One major change that the TDF made to LibreOffice is very important.  Instead of producing
complete binary sets (Windows x86, MacOSX, Linux32, and Linux64) for *each* localization,
LibreOffice provides one complete set for *all* localizations.  The off-line Help is only
in English, but localized off-line Helps can be obtained as small downloads.  The on-line
helps reached by default are localized.

You can imagine how this simplifies deployment, including QA and binding votes.  They have
also been using Windows .msi binaries, with Microsoft's signing method, for some time.

Somehow, it would be good to have a checklist of the kinds of things that we would like to
try and confirm using rebuilds of a stable version, not just for emergency releases.  There
are a number of deployment improvements that could be tested and QA'd that way without worrying
about regressions inside of a feature release.

Just a thought.

 - Dennis

> -----Original Message-----
> From: Patricia Shanahan []
> Sent: Friday, August 19, 2016 11:30
> To:
> Subject: Re: Release Manager for 4.2.0?
> On 8/19/2016 10:41 AM, Kay wrote:
> >
> > On 01/28/2016 04:06 PM, Andrea Pescetti wrote:
> >> As I wrote a few day ago, in theory it would be good to release
> >> OpenOffice 4.2.0 in February. If it happens a bit later it wouldn't
> be a
> >> big issue, but I believe that, in the constant balance between
> periods
> >> where we are focused on talks (internal to OpenOffice and with the
> >> enlarged community) and periods where we are more focused on the
> >> OpenOffice product, it's time to start working again towards a
> release.
> >>
> >> For 4.2.0 we need a Release Manager. I would prefer NOT to be the
> >> Release Manager for 4.2.0 since I'm finding that in this period I can
> >> help more productively with tasks that do not require constant
> >> interaction than with tasks that require a constant monitoring of
> >> project channels.
> >>
> >> I am surely available to have a significant role in the 4.2.0
> release,
> >> especially with getting localization working again (actually, this
> mail
> >> also serves as announcement that I am going to ask for higher
> privileges
> >> on the Pootle server in order to check the translation workflow); but
> if
> >> someone else steps in as a Release Manager we could deliver earlier.
> >>
> >> So if anyone is interested feel free to discuss this on list, or to
> >> contact me off-list if you prefer, or to discuss in person at FOSDEM
> >> next weekend!
> >>
> >> Regards,
> >>   Andrea.
> >>
> >
> > Hi all--
> >
> > I am volunteering to be release manager for 4.2.0.  I have been
> involved
> > in all the AOO releases since 3.40, and I'm familiar with the process.
> > Like all of us involved with the project, I am a volunteer. Due to
> this,
> > I can not provide an expected release date. Releases, as we know are
> > community efforts. We'll release when we feel 4.2.0 is ready.
> >
> > So, I will let this offer stand the weekend just in case someone else
> > feels they'd LOVE to do this. If we don't have any objections to my
> > being the next release manager over the next 72 hours, we can get
> > started next week ironing out what needs to be done. We will need LOTS
> > of help!
> This looks ideal to me. I would like to learn the release processes, and
> try to document them as completely as possible. I would prefer to learn
> by watching and helping someone who already knows how it is done, than
> by jumping in the deep end and splashing about.
> I have an agenda of constructing an emergency release procedure but it
> will be easier if I can first see how the normal process goes.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message