Re: Planning for emergency releases

On 10/08/2016 Patricia Shanahan wrote: On 8/9/2016 2:41 PM, Andrea Pescetti wrote: Patricia Shanahan wrote: How do we go about getting trained as release manager? By making a release, or two. If we only do two or three releases a year, we will only be able to train release managers are a

Re: Planning for emergency releases

On 8/12/2016 2:14 PM, Dennis E. Hamilton wrote: -Original Message- From: Patricia Shanahan [mailto:p...@acm.org] ... Personally, I would like to treat the last stable release as the base for emergency fixes. I started out suggesting using the current patch as an exercise to work

RE: Planning for emergency releases

> -Original Message- > From: Patricia Shanahan [mailto:p...@acm.org] > Sent: Friday, August 12, 2016 13:55 > To: dev@openoffice.apache.org > Subject: Re: Planning for emergency releases > > > > On 8/12/2016 1:40 PM, Dennis E. Hamilton wrote: > >

Re: Planning for emergency releases

On 8/12/2016 1:40 PM, Dennis E. Hamilton wrote: -Original Message- From: Patricia Shanahan [mailto:p...@acm.org] Sent: Thursday, August 11, 2016 11:07 To: dev@openoffice.apache.org Subject: Re: Planning for emergency releases [ ... ] Meanwhile, it is interesting for contemplating

RE: Planning for emergency releases

> -Original Message- > From: Patricia Shanahan [mailto:p...@acm.org] > Sent: Thursday, August 11, 2016 11:07 > To: dev@openoffice.apache.org > Subject: Re: Planning for emergency releases > [ ... ] > > Meanwhile, it is interesting for contemplating a ready-to-rele

Re: Planning for emergency releases

On 8/11/2016 10:45 AM, Marcus wrote: Am 08/10/2016 12:25 AM, schrieb Patricia Shanahan: On 8/9/2016 3:12 PM, Marcus wrote: ... we have a documented release process here [1]. Of course it's for a full release. But for a bugfix (or emergency) release it can be derived and then shortend. [1]

Re: Planning for emergency releases

Am 08/10/2016 12:25 AM, schrieb Patricia Shanahan: On 8/9/2016 3:12 PM, Marcus wrote: ... we have a documented release process here [1]. Of course it's for a full release. But for a bugfix (or emergency) release it can be derived and then shortend. [1]

Re: Planning for emergency releases

On 8/9/2016 3:12 PM, Marcus wrote: ... we have a documented release process here [1]. Of course it's for a full release. But for a bugfix (or emergency) release it can be derived and then shortend. [1] https://cwiki.apache.org/confluence/display/OOOUSERS/Release+Planning+Template That is the

Re: Planning for emergency releases

Am 08/09/2016 11:07 PM, schrieb Patricia Shanahan: On 8/9/2016 8:52 AM, Kay sch...@apache.org wrote: On 08/08/2016 09:26 PM, Patricia Shanahan wrote: On 8/8/2016 11:14 AM, Marcus wrote: Am 08/08/2016 07:28 PM, schrieb Andrea Pescetti: On 07/08/2016 Marcus wrote: Maybe we are not that

Re: Planning for emergency releases

On 8/9/2016 2:41 PM, Andrea Pescetti wrote: Patricia Shanahan wrote: How do we go about getting trained as release manager? By making a release, or two. If we only do two or three releases a year, we will only be able to train release managers are a rate of about two a year. Is that fast

Re: Planning for emergency releases

Patricia Shanahan wrote: How do we go about getting trained as release manager? By making a release, or two. Documenting the process in more detail? You can see the whole process documented everywhere (ASF pages and CWiki for the 4.1.2 release), but it's a matter of tooling at this stage

Re: Planning for emergency releases

On 8/9/2016 8:52 AM, Kay sch...@apache.org wrote: On 08/08/2016 09:26 PM, Patricia Shanahan wrote: On 8/8/2016 11:14 AM, Marcus wrote: Am 08/08/2016 07:28 PM, schrieb Andrea Pescetti: On 07/08/2016 Marcus wrote: Maybe we are not that far aways from each other. What I want to to avoid is

Re: Planning for emergency releases

On 08/08/2016 09:26 PM, Patricia Shanahan wrote: > On 8/8/2016 11:14 AM, Marcus wrote: >> Am 08/08/2016 07:28 PM, schrieb Andrea Pescetti: >>> On 07/08/2016 Marcus wrote: Maybe we are not that far aways from each other. What I want to to avoid is to provide hundreads of MBs for a

RE: Planning for emergency releases

> -Original Message- > From: Patricia Shanahan [mailto:p...@acm.org] > Sent: Monday, August 8, 2016 21:26 > To: dev@openoffice.apache.org > Subject: Re: Planning for emergency releases > > On 8/8/2016 11:14 AM, Marcus wrote: > > Am 08/08/2016 07:28

Re: Planning for emergency releases

On 8/8/2016 11:14 AM, Marcus wrote: Am 08/08/2016 07:28 PM, schrieb Andrea Pescetti: On 07/08/2016 Marcus wrote: Maybe we are not that far aways from each other. What I want to to avoid is to provide hundreads of MBs for a single fix. Of course we can do a 4.1.3 with some collected fixes. As I

RE: Planning for emergency releases

