Re: Writing up the release process
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: Bugzilla needs version 4.1.3 added
Marcus wrote: > Am 10/13/2016 09:34 PM, schrieb Keith N. McKenna: >> Marcus wrote: >>> Am 10/13/2016 08:18 PM, schrieb Keith N. McKenna: With the announcement of the Release of version 4.1.3 that revision should be added to Bugzilla so that bugs can be reported against it. Currently only 4.1.3-dev is active and for latest confirmation on the latest available is 4.1.2 >>> >>> right, I'll do this as next task. However, this needs definetely added >>> as important task to the cookbook. Will you do this? >>> >> Done > > and BZ is also updated. :-) > The version drop down list for the Latest Confirmation In field also needs to be updated with 4.1.3. Keith > Marcus > > > >>> https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release >>> >>> >>> You just need to add some text. Don't care about formatting or order. We >>> will do this later when everything (hopefully ;-) ) is there. >>> >>> Hey, it's a great idea when you would coordinate the creation of this >>> cookbook. Then you learn more about the whole process, can add opinions >>> from your point of view, etc. >>> >>> What do you think? signature.asc Description: OpenPGP digital signature
Re: Writing up the release process
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: Bugzilla needs version 4.1.3 added
Marcus wrote: > Am 10/13/2016 09:34 PM, schrieb Keith N. McKenna: >> Marcus wrote: >>> Am 10/13/2016 08:18 PM, schrieb Keith N. McKenna: With the announcement of the Release of version 4.1.3 that revision should be added to Bugzilla so that bugs can be reported against it. Currently only 4.1.3-dev is active and for latest confirmation on the latest available is 4.1.2 >>> >>> right, I'll do this as next task. However, this needs definetely added >>> as important task to the cookbook. Will you do this? >>> >> Done > > and BZ is also updated. :-) > > Marcus > > > >>> https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release >>> >>> >>> You just need to add some text. Don't care about formatting or order. We >>> will do this later when everything (hopefully ;-) ) is there. >>> >>> Hey, it's a great idea when you would coordinate the creation of this >>> cookbook. Then you learn more about the whole process, can add opinions >>> from your point of view, etc. >>> >>> What do you think? Great. Thanks Marcus. signature.asc Description: OpenPGP digital signature
Re: Writing up the release process
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: Eine offene Mail an die deutsche Community und die deutschen PMC-Vertreter
Hallo Michael, *, Sorry, aber ich muss etwas dazu sagen und deutlich werden, denn auch wenn Deine Antwort ja nicht falsch ist, ist sie doch so diplomatisch das sie den Kern der Probleme nur streift. > From: Dr. Michael Stehmann [mailto:anw...@rechtsanwalt-stehmann.de] > Ich sehe nicht, dass Mitglieder der deutschsprachigen Community an > verschiedenen Strängen zögen. Ich finde, dass die deutschsprachige > Community im Rahmen ihrer Möglichkeiten eine engagierte und > fruchtbringende Arbeit leistet. In lass mich gerne 'prügeln', aber mein Statement dazu ist: Nein, das ist nicht wirklich so, denn in Wahrheit steht hier ein halbes Dutzend Leute eher abwartend da, weil sie nicht konkret wissen was sie tun können und/oder mit den Rahmenbedingungen so unzufrieden sind das sie nur sporadisch etwas tun und zusätzlich schätze ich das nochmal ein Dutzend Leute diese Liste hier mitliest die wir zu Mitarbeit bewegen könnten wenn wir die Bedingungen verbessern. Überwiegend sind das alles Leute denen das Verständnis für den quasi besonderen Stil der Community-Arbeitsweise fehlt und darin kann ich sie verdammt gut verstehen, denn mir ging das ursprünglich mal genauso und das ich noh hier bin ist nur dem Zufall geschuldet das ich quasi persönliche Mentoren hatte (z.B. Thomas K. und Andre Sch.) > Ich sehe auch, dass das internationale Projekt bereit und willens ist, > Fehler, die in diesem ersten Release-Prozess in "Community-Hand" fast > notwendigerweise aufgetreten sind, festzustellen, um daraus für die > Zukunft zu lernen. > > Ich bin auch schon sehr gespannt auf die Dokumentation, die bereits in > Arbeit ist. Dabei ist bemerkenswert, dass es dort nicht nur technische > Fragen angesprochen werden. > > Es ist jetzt die Zeit, den Schwung, der durch den Ruck in der > Community > entstanden ist, auszunutzen. Wir haben nun etwas in der Hand, auf das > wir, wenn man die Umstände sieht, unter denen es entstehen > musste, stolz > sein können. Wenn es so weiterläuft, werden wir bald das > nächste Release > haben, bei dem wir alles besser machen können. Das sind alles Aussagen die für die internationale Liste passen, aber für hier zu ungenau sind. Es tut mir wirklich leid, nur ohne jede weitere Umschweife: das Problem das wir (und potentiell alle lokalen AOO-Communities) haben ist die unzureichende Selbstständigkeit und die Tatsache das wir der internationalen Klärung dieser Frage seit Jahren ausweichen. (und wie wenig ich hierbei eigentlich Apache an Schuld zuweise, hatte ich schon in meinem anderen Post thematisiert) Ich habe überhaupt nicht die Absicht hier und heute Streit zu beginnen, allein bitte ich in aller Ernsthaftigkeit dieses Problem doch endlich einmal ernsthaft wahrzunehmen. Wie weitgehend wir diesbezüglich etwas verbessern können wird sich zeigen, nur weiterhin so zu tun als gäbe es das Problem nicht, heisst nichts Anderes als das bei de-AOO alles weiterhin nur auf Sparflamme kochen wird wie bisher. Deinen (Michael) persönlichen Einsatz für de-AOO kritisiere ich im Übrigen überhaupt nicht, aber ich bitte doch nun mal um Ernsthaftigkeit z.B. bei der Beurteilung das Deine und Mechthildes Messeauftritte (und gelegentliche Auftritte der ProOO-Box) nicht andeutungsweise das repräsenieren wozu früher, bei de-OOo, die Community ganz selbstverständlich in der Lage war. Da hilft auch keine Entschuldigung das wir heute weniger Leute sind, denn das wir das überhaupt sind hat ja gerade mit nicht optimalen Bedingungen zu tun, Bedingungen die wir selbst gestalten, für die wir (moralisch) verantwortlich sind. Gruß Jörg - To unsubscribe, e-mail: dev-de-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-de-h...@openoffice.apache.org
Re: AOO 4.1.3 announce - pt-BR translation
Am 10/13/2016 03:42 PM, schrieb Claudio Ferreia Filho: I don't know how is your strategy to publish the translations, but IMHO they can be added in the announce at Apache Blog. as we'll have more translated text we've created a container page to collect all. See the link at top of the announcement [1]. Anyway, the pt-BR translation is published at cwiki[1],as a child page. [1]https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65875077 I've set a link to your translation on the Portuguese webpage [2]. The big blue link in the header. Congratulations for all by more one step in AOO. Thanks a lot. :-) [1] https://s.apache.org/JiCT [2] http://www.openoffice.org/pt/ 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
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: AOO 4.1.3 announce - pt-BR translation
Thanks, Andrea --DONE! Warm regards,Sally From: Andrea PescettiTo: dev@openoffice.apache.org; sally Khudairi Sent: Thursday, October 13, 2016 4:57 PM Subject: Re: AOO 4.1.3 announce - pt-BR translation Claudio Ferreia Filho wrote: > I don't know how is your strategy to publish the translations, but IMHO > they can be added in the announce at Apache Blog. Sally, could you please add a "Translations" link at the beginning of your post https://blogs.apache.org/foundation/entry/the_apache_openoffice_project_announces and let it point at https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3+Announcement where we are storing translations? (see the dev list archives if you need more context, but this is all we need at the moment) Thanks, Andrea.
Re: [CWiki] Account Whitelisting
Joerg Sievers wrote: jogi Joerg Sievers Whitelisted. Andrea - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO 4.1.3 announce - pt-BR translation
Claudio Ferreia Filho wrote: I don't know how is your strategy to publish the translations, but IMHO they can be added in the announce at Apache Blog. Sally, could you please add a "Translations" link at the beginning of your post https://blogs.apache.org/foundation/entry/the_apache_openoffice_project_announces and let it point at https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3+Announcement where we are storing translations? (see the dev list archives if you need more context, but this is all we need at the moment) Thanks, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Bugzilla needs version 4.1.3 added
Am 10/13/2016 09:34 PM, schrieb Keith N. McKenna: Marcus wrote: Am 10/13/2016 08:18 PM, schrieb Keith N. McKenna: With the announcement of the Release of version 4.1.3 that revision should be added to Bugzilla so that bugs can be reported against it. Currently only 4.1.3-dev is active and for latest confirmation on the latest available is 4.1.2 right, I'll do this as next task. However, this needs definetely added as important task to the cookbook. Will you do this? Done and BZ is also updated. :-) Marcus https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release You just need to add some text. Don't care about formatting or order. We will do this later when everything (hopefully ;-) ) is there. Hey, it's a great idea when you would coordinate the creation of this cookbook. Then you learn more about the whole process, can add opinions from your point of view, etc. What do you think? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: This can not be true
Am 10/13/2016 09:12 AM, schrieb Andrea Pescetti: Jörg Schmidt wrote: no reasonable planning takes place. How can it be that even though *there was a help offer for the translation*, a press release is simply published in English without coordinating internationally? I agree with Joerg here. We did it for the release notes, and we can do it for the announcements (Press releases) too. Two thing must be said: there was no time for coordination since the press release had been accidentally made available before the planned date; and the press release is traditionally kept confidential before issuing it (while the Release notes are not). Still, I agree that translation volunteers must be given access to the Press Release so that they can translate it and issue it soon after the English one. We must make sure to do so starting with the next release. I'm sorry when something was not understood. I got the request from Joerg (and Dick for Dutch) to translate it press release. However, there was not hint that we should wait until this is ready. I really didn't thought that this was important. We will add this task to the cookbook and consider it for the next release. Again, I'm sorry when the timing was not perfectly coordinated. https://blogs.apache.org/foundation/entry/the_apache_openoffice_project_announces Joerg, what if we create a copy of the Press Release on the CWiki and we append each translation as child page? Would it work? I'm going to do the same for Italian as soon as I have some time for it. And then we will edit the English blog post to link to translations. That's for sure a good idea. Then we can link to the translated text. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Bugzilla needs version 4.1.3 added
Marcus wrote: > Am 10/13/2016 08:18 PM, schrieb Keith N. McKenna: >> With the announcement of the Release of version 4.1.3 that revision >> should be added to Bugzilla so that bugs can be reported against it. >> Currently only 4.1.3-dev is active and for latest confirmation on the >> latest available is 4.1.2 > > right, I'll do this as next task. However, this needs definetely added > as important task to the cookbook. Will you do this? > Done > https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release > > You just need to add some text. Don't care about formatting or order. We > will do this later when everything (hopefully ;-) ) is there. > > Hey, it's a great idea when you would coordinate the creation of this > cookbook. Then you learn more about the whole process, can add opinions > from your point of view, etc. > > What do you think? > > Thanks > > Marcus signature.asc Description: OpenPGP digital signature
Re: AOO 4.1.3 announced on en-Forum
Am 10/13/2016 03:23 PM, schrieb FR web forum: I've announced on fr-Forum and modified index.html on fr website. Somebody can commit this page? Thanks - Mail original - De: "Rory O'Farrell"À: dev@openoffice.apache.org Envoyé: Jeudi 13 Octobre 2016 10:49:56 Objet: AOO 4.1.3 announced on en-Forum I have posted a sticky announcement of the availability of AOO 4.1.3 on the en-Forum, advising to use only the main download site and its redirection. Also in the posting is a link to the release announcement. please have a look. I can see 4.1.3 on the "index.html" now. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: Eine offene Mail an die deutsche Community und die deutschen PMC-Vertreter
Moin Claudia, damit meine ich nicht Deine Frage. > -Original Message- > From: C. Wiebe [mailto:clad...@gmail.com] > Sent: Thursday, October 13, 2016 9:23 PM > To: dev-de@openoffice.apache.org > Subject: Re: Eine offene Mail an die deutsche Community und die deutschen > PMC-Vertreter > > Meinst Du mich wg. meiner Frage oder die Apachis Claudia Wiebe > clad...@gmail.com Am 13.10.2016 um 21:06 schrieb Jan-Christian Wienandt: > > Moin Jörg, > > > > > > … denn sie wissen nicht, was sie tun > > > > Gruß > > Jan > > > > > > - > > To unsubscribe, e-mail: dev-de-unsubscr...@openoffice.apache.org > > For additional commands, e-mail: dev-de-h...@openoffice.apache.org > > > > > - > To unsubscribe, e-mail: dev-de-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-de-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-de-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-de-h...@openoffice.apache.org
Re: Eine offene Mail an die deutsche Community und die deutschen PMC-Vertreter
Meinst Du mich wg. meiner Frage oder die Apachis Claudia Wiebe clad...@gmail.com Am 13.10.2016 um 21:06 schrieb Jan-Christian Wienandt: Moin Jörg, … denn sie wissen nicht, was sie tun Gruß Jan - To unsubscribe, e-mail: dev-de-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-de-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-de-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-de-h...@openoffice.apache.org
RE: Eine offene Mail an die deutsche Community und die deutschen PMC-Vertreter
Moin Jörg, … denn sie wissen nicht, was sie tun Gruß Jan - To unsubscribe, e-mail: dev-de-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-de-h...@openoffice.apache.org
Re: Bugzilla needs version 4.1.3 added
Marcus wrote: > Am 10/13/2016 08:18 PM, schrieb Keith N. McKenna: >> With the announcement of the Release of version 4.1.3 that revision >> should be added to Bugzilla so that bugs can be reported against it. >> Currently only 4.1.3-dev is active and for latest confirmation on the >> latest available is 4.1.2 > > right, I'll do this as next task. However, this needs definetely added > as important task to the cookbook. Will you do this? > > https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release > > You just need to add some text. Don't care about formatting or order. We > will do this later when everything (hopefully ;-) ) is there. > > Hey, it's a great idea when you would coordinate the creation of this > cookbook. Then you learn more about the whole process, can add opinions > from your point of view, etc. > > What do you think? > > Thanks > > Marcus Can do for both. Keith signature.asc Description: OpenPGP digital signature
Re: Release Archives
Am 10/13/2016 08:38 PM, schrieb Matthias Seidel: Small glitch: http://openoffice.apache.org/downloads.html "Release Archives" the "Current Version 4.1.2" should be renamed to "Apache OpenOffice 4.1.2" thanks for the hint. It'll be fixed together with more 4.1.3 changes this evening. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Bugzilla needs version 4.1.3 added
Am 10/13/2016 08:18 PM, schrieb Keith N. McKenna: With the announcement of the Release of version 4.1.3 that revision should be added to Bugzilla so that bugs can be reported against it. Currently only 4.1.3-dev is active and for latest confirmation on the latest available is 4.1.2 right, I'll do this as next task. However, this needs definetely added as important task to the cookbook. Will you do this? https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release You just need to add some text. Don't care about formatting or order. We will do this later when everything (hopefully ;-) ) is there. Hey, it's a great idea when you would coordinate the creation of this cookbook. Then you learn more about the whole process, can add opinions from your point of view, etc. What do you think? Thanks Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Release Archives
Small glitch: http://openoffice.apache.org/downloads.html "Release Archives" the "Current Version 4.1.2" should be renamed to "Apache OpenOffice 4.1.2" regards Matthias smime.p7s Description: S/MIME Cryptographic Signature
Re: Writing up the release process
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
Bugzilla needs version 4.1.3 added
With the announcement of the Release of version 4.1.3 that revision should be added to Bugzilla so that bugs can be reported against it. Currently only 4.1.3-dev is active and for latest confirmation on the latest available is 4.1.2 Regards Keith signature.asc Description: OpenPGP digital signature
Re: "Latest version" on Sourceforge
Am 10/13/2016 07:20 PM, schrieb Matthias Seidel: Thanks! This should definitely go into the release instructions... actually it is, but it's not in the right order. Therefore I've overlooked it yesterday. This needs to be changed for the next release. I've now changed the default. Thanks Marcus Am 13.10.2016 um 19:17 schrieb Dave Brondsema: On 10/13/16 1:11 PM, Rory O'Farrell wrote: On Thu, 13 Oct 2016 18:57:14 +0200 Matthias Seidelwrote: The "latest version" on https://sourceforge.net/projects/openofficeorg.mirror/files/ is still pointing to 4.1.2. I think this had to be set manually on sourceforge... regards Matthias Clear your browser cache and 4.1.3 will show up. I took the liberty of changing this just a few minutes ago. It would be good to include this in the release instructions. After making the folder unstaged, just go into the subdirs and click the "i" icon for the Mac release, and mark it as default. Repeat for Windows& Linux. Other types don't really matter too much. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: "Latest version" on Sourceforge
On 10/13/16 1:11 PM, Rory O'Farrell wrote: > On Thu, 13 Oct 2016 18:57:14 +0200 > Matthias Seidelwrote: > >> The "latest version" on >> https://sourceforge.net/projects/openofficeorg.mirror/files/ is still >> pointing to 4.1.2. >> >> I think this had to be set manually on sourceforge... >> >> regards >> >> Matthias >> > > Clear your browser cache and 4.1.3 will show up. > I took the liberty of changing this just a few minutes ago. It would be good to include this in the release instructions. After making the folder unstaged, just go into the subdirs and click the "i" icon for the Mac release, and mark it as default. Repeat for Windows & Linux. Other types don't really matter too much. -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming <>< - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: "Latest version" on Sourceforge
Thanks! This should definitely go into the release instructions... Am 13.10.2016 um 19:17 schrieb Dave Brondsema: > On 10/13/16 1:11 PM, Rory O'Farrell wrote: >> On Thu, 13 Oct 2016 18:57:14 +0200 >> Matthias Seidelwrote: >> >>> The "latest version" on >>> https://sourceforge.net/projects/openofficeorg.mirror/files/ is still >>> pointing to 4.1.2. >>> >>> I think this had to be set manually on sourceforge... >>> >>> regards >>> >>> Matthias >>> >> Clear your browser cache and 4.1.3 will show up. >> > I took the liberty of changing this just a few minutes ago. > > It would be good to include this in the release instructions. After making > the > folder unstaged, just go into the subdirs and click the "i" icon for the Mac > release, and mark it as default. Repeat for Windows & Linux. Other types > don't > really matter too much. > > smime.p7s Description: S/MIME Cryptographic Signature
Re: "Latest version" on Sourceforge
That was not the point, the directory was visible... But now the link is OK! ;-) Am 13.10.2016 um 19:11 schrieb Rory O'Farrell: > On Thu, 13 Oct 2016 18:57:14 +0200 > Matthias Seidelwrote: > >> The "latest version" on >> https://sourceforge.net/projects/openofficeorg.mirror/files/ is still >> pointing to 4.1.2. >> >> I think this had to be set manually on sourceforge... >> >> regards >> >> Matthias >> > Clear your browser cache and 4.1.3 will show up. > smime.p7s Description: S/MIME Cryptographic Signature
Re: "Latest version" on Sourceforge
On Thu, 13 Oct 2016 18:57:14 +0200 Matthias Seidelwrote: > The "latest version" on > https://sourceforge.net/projects/openofficeorg.mirror/files/ is still > pointing to 4.1.2. > > I think this had to be set manually on sourceforge... > > regards > > Matthias > Clear your browser cache and 4.1.3 will show up. -- Rory O'Farrell - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
"Latest version" on Sourceforge
The "latest version" on https://sourceforge.net/projects/openofficeorg.mirror/files/ is still pointing to 4.1.2. I think this had to be set manually on sourceforge... regards Matthias smime.p7s Description: S/MIME Cryptographic Signature
[CWiki] Account Whitelisting
jogi Joerg Sievers signature.asc Description: OpenPGP digital signature
AOO 4.1.3 announce - pt-BR translation
Hi I don't know how is your strategy to publish the translations, but IMHO they can be added in the announce at Apache Blog. Anyway, the pt-BR translation is published at cwiki[1],as a child page. [1]https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65875077 Congratulations for all by more one step in AOO. Regards, Claudio Ferreira
Re: AOO 4.1.3 announced on en-Forum
I've announced on fr-Forum and modified index.html on fr website. Somebody can commit this page? Thanks - Mail original - De: "Rory O'Farrell"À: dev@openoffice.apache.org Envoyé: Jeudi 13 Octobre 2016 10:49:56 Objet: AOO 4.1.3 announced on en-Forum I have posted a sticky announcement of the availability of AOO 4.1.3 on the en-Forum, advising to use only the main download site and its redirection. Also in the posting is a link to the release announcement. Rory -- Rory O'Farrell - 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
> On Oct 12, 2016, at 6:05 PM, Patricia Shanahanwrote: > > 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: This can not be true
Jörg Schmidt wrote: From: Andrea Pescetti Joerg, what if we create a copy of the Press Release on the CWiki and we append each translation as child page? Would it work? Yes, that would be a possibility. Page created at https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.3+Announcement ; people interested in translating it can add a child page for their language. 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
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: This can not be true
+1 Andrea Pescettischrieb am Do., 13. Okt. 2016, 09:12: > Jörg Schmidt wrote: > > no reasonable planning takes place. > > How can it be that even though *there was a help offer for the > translation*, a press release is simply published in English without > coordinating internationally? > > I agree with Joerg here. We did it for the release notes, and we can do > it for the announcements (Press releases) too. > > Two thing must be said: there was no time for coordination since the > press release had been accidentally made available before the planned > date; and the press release is traditionally kept confidential before > issuing it (while the Release notes are not). > > Still, I agree that translation volunteers must be given access to the > Press Release so that they can translate it and issue it soon after the > English one. We must make sure to do so starting with the next release. > > > > https://blogs.apache.org/foundation/entry/the_apache_openoffice_project_announces > > Joerg, what if we create a copy of the Press Release on the CWiki and we > append each translation as child page? Would it work? I'm going to do > the same for Italian as soon as I have some time for it. And then we > will edit the English blog post to link to translations. > > Regards, >Andrea. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > -- Disclaimer: Diese Nachricht stammt aus einem Google Account. Ihre Antwort wird in der Google Cloud Gespeichert und durch Google Algorythmen zwecks werbeanaöysen gescannt. Es ist derzeit nicht auszuschließen das ihre Nachricht auch durch einen NSA Mitarbeiter geprüft wird. Durch kommunikation mit diesen Account stimmen Sie zu das ihre Mail, ihre Kontaktdaten und die Termine die Sie mit mir vereinbaren online zu Google konditionen in der Googlecloud gespeichert wird. Sollten sie dies nicht wünschen kontaktieren sie mich bitte Umgehend um z.B. alternativen zu verhandeln.
AOO 4.1.3 announced on en-Forum
I have posted a sticky announcement of the availability of AOO 4.1.3 on the en-Forum, advising to use only the main download site and its redirection. Also in the posting is a link to the release announcement. Rory -- Rory O'Farrell- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: This can not be true
On 10/12/2016 11:55 PM, Jörg Schmidt wrote: Hello Apache, Hello OpenOffice-PMC, Hello Community, I am absolutely horrified that in a situation where we have to overcome problems together, no reasonable planning takes place. I have started a Wiki page on "How to Cook a Release", https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release, so that we will know everything that needs to be done and how to do it. That should reduce the risk of something important getting missed. I'm adding a section on Translations. What documents, other than the release notes and the press release, should be translated? How can it be that even though *there was a help offer for the translation*, a press release is simply published in English without coordinating internationally? How could appear the following article (which is supposed to be a press release) without waiting for possible translations? https://blogs.apache.org/foundation/entry/the_apache_openoffice_project_announces I disagree with this approach. Jörg - 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: This can not be true
Hello, > From: Andrea Pescetti [mailto:pesce...@apache.org] > Two thing must be said: there was no time for coordination since the > press release had been accidentally made available before the planned > date; and the press release is traditionally kept confidential before > issuing it (while the Release notes are not). > > Still, I agree that translation volunteers must be given > access to the > Press Release so that they can translate it and issue it soon > after the > English one. Exactly, that is the problem. I am ready to make a translation as quickly as possible, but I need practically at least 24-48 hours of time. > Joerg, what if we create a copy of the Press Release on the > CWiki and we > append each translation as child page? Would it work? Yes, that would be a possibility. I have little time, because of my professional activity, but I will try to make the translation as fast as possible. I think within 48 hours. Greetings, Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: This can not be true
Jörg Schmidt wrote: no reasonable planning takes place. How can it be that even though *there was a help offer for the translation*, a press release is simply published in English without coordinating internationally? I agree with Joerg here. We did it for the release notes, and we can do it for the announcements (Press releases) too. Two thing must be said: there was no time for coordination since the press release had been accidentally made available before the planned date; and the press release is traditionally kept confidential before issuing it (while the Release notes are not). Still, I agree that translation volunteers must be given access to the Press Release so that they can translate it and issue it soon after the English one. We must make sure to do so starting with the next release. https://blogs.apache.org/foundation/entry/the_apache_openoffice_project_announces Joerg, what if we create a copy of the Press Release on the CWiki and we append each translation as child page? Would it work? I'm going to do the same for Italian as soon as I have some time for it. And then we will edit the English blog post to link to translations. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
This can not be true
Hello Apache, Hello OpenOffice-PMC, Hello Community, I am absolutely horrified that in a situation where we have to overcome problems together, no reasonable planning takes place. How can it be that even though *there was a help offer for the translation*, a press release is simply published in English without coordinating internationally? How could appear the following article (which is supposed to be a press release) without waiting for possible translations? https://blogs.apache.org/foundation/entry/the_apache_openoffice_project_announces I disagree with this approach. Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org