Re: [DISCUSS] 4.1.4 Release Manager?

+1 :) Keith N. McKenna schrieb am Mo., 3. Okt. 2016, 18:09: > Ariel Constenla-Haile wrote: > > On Thu, Sep 29, 2016 at 03:58:11PM -0700, Patricia Shanahan wrote: > >> There are now release blocker requests for 4.1.4, so we need a release > >> manager to decide on

Re: [DISCUSS] 4.1.4 Release Manager?

Am 09/30/2016 07:15 PM, schrieb Andrea Pescetti: Ariel Constenla-Haile wrote: On Thu, Sep 29, 2016 at 03:58:11PM -0700, Patricia Shanahan wrote: There are now release blocker requests for 4.1.4, so we need a release manager to decide on them. If nobody steps in, and/or nobody has any

Re: [DISCUSS] 4.1.4 Release Manager?

On 9/30/2016 10:15 AM, Andrea Pescetti wrote: Ariel Constenla-Haile wrote: On Thu, Sep 29, 2016 at 03:58:11PM -0700, Patricia Shanahan wrote: There are now release blocker requests for 4.1.4, so we need a release manager to decide on them. If nobody steps in, and/or nobody has any objection,

Re: [DISCUSS] 4.1.4 Release Manager?

Ariel Constenla-Haile wrote: On Thu, Sep 29, 2016 at 03:58:11PM -0700, Patricia Shanahan wrote: There are now release blocker requests for 4.1.4, so we need a release manager to decide on them. If nobody steps in, and/or nobody has any objection, you can count with me. I would be very happy

Re: [DISCUSS] 4.1.4 Release Manager?

On Thu, Sep 29, 2016 at 03:58:11PM -0700, Patricia Shanahan wrote: > There are now release blocker requests for 4.1.4, so we need a release > manager to decide on them. If nobody steps in, and/or nobody has any objection, you can count with me. Regards -- Ariel Constenla-Haile signature.asc

[DISCUSS] 4.1.4 Release Manager?

There are now release blocker requests for 4.1.4, so we need a release manager to decide on them. I am reluctant to be release manager for 4.1.4, because I will have limited Internet access, and no access to my home computers, from December 15th to January 8th. I will be packing immediately

Re: 4.1.4 Release Manager?

I do not know. How much time there is for one to do. I have to ask people. Marcus schrieb am Mo., 19. Sep. 2016, 19:36: > Am 09/19/2016 08:27 AM, schrieb Peter Kovacs: > > The idea for the Phönix Motiv is ment as a statement. And IMHO has most > > drama on 4.1.3 release. >

Re: 4.1.4 Release Manager?

Am 09/19/2016 08:27 AM, schrieb Peter Kovacs: The idea for the Phönix Motiv is ment as a statement. And IMHO has most drama on 4.1.3 release. Today Xing (Germans linkid social media ) posted the article from ZDF.de (Germans 2nd state TV station) about the upcoming death of open office.

Re: 4.1.4 Release Manager?

The idea for the Phönix Motiv is ment as a statement. And IMHO has most drama on 4.1.3 release. Today Xing (Germans linkid social media ) posted the article from ZDF.de (Germans 2nd state TV station) about the upcoming death of open office. Referring Dennis email about the idea of retirement for

Re: 4.1.4 Release Manager?

On 9/18/2016 12:14 AM, Marcus wrote: Am 09/18/2016 07:45 AM, schrieb Peter Kovacs: Hmm, does anyone know an artist that has some time and can draw a splash screen? I would love to see the next edition Called 4.1.3 Phoenix addition, And I would love to see a Splashscreen that shows an Phönix

Re: 4.1.4 Release Manager?

Am 09/18/2016 07:45 AM, schrieb Peter Kovacs: Hmm, does anyone know an artist that has some time and can draw a splash screen? I would love to see the next edition Called 4.1.3 Phoenix addition, And I would love to see a Splashscreen that shows an Phönix carry the AOOo Logo upward. That would

Re: 4.1.4 Release Manager?

Hmm, does anyone know an artist that has some time and can draw a splash screen? I would love to see the next edition Called 4.1.3 Phoenix addition, And I would love to see a Splashscreen that shows an Phönix carry the AOOo Logo upward. That would make a statement. Actually thinking of it, if

Re: 4.1.4 Release Manager?

> From: Marcus [mailto:marcus.m...@wtnet.de] > > (b) > > Or you choose a more formal type of label them. > > OK, "AOO XP" would probably not so great, but what would > be, for example, with > > "AOO NE" (for new experience)? > > From the view point of a normal user I find it confusing as >

Re: 4.1.4 Release Manager?

Am 09/16/2016 02:07 PM, schrieb Jörg Schmidt: From: Jim Jagielski [mailto:j...@jagunet.com] Any real reason to name it 4.2.0 ? Two years of miscellaneous changes and fixes, a radically improved build system, unit tests at build time, updates of a lot of libraries, support for new

Re: 4.1.4 Release Manager?

> From: Dr. Michael Stehmann [mailto:anw...@rechtsanwalt-stehmann.de] > What's about AOO 42? ;-) indeed, that would be an interesting play on words Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For

Re: 4.1.4 Release Manager?

> From: Jim Jagielski [mailto:j...@jagunet.com] > >> Any real reason to name it 4.2.0 ? > > > > Two years of miscellaneous changes and fixes, a radically > improved build system, unit tests at build time, updates of a > lot of libraries, support for new languages, new > translations, new

Re: 4.1.4 Release Manager?

Am 16.09.2016 um 13:19 schrieb Jim Jagielski: >> Jim Jagielski wrote: >>> Any real reason to name it 4.2.0 ? >> >> Two years of miscellaneous changes and fixes, a radically improved build >> system, unit tests at build time, updates of a lot of libraries, support for >> new languages, new