+1 on the permanent "ready to release" mode. > -Original Message- > From: Marcus [mailto:marcus.m...@wtnet.de] > Sent: Monday, August 8, 2016 11:15 > To: dev@openoffice.apache.org > Subject: Re: Planning for emergency releases > > Am 08/08/2016 07

Re: Planning for emergency releases

Am 08/08/2016 07:28 PM, schrieb Andrea Pescetti: On 07/08/2016 Marcus wrote: Maybe we are not that far aways from each other. What I want to to avoid is to provide hundreads of MBs for a single fix. Of course we can do a 4.1.3 with some collected fixes. As I don't know what is coming in the

Re: Planning for emergency releases

On 07/08/2016 Marcus wrote: Maybe we are not that far aways from each other. What I want to to avoid is to provide hundreads of MBs for a single fix. Of course we can do a 4.1.3 with some collected fixes. As I don't know what is coming in the future I would not love to see another 4.1.4, 4.1.5,

Re: Planning for emergency releases

Am 08/07/2016 07:38 PM, schrieb Dennis E. Hamilton: -Original Message- From: Marcus [mailto:marcus.m...@wtnet.de] Sent: Sunday, August 7, 2016 10:16 To: dev@openoffice.apache.org Subject: Re: Planning for emergency releases Am 08/07/2016 06:14 PM, schrieb Patricia Shanahan: On 8/7

Re: Planning for emergency releases

On 8/7/2016 10:16 AM, Marcus wrote: Am 08/07/2016 06:14 PM, schrieb Patricia Shanahan: ... but meanwhile work on getting competent at preparing a full release promptly if needed. Maybe we are not that far aways from each other. What I want to to avoid is to provide hundreads of MBs for a

RE: Planning for emergency releases

> -Original Message- > From: Marcus [mailto:marcus.m...@wtnet.de] > Sent: Sunday, August 7, 2016 10:16 > To: dev@openoffice.apache.org > Subject: Re: Planning for emergency releases > > Am 08/07/2016 06:14 PM, schrieb Patricia Shanahan: > > > >

Re: Planning for emergency releases

Am 08/07/2016 06:19 PM, schrieb Patricia Shanahan: On 8/7/2016 8:29 AM, Marcus wrote: Am 08/06/2016 12:57 AM, schrieb Patricia Shanahan: ... I don't agree with the car analogy - bits are relatively cheap, and I will personally promise to recycle any obsoleted bits that are returned to us,

Re: Planning for emergency releases

Am 08/07/2016 06:14 PM, schrieb Patricia Shanahan: On 8/7/2016 8:29 AM, Marcus wrote: ... I don't want to have it perfect. And we are already in this emergency situation. We have either a patch process nor a full-release process. We don't have what I consider to be the full emergency, a live

Re: Planning for emergency releases

On 8/7/2016 8:29 AM, Marcus wrote: Am 08/06/2016 12:57 AM, schrieb Patricia Shanahan: ... I don't agree with the car analogy - bits are relatively cheap, and I will personally promise to recycle any obsoleted bits that are returned to us, without taking up any landfill space. I would not do

Re: Planning for emergency releases

On 8/7/2016 8:29 AM, Marcus wrote: ... I don't want to have it perfect. And we are already in this emergency situation. We have either a patch process nor a full-release process. We don't have what I consider to be the full emergency, a live exploit in the field. Why not both strategies? Go

Re: Planning for emergency releases

Am 08/06/2016 12:57 AM, schrieb Patricia Shanahan: On 8/5/2016 2:20 PM, Marcus wrote: Am 08/05/2016 10:43 PM, schrieb Patricia Shanahan: This is mainly a summary of opinions I've already expressed on security@. The discussion does not actually involve anything that needs to be confidential, so

Re: Planning for emergency releases

Am 08/05/2016 11:59 PM, schrieb Dave Fisher: Until AOO can provide a simple auto-update that includes patches then from a user perspective Patricia is completely correct. I don't believe that this can be the only agrument to provide a full-blown release. ;-) Marcus On Aug 5, 2016, at

RE: Planning for emergency releases

> -Original Message- > From: Marcus [mailto:marcus.m...@wtnet.de] > Sent: Friday, August 5, 2016 14:21 > To: dev@openoffice.apache.org > Subject: Re: Planning for emergency releases > > Am 08/05/2016 10:43 PM, schrieb Patricia Shanahan: > > This is mainly

Re: Planning for emergency releases

On 8/5/2016 2:20 PM, Marcus wrote: Am 08/05/2016 10:43 PM, schrieb Patricia Shanahan: This is mainly a summary of opinions I've already expressed on security@. The discussion does not actually involve anything that needs to be confidential, so it should be taking place on dev@ instead. This

Re: Planning for emergency releases

Hi Marcus, Until AOO can provide a simple auto-update that includes patches then from a user perspective Patricia is completely correct. Regards, Dave Sent from my iPhone > On Aug 5, 2016, at 2:20 PM, Marcus wrote: > > Am 08/05/2016 10:43 PM, schrieb Patricia Shanahan:

Re: Planning for emergency releases

Am 08/05/2016 10:43 PM, schrieb Patricia Shanahan: This is mainly a summary of opinions I've already expressed on security@. The discussion does not actually involve anything that needs to be confidential, so it should be taking place on dev@ instead. This is controversial - I expect replies