Re: Writing up the release process

2016-10-20 Thread John D'Orazio 
I can confirm that opening Open Office today, without going into Tools or
other, I automatically received after about a minute the notification of
the new update available for version 4.1.3.

On Tue, Oct 18, 2016 at 9:16 AM, Andrea Pescetti 
wrote:

> Marcus wrote:
>
>> You may want to review the text as there are some typos in the last
>> sentence. ;-)
>>
>
> Thanks, there were some copy/paste issues. Keith already fixed the text a
> bit, and I've now edited it again. By the way, translators might want to
> update their localized version (they should have received a notification
> mail with details of changed text anyway).
>
> Regards,
>   Andrea.
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>


-- 
John R. D'Orazio

Re: Writing up the release process

2016-10-18 Thread Andrea Pescetti 

Marcus wrote:

You may want to review the text as there are some typos in the last
sentence. ;-)


Thanks, there were some copy/paste issues. Keith already fixed the text 
a bit, and I've now edited it again. By the way, translators might want 
to update their localized version (they should have received a 
notification mail with details of changed text anyway).


Regards,
  Andrea.

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

Re: Writing up the release process

2016-10-17 Thread Marcus 

Am 10/17/2016 11:16 PM, schrieb Andrea Pescetti:

On 15/10/2016 Marcus wrote:

Am 10/14/2016 09:01 AM, schrieb Andrea Pescetti:

Keith N. McKenna wrote:

Pedro wrote:

Currently version 4.1.2 still reports that it "is up to date" ...

The change to the update script is usually done several days after...

I plan to update script data during the weekend.

+1


This is now done, only for 4.1.2 to 4.1.3;


it's working.

Check via "Tools - Options - OpenOffice - Online Update" and click on 
[Check now]. In the following dialog my 4.1.2 installation shows an 
update notice for 4.1.3 and the [Downlod] button refers to the download 
webpage.


> I'll later do all 4.x.y to

4.1.3, but this is likely to be a minority of users. So all OpenOffice
4.1.2 users are now expected to receive a notification depending on
their OpenOffice settings (monthly notification, weekly notification,
daily notification, never).


Yes, that can be set later. But it should be done to really reach every 
user.



The delay was caused by a need for updating the Release notes to explain
better how to circumvent Gatekeeper in the new Mac OS X Sierra - the
instructions we had applied to older versions only.


You may want to review the text as there are some typos in the last 
sentence. ;-)


Thanks for the update work.

Marcus


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

Re: Writing up the release process

2016-10-17 Thread Andrea Pescetti 

On 15/10/2016 Marcus wrote:

Am 10/14/2016 09:01 AM, schrieb Andrea Pescetti:

Keith N. McKenna wrote:

Pedro wrote:

Currently version 4.1.2 still reports that it "is up to date" ...

The change to the update script is usually done several days after...

I plan to update script data during the weekend.

+1


This is now done, only for 4.1.2 to 4.1.3; I'll later do all 4.x.y to 
4.1.3, but this is likely to be a minority of users. So all OpenOffice 
4.1.2 users are now expected to receive a notification depending on 
their OpenOffice settings (monthly notification, weekly notification, 
daily notification, never).


The delay was caused by a need for updating the Release notes to explain 
better how to circumvent Gatekeeper in the new Mac OS X Sierra - the 
instructions we had applied to older versions only.


Regards,
  Andrea.

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

Re: Writing up the release process

2016-10-15 Thread Marcus 

Am 10/14/2016 09:01 AM, schrieb Andrea Pescetti:

Keith N. McKenna wrote:

Pedro wrote:

Currently version 4.1.2 still reports that it "is up to date"

I have added the your comment to the cwiki document. The change to the
update script is usually done several days after the formal Release
announcement so as to minimize the load on the mirrors.


I confirm this is the case. I plan to update script data during the
weekend.


+1

In the past we have waited a longer time (IMHO 1 -2 weeks). But to get 
the good news out to the world fast, I would do an except here.


Marcus


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

Re: Writing up the release process

2016-10-14 Thread Pedro 



On 14-10-2016 08:01, Andrea Pescetti wrote:

Keith N. McKenna wrote:

Pedro wrote:

Currently version 4.1.2 still reports that it "is up to date"

I have added the your comment to the cwiki document. The change to the
update script is usually done several days after the formal Release
announcement so as to minimize the load on the mirrors.