Re: 4.1.4 Release Manager?

> On Sep 15, 2016, at 5:01 PM, Andrea Pescetti wrote: > > Jim Jagielski wrote: >> Any real reason to name it 4.2.0 ? > > Two years of miscellaneous changes and fixes, a radically improved build > system, unit tests at build time, updates of a lot of libraries, support for

Re: 4.1.4 Release Manager?

On Thu, Sep 15, 2016 at 09:14:33PM +0200, Marcus wrote: > Am 09/15/2016 05:44 PM, schrieb Pedro Giffuni: > >I am rather amazed by the idea of 4.1.4, shouldn't we release > >4.2.0 instead? I mean ... > > > >- I thought the idea behind 4.1.3 was to make a quick fix for > >4.1.2 and to give more time

Re: 4.1.4 Release Manager?

Jim Jagielski wrote: Any real reason to name it 4.2.0 ? Two years of miscellaneous changes and fixes, a radically improved build system, unit tests at build time, updates of a lot of libraries, support for new languages, new translations, new dictionaries... if this is not 4.2.0 it should

Re: 4.1.4 Release Manager?

Am 09/15/2016 09:30 PM, schrieb Jim Jagielski: Any real reason to name it 4.2.0 ? as I don't know what your intention of this short sentence is, I feel that also short answer like "Yes, of course" is maybe not helping. ;-) The only alternative would be 5.0. Sure, we have many code changes

Re: 4.1.4 Release Manager?

Am 09/15/2016 09:59 PM, schrieb Jorg Schmidt: From: Dave Fisher [mailto:dave2w...@comcast.net] Sent: Thursday, September 15, 2016 9:05 PM To: dev@openoffice.apache.org Subject: Re: 4.1.4 Release Manager? The strategy behind 4.1.3 and 4.1.4 is this:. (1) Quick releases of important bug fixes

Re: 4.1.4 Release Manager?

On 9/15/2016 12:59 PM, Jorg Schmidt wrote: From: Dave Fisher [mailto:dave2w...@comcast.net] Sent: Thursday, September 15, 2016 9:05 PM To: dev@openoffice.apache.org Subject: Re: 4.1.4 Release Manager? The strategy behind 4.1.3 and 4.1.4 is this:. (1) Quick releases of important bug fixes

Re: 4.1.4 Release Manager?

> From: Dave Fisher [mailto:dave2w...@comcast.net] > Sent: Thursday, September 15, 2016 9:05 PM > To: dev@openoffice.apache.org > Subject: Re: 4.1.4 Release Manager? > > The strategy behind 4.1.3 and 4.1.4 is this:. > > (1) Quick releases of important bug fixes especiall

Re: 4.1.4 Release Manager?

I believe we should always have a point release, based on the last fully stable and released version, ready for code check-in: Release manager identified, branch created, release-blocker flags created. That shortens the latency from identifying an urgent fix to having the fix in our users'

Re: 4.1.4 Release Manager?

Any real reason to name it 4.2.0 ? > On Sep 15, 2016, at 3:25 PM, Phillip Rhodes wrote: > > I like this idea... 4.1.3 and 4.1.4 in the near-term, and then 4.2.0 in > early 2017. Feels like a good rhythm to aim for. > > Phil > > On Sep 15, 2016 15:14, "Marcus"

Re: 4.1.4 Release Manager?

I like this idea... 4.1.3 and 4.1.4 in the near-term, and then 4.2.0 in early 2017. Feels like a good rhythm to aim for. Phil On Sep 15, 2016 15:14, "Marcus" wrote: > Am 09/15/2016 05:44 PM, schrieb Pedro Giffuni: > >> I am rather amazed by the idea of 4.1.4, shouldn't

Re: 4.1.4 Release Manager?

The strategy behind 4.1.3 and 4.1.4 is this:. (1) Quick releases of important bug fixes especially related to security. (2) quickly building release manager skills. We became overly dependent on people who are no longer with us. (3) establishing a regular cadence. If you both want to work

Re: 4.1.4 Release Manager?

Am 09/15/2016 05:44 PM, schrieb Pedro Giffuni: I am rather amazed by the idea of 4.1.4, shouldn't we release 4.2.0 instead? I mean ... - I thought the idea behind 4.1.3 was to make a quick fix for 4.1.2 and to give more time for the 4.2.0 release process. - the code in trunk has over two years

Re: 4.1.4 Release Manager?

+1 On 9/15/2016 12:04 PM, Dave Fisher wrote: The strategy behind 4.1.3 and 4.1.4 is this:. (1) Quick releases of important bug fixes especially related to security. (2) quickly building release manager skills. We became overly dependent on people who are no longer with us. (3) establishing a

Re: 4.1.4 Release Manager?

On Thu, Sep 15, 2016 at 5:44 PM, Pedro Giffuni wrote: > Hi Patricia; > > I am rather amazed by the idea of 4.1.4, shouldn't we release > 4.2.0 instead? I mean ... +1. We absolutely should. - To unsubscribe,

Re: 4.1.4 Release Manager?

Hi Patricia; I am rather amazed by the idea of 4.1.4, shouldn't we release 4.2.0 instead? I mean ... - I thought the idea behind 4.1.3 was to make a quick fix for 4.1.2 and to give more time for the 4.2.0 release process. - the code in trunk has over two years of development and is more

4.1.4 Release Manager?

Any volunteers for 4.1.4 Release Manager? It would be better to have someone else do it: Cross-training - part of our troubles may have been due to depending on one or two people for particular roles. Distraction - I need to keep my focus on pushing 4.1.3 out as soon as possible. Schedule