AOO 4.1.6 Release Planning - release Manager
Thanks very much Kay. We should select a release Manager. Are there any volunteers? All the Best Peter Ursprüngliche Nachricht Von: "Kay Schenk (Confluence)" Gesendet: 12. August 2018 23:00:02 MESZ An: legi...@gmail.com Betreff: [CONF] Apache OpenOffice Community > AOO 4.1.6 Release Planning There's 1 new edit on this page AOO 4.1.6 Release Planning Kay Schenk edited this page Here's what changed: The purpose of the following table is to provide a schedule plan for a new release planning. It is desired for a new major release (x.y like 4.1) but it could be also used for a minor release (x.y.z like 4.1.1). Phases and steps in scheduleDateResponsibleCommentFeature freeze Start ?Committer Announce it on dev@, qa@, l10n@ ?Release Manager Update version / milestone / build ID data in SVN e.g., "4.1.0" --> "4.2.0" ?Developer Create new branch in SVN for the new release ?Developer Create Release Notes (RN) in Confluence Wiki Use page name like "AOO+X.Y.Z+Release+Notes Example: AOO 4.0.1 Release Notes ?Committer String freeze Start ?NL community Update RN with new languages ?Release Manager Announce it on dev@, qa@, l10n@ ?Release Manager Translation phase Changes in strings for the application UI and Help as well as for dictionaries Start ?NL community End ?NL community Announce it on dev@, qa@, l10n@ ?Release Manager Code freeze Start ?Committer Start release blocker mode (aka show stopper mode) ?Release Manager Commit changes to reflect the upcoming release: Version number, build ID, build date+time, copyright year ?Release Manager Update all bundled dictionaries ?L10N list Update RN with latest changes ?All people Announce it on dev@, qa@, l10n@ ?Release Manager Beta ReleaseDateResponsibleComment Build the RC ?Release Manager Update Wiki page to make the files available Development Snapshot Build Make sure the files have the correct access permissions ?Release Manager Start vote ?Release Manager Announce vote on dev@, qa@, l10n@ ?Release Manager Start Beta testing phase ?QA Update RN with latest changes ?All people Start translating RN ?NL community Announce it on dev@ (+ qa@, l10n@) ?Release Manager End Beta testing phase ?QA Announce vote results on dev@ (+ qa@, l10n@) ?Release Manager Upload files to Apache Dist/SourceForge Make sure to set the staging bit for the Beta directory ?Release Manager Update download scripting – javascript files in /download See [1] in the next table below for details ?Committer Remind the release blocker mode Announce it on dev@, qa@, l10n@ ?Release Manager Release CandidateDateResponsibleComment Build the RC ?Release Manager Update Wiki page to make the files available Development Snapshot Builds Make sure the files have the correct access permissions Update devbuilds.html ?Release Manager Start vote ?Release Manager Announce vote on dev@, qa@, l10n@ ?Release Manager Start RC testing phase ?QA Update RN with latest changes ?All people Update translating RN ?NL community Announce it on dev@ (+ qa@, l10n@) ?Release Manager End RC testing phase ?QA End vote (date *and* time in UTC timezone) ?Release Manager Announce vote results on dev@ (+ qa@, l10n@) ?Release Manager General Availability DateResponsibleComment Prepare Upload files to Apache Dist/SourceForge Make sure to set the staging bit for the RC directory ?Release Manager Update download scripting See [2] in the next table below for details ?Committer Verify RN if all is correct ?All people Public Announcement of GA Announce it on announce@, dev@ ?Release Manager Update feeds Supply dummy file for next release version Use input files and scripts from: http://svn.apache.org/viewvc/openoffice/devtools/genUpdateFeed/ ? Committer After release job Update data in Bugzilla: Add/modify values for: "Version", "Target milestone", "Release blocker flag", "Last Confirmation on" ?BZ Admin Update version / milestone / build ID data in SVN: e.g., "4.1.0" --> "4.2.0" ?Developer Update "www.openoffice.org" homepage: Create new blog and/or news entry Update news entry on homepage Update headline below the logo ?Committer Update DOAP file: https://svn.apache.org/repos/asf/openoffice/site/trunk/content/openoffice.rdf ?Committer Create a "kid" build: This helpful and often asked for translation testing. Announce it on dev@, qa@, l10n@ ?Release Manager Commit update feeds Commit generated feeds to appropriate areas: http://svn.apache.org/viewvc/openoffice/updates-site/trunk/ ?Committer [1] Beta Release: Update download scripting (main download area) Object properties / variables Value exampleComment "globalvars.js": Add the new version data, BETA_VERSION BETA_NAME BETA_MILESTONE
Re: IBM Plex font
Hi Carl, Am 11.08.2018 um 19:24 schrieb Carl Marcum: > Hi Matthias, > > > On 08/09/2018 11:55 AM, Matthias Seidel wrote: >> Hi all, >> >> IBM Plex font [1] is a real nice looking font type. >> >> Apart from that, it is now dual-licensed under OFL and Apache >> license. [2] >> >> I am wondering if we could include it in OpenOffice? >> >> Regards, >> >> Matthias >> >> [1] https://www.ibm.com/plex/ >> [2] https://github.com/IBM/plex/issues/190#issuecomment-411801246 >> >> > > It does look nice and it looks like IBM put a lot into it. Yes, and they are constantly improving it... Regards, Matthias > > I'm in favor of including it. > > Thanks for bring it up. > > Best regards, > Carl > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
Fwd: RE: Rights of use for business
Forwarding to Jonathan too. Ursprüngliche Nachricht Von: "Jörg Schmidt" Gesendet: 12. August 2018 09:59:25 MESZ An: dev@openoffice.apache.org Betreff: RE: Rights of use for business > From: Jonathan Farrow [mailto:jonathanalexanderfar...@gmail.com] > Sent: Sunday, August 12, 2018 1:51 AM > To: dev@openoffice.apache.org > Subject: Rights of use for business > > Hello, > > I have a question. Can I use Open Office as a professional business > application such as using the spread sheets so that I can > keep track of my > business orders and such legally? yes, of course. Apache OpenOffice is free software, including commercial use. greetings. 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: IBM Plex font
What should a font bring to be worth added to Open Office? Am 12. August 2018 11:40:07 MESZ schrieb Marcus : >Am 10.08.2018 um 03:41 schrieb Fernando Cassia: >> On 8/9/18, Marcus wrote: >>> >>> even when it looks nice, is great with scaling and also compatible >with >>> the AL, I'm wondering what a good purpose could be? Adding a new >font >>> without any reason would just increase the install size about some >>> megabytes (when I see this right at [1]). >>> >>> [1] https://github.com/IBM/plex/releases/tag/v1.1.3 >>> >> [...] >> >> I just downloaded TrueType.zip from the github project page, >> decompressed it to its own subfolder, and recompressed it to 7zip >> format using p7zip -mx9 (maximum compression). The resulting packaged >> size is 2MB >> >> 2MB doesn´t seem like a killer size increase to me... > >sure, but where should we draw the line? At 5 or 10 MB? IMHO every >addition - that increases the install base - should have a reason. > >Adding a font just because it's nice looking or compatible with our >license is not enough. > >My 2 ct. > >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: IBM Plex font
Am 10.08.2018 um 03:41 schrieb Fernando Cassia: On 8/9/18, Marcus wrote: even when it looks nice, is great with scaling and also compatible with the AL, I'm wondering what a good purpose could be? Adding a new font without any reason would just increase the install size about some megabytes (when I see this right at [1]). [1] https://github.com/IBM/plex/releases/tag/v1.1.3 [...] I just downloaded TrueType.zip from the github project page, decompressed it to its own subfolder, and recompressed it to 7zip format using p7zip -mx9 (maximum compression). The resulting packaged size is 2MB 2MB doesn´t seem like a killer size increase to me... sure, but where should we draw the line? At 5 or 10 MB? IMHO every addition - that increases the install base - should have a reason. Adding a font just because it's nice looking or compatible with our license is not enough. My 2 ct. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: IBM Plex font
Am 11.08.2018 um 17:13 schrieb Andrea Pescetti: On 10/08/2018 Matthias Seidel wrote: Am 10.08.2018 um 00:13 schrieb Keith N. McKenna: On 8/9/2018 11:55 AM, Matthias Seidel wrote: I am wondering if we could include it in OpenOffice? [1] https://www.ibm.com/plex/ My question would be like Marcus's; What purpose are we serving by adding it to the distribution. I already have a plethora of fonts installed that I will never use. If someone wants it it can be downloaded for free. OK, point taken. It could still be a good exercise to add it to trunk as a test, so that we can check what the size increase actually is and revisit that part of OpenOffice. Then, if there is no special benefit and the size increase is too much, we can always remove it, but I see some value (meaning: some knowledge gain) in trying even if in the end we decide not to keep it. for testing purpose What-Happens-If... it would be OK also for me. However, even when it's just a few megabytes I don't see any real need when we keep the font in the repo. Please note: It's always starting with "just this", then other things come along ... and this ... and this ... ;-) Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: Rights of use for business
> From: Jonathan Farrow [mailto:jonathanalexanderfar...@gmail.com] > Sent: Sunday, August 12, 2018 1:51 AM > To: dev@openoffice.apache.org > Subject: Rights of use for business > > Hello, > > I have a question. Can I use Open Office as a professional business > application such as using the spread sheets so that I can > keep track of my > business orders and such legally? yes, of course. Apache OpenOffice is free software, including commercial use. greetings. Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Rights of use for business
Hello, I have a question. Can I use Open Office as a professional business application such as using the spread sheets so that I can keep track of my business orders and such legally? Please let me know. Thanks! Jonathan Farrow