I confirm this is the case. I plan to update script data during the 
weekend.


Thank you both for your answers.
Even without the notice the downloads at Sourceforge are already 
growing...


Regards,
Pedro

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

Re: Writing up the release process

2016-10-14 Thread Andrea Pescetti 

Keith N. McKenna wrote:

Pedro wrote:

Currently version 4.1.2 still reports that it "is up to date"

I have added the your comment to the cwiki document. The change to the
update script is usually done several days after the formal Release
announcement so as to minimize the load on the mirrors.


I confirm this is the case. I plan to update script data during the weekend.

Regards,
  Andrea.

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

Re: Writing up the release process

2016-10-13 Thread Keith N. McKenna 
Pedro wrote:
> One last step needed: update the version number somewhere so that
> current OpenOffice users are warned that a new version is available.
> Currently version 4.1.2 still reports that it "is up to date"
> 
> Thank you all for keeping the project alive.

I have added the your comment to the cwiki document. The change to the
update script is usually done several days after the formal Release
announcement so as to minimize the load on the mirrors.

regards
Keith
> 




signature.asc
Description: OpenPGP digital signature

Re: Writing up the release process

2016-10-13 Thread Pedro 
One last step needed: update the version number somewhere so that 
current OpenOffice users are warned that a new version is available. 
Currently version 4.1.2 still reports that it "is up to date"


Thank you all for keeping the project alive.

On 12/10/2016 22:49, Patricia Shanahan wrote:
First, congratulations to everyone on releasing 4.1.3. If this were a 
conventional, co-located project I'd like to take you all out for a 
drink after work.


Now back to work :-)

At this moment, I hope everyone remembers exactly what they did, what 
karma and tools they used, to make the release happen. I would like to 
get that written up now, before steps get forgotten. That way, future 
release managers will be not be as helpless and confused as I was.


I'm thinking of creating "How to cook a release" as a child page under 
https://cwiki.apache.org/confluence/display/OOOUSERS/Releases, but 
given my inability to delete pages I would like to get opinions first.


My general idea is to keep it initially free-form. Just add what you 
did, and how you did it, before you forget anything. I can organize it 
later, or maybe a technical writer will organize it?


We can use the 4.1.4 release to verify and fix any omissions in the 
recipe.


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




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

Re: Writing up the release process

2016-10-13 Thread Keith N. McKenna 
Andrea Pescetti wrote:
> Keith N. McKenna wrote:
>> Can you restore my space admin privileges on the Cwiki. I had removed
>> all but my basic privileges.
> 
> Sure! I've now given you all permissions I could assign. I hope this is
> enough; if not, we must contact Infra (but it seems that I could assign
> the space admin permissions so it should be OK now).
> 
> Regards,
>   Andrea.
They are all back Andrea. Thank you very much.




signature.asc
Description: OpenPGP digital signature

Re: Writing up the release process

2016-10-13 Thread Andrea Pescetti 

Keith N. McKenna wrote:

Can you restore my space admin privileges on the Cwiki. I had removed
all but my basic privileges.


Sure! I've now given you all permissions I could assign. I hope this is 
enough; if not, we must contact Infra (but it seems that I could assign 
the space admin permissions so it should be OK now).


Regards,
  Andrea.

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

Re: Writing up the release process

2016-10-13 Thread Keith N. McKenna 
Andrea Pescetti wrote:
> Patricia Shanahan wrote:
 I'm thinking of creating "How to cook a release" as a child page under
 https://cwiki.apache.org/confluence/display/OOOUSERS/Releases, but
 given
 my inability to delete pages I would like to get opinions first.
> 
> You can now delete pages. and in general, if people do not have enough
> permissions to do their tasks, this must be fixed the obvious way, i.e.,
> by granting those permissions.
> 
>> https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release
>>
>> If anyone has material but cannot edit the page, just e-mail me your
>> notes and I'll add it.
> 
> ...or, again, just ask for permissions to edit pages here and they will
> be granted. You need an account first.
> https://cwiki.apache.org/confluence/display/OOOUSERS/Wiki+Home explains
> what you need to do.
> 
> Regards,
>   Andrea.
Can you restore my space admin privileges on the Cwiki. I had removed
all but my basic privileges. User name is keith.mcke...@comcast.net

Thanks
Keith



signature.asc
Description: OpenPGP digital signature

Re: Writing up the release process

2016-10-13 Thread Jim Jagielski 

> On Oct 12, 2016, at 6:05 PM, Patricia Shanahan  wrote:
> 
> On 10/12/2016 2:55 PM, Marcus wrote:
>> Am 10/12/2016 11:49 PM, schrieb Patricia Shanahan:
>>> First, congratulations to everyone on releasing 4.1.3. If this were a
>>> conventional, co-located project I'd like to take you all out for a
>>> drink after work.
>>> 
>>> Now back to work :-)
>>> 
>>> At this moment, I hope everyone remembers exactly what they did, what
>>> karma and tools they used, to make the release happen. I would like to
>>> get that written up now, before steps get forgotten. That way, future
>>> release managers will be not be as helpless and confused as I was.
>>> 
>>> I'm thinking of creating "How to cook a release" as a child page under
>>> https://cwiki.apache.org/confluence/display/OOOUSERS/Releases, but given
>>> my inability to delete pages I would like to get opinions first.
>> 
>> JFDI ;-)
> 
> Done. 
> https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release
> 
> If anyone has material but cannot edit the page, just e-mail me your notes 
> and I'll add it.

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

Re: Writing up the release process

2016-10-13 Thread Andrea Pescetti 

Patricia Shanahan wrote:

I'm thinking of creating "How to cook a release" as a child page under
https://cwiki.apache.org/confluence/display/OOOUSERS/Releases, but given
my inability to delete pages I would like to get opinions first.


You can now delete pages. and in general, if people do not have enough 
permissions to do their tasks, this must be fixed the obvious way, i.e., 
by granting those permissions.



https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release
If anyone has material but cannot edit the page, just e-mail me your
notes and I'll add it.


...or, again, just ask for permissions to edit pages here and they will 
be granted. You need an account first. 
https://cwiki.apache.org/confluence/display/OOOUSERS/Wiki+Home explains 
what you need to do.


Regards,
  Andrea.

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

Re: Writing up the release process

2016-10-12 Thread Patricia Shanahan 

On 10/12/2016 2:55 PM, Marcus wrote:

Am 10/12/2016 11:49 PM, schrieb Patricia Shanahan:

First, congratulations to everyone on releasing 4.1.3. If this were a
conventional, co-located project I'd like to take you all out for a
drink after work.

Now back to work :-)

At this moment, I hope everyone remembers exactly what they did, what
karma and tools they used, to make the release happen. I would like to
get that written up now, before steps get forgotten. That way, future
release managers will be not be as helpless and confused as I was.

I'm thinking of creating "How to cook a release" as a child page under
https://cwiki.apache.org/confluence/display/OOOUSERS/Releases, but given
my inability to delete pages I would like to get opinions first.


JFDI ;-)


Done. 
https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release


If anyone has material but cannot edit the page, just e-mail me your 
notes and I'll add it.





My general idea is to keep it initially free-form. Just add what you
did, and how you did it, before you forget anything. I can organize it
later, or maybe a technical writer will organize it?


Yes, no big formatting for the start. Just write down what you all did.
Even the chronological and/or logical order can be done afterwards. The
most important part are really the working steps itself.


We can use the 4.1.4 release to verify and fix any omissions in the
recipe.


I think we have to. ;-)

Marcus


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



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

Re: Writing up the release process

2016-10-12 Thread Marcus 

Am 10/12/2016 11:49 PM, schrieb Patricia Shanahan:

First, congratulations to everyone on releasing 4.1.3. If this were a
conventional, co-located project I'd like to take you all out for a
drink after work.

Now back to work :-)

At this moment, I hope everyone remembers exactly what they did, what
karma and tools they used, to make the release happen. I would like to
get that written up now, before steps get forgotten. That way, future
release managers will be not be as helpless and confused as I was.

I'm thinking of creating "How to cook a release" as a child page under
https://cwiki.apache.org/confluence/display/OOOUSERS/Releases, but given
my inability to delete pages I would like to get opinions first.


JFDI ;-)


My general idea is to keep it initially free-form. Just add what you
did, and how you did it, before you forget anything. I can organize it
later, or maybe a technical writer will organize it?


Yes, no big formatting for the start. Just write down what you all did. 
Even the chronological and/or logical order can be done afterwards. The 
most important part are really the working steps itself.



We can use the 4.1.4 release to verify and fix any omissions in the recipe.


I think we have to. ;-)

Marcus


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