Re: Release process and 4.1.3

2016-09-10 Thread Andrea Pescetti 

Patricia Shanahan wrote:

I just created an account, user name "pats".


Whitelisted.

Andrea

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

Re: Release process and 4.1.3

2016-09-10 Thread Patricia Shanahan 



On 9/10/2016 7:02 AM, Andrea Pescetti wrote:

Patricia Shanahan wrote:

On 9/9/2016 12:11 AM, Andrea Pescetti wrote:

Actually, 4.1.2 was exactly this. Your starting point should thus be
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.2 ; just
copy the wiki page and edit/generalize accordingly.

Can you give me a pointer to how to copy and edit confluence pages?


At first you need to login (top right); you need a whitelisted account,
so if the following instructions do not work we have to whitelist it
(create the account first; then give us the username and we will
whitelist it).



I just created an account, user name "pats".

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

Re: Release process and 4.1.3

2016-09-09 Thread Andrea Pescetti 

Patricia Shanahan wrote:

https://cwiki.apache.org/confluence/display/OOOUSERS/Release+Planning+Template
It is what I would want to do for a major release with user interface
changes.


Yes, that one is the template for a 4.2.0, not for a 4.1.3 release.


We also need something far, far more agile for getting simple bug fix
releases out quickly and easily. I propose using 4.1.3 as a test case
for a stripped down process.


Actually, 4.1.2 was exactly this. Your starting point should thus be 
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.2 ; just 
copy the wiki page and edit/generalize accordingly.



No string changes means we do not need the "String freeze" or
"Translation phase" steps. No significant changes to external
interfaces, combined with a small number of relatively simple fixes,
eliminates the "Beta Release" phase.


This is the difference between a "micro" (third digit) and a "minor" 
(second digit) release. Calling it 4.1.3 implies all of this, barring 
exceptional situations.



We still need to pick the bug fixes to go in the release, construct a
release candidate, test it, write release notes etc.


This is all covered in the link I sent. There might be some steps that 
need better clarification though.


Regards,
  Andrea.

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

Re: Release process and 4.1.3

2016-09-08 Thread Phillip Rhodes 
On Thu, Sep 8, 2016 at 10:05 PM, Patricia Shanahan  wrote:

> We also need something far, far more agile for getting simple bug fix
> releases out quickly and easily. I propose using 4.1.3 as a test case for a
> stripped down process.
>

+1


Phil
~~
This message optimized for indexing by NSA PRISM

Release process and 4.1.3

2016-09-08 Thread Patricia Shanahan 
I've looked at the Release Planning Template, 
https://cwiki.apache.org/confluence/display/OOOUSERS/Release+Planning+Template


It is what I would want to do for a major release with user interface 
changes.


We also need something far, far more agile for getting simple bug fix 
releases out quickly and easily. I propose using 4.1.3 as a test case 
for a stripped down process. Alternatively, this can be regarded as 
adding binary distribution to the normal way ASF projects release.


The minimal process will be suitable for releases containing only a 
small set of bug fix changes that do not require any changes or 
additions to externally displayed strings, and do not make significant 
changes to the external interface.


No string changes means we do not need the "String freeze" or 
"Translation phase" steps. No significant changes to external 
interfaces, combined with a small number of relatively simple fixes, 
eliminates the "Beta Release" phase.


We still need to pick the bug fixes to go in the release, construct a 
release candidate, test it, write release notes etc.








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