Re: Post-release steps for 4.1.4
Matthias Seidel wrote: But knowing that now one thing comes to my mind: If we *would* enable permanent redirection to HTTPS for the website, we may have to exclude http://installation.openoffice.org/description otherwise it would break the update feed? No, this is not a problem. It is not a real URL. See it more as a string, like if it was "TheOpenOfficeUpdateFeedSchema". Historically a URL is used for this purpose, but it can be an invented URL like http://the.openoffice.update.feed.schema since nobody uses it as a URL. I think https://www.w3schools.com/xml/xml_namespaces.asp gives a good explanation, summarized as follows: - The namespace URI is not used by the parser to look up information. - The purpose of using an URI is to give the namespace a unique name. - However, companies often use the namespace as a pointer to a web page containing namespace information. Actually, until a few years ago the URL was not existing at all (if one clicked on it a 404 would appear). Then we decided to put something at the URL. But the reason it broke is simply that the string changed: the fact that it looks like a URL is irrelevant in this respect. OK, I will add German and French then, leaving Mac out. Tomorrow (or Monday?) all remaining languages will follow (without Mac). OK, good plan. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Post-release steps for 4.1.4
Am 28.10.2017 um 22:12 schrieb Andrea Pescetti: > Matthias Seidel wrote: >> Am 28.10.2017 um 20:07 schrieb Andrea Pescetti: >>> You didn't only look around, you committed stuff and I'll now try to >>> review it. But yes, I confirm that one is the tool we use. >> >> Only small changes for https... I couldn't resist! ;-) > > OK, no problem! But as you will see in > http://svn.apache.org/viewvc/openoffice/devtools/genUpdateFeed/ > (besides the duplicated record for "he" that invalidated the feed but, > I assume, was just due to not noticing that we had it already) there > is an important lesson to learn about HTTPS. > > When this is meant for a human using an ordinary browser, indeed we > can do the change and if somebody feels this is better and more > secure, no objections to doing so. > > When this is meant for a program, though, we must make sure that > things will still work. In this case, switching to HTTPS broke since > the XML namespace (which looks like a URL, but is not meant to be > browsed) changed and OpenOffice was no longer able to recognize it, so > my 4.1.3 was not finding the update. There is absolutely no advantage > in changing XML namespaces to HTTPS, they are not real URLs and the > only effect in changing them will be that OpenOffice won't detect the > updates any longer. I kept the HTTPS in download URL instead: with our > current model, we ask the user to open a browser anyway, so this won't > break. Sorry for my mistakes... But knowing that now one thing comes to my mind: If we *would* enable permanent redirection to HTTPS for the website, we may have to exclude http://installation.openoffice.org/description otherwise it would break the update feed? I am not really sure about that, but we should have an eye on it... > >>> Let's do this: I'll push the update feeds for Italian 4.1.3 only, >>> within a couple hours, just to check that everything still works the >>> way it should; then I'll leave you free to take over. >> OK, I would then proceed according to your list. > > Italian done. Actually I decided to keep Mac on hold, since I'd like > to know more about https://bz.apache.org/ooo/show_bug.cgi?id=127568 > before pushing the update to all users. If others feel the same, we > can keep Mac notifications pending for the time being. OK, I will add German and French then, leaving Mac out. Tomorrow (or Monday?) all remaining languages will follow (without Mac). I will hold back all other update feeds (4.0 - 4.1.2) until the situation is clear. Regards, Matthias > > Regards, > Andrea. > > - > 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
Re: Post-release steps for 4.1.4
> Italian done. Actually I decided to keep Mac on hold, since I'd like to know > more about https://bz.apache.org/ooo/show_bug.cgi?id=127568 before pushing > the update to all users. If others feel the same, we can keep Mac > notifications pending for the time being. +1 to delay Mac notice. Regards, Dave > > Regards, > Andrea. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > signature.asc Description: Message signed with OpenPGP
Re: Post-release steps for 4.1.4
Matthias Seidel wrote: Am 28.10.2017 um 20:07 schrieb Andrea Pescetti: You didn't only look around, you committed stuff and I'll now try to review it. But yes, I confirm that one is the tool we use. Only small changes for https... I couldn't resist! ;-) OK, no problem! But as you will see in http://svn.apache.org/viewvc/openoffice/devtools/genUpdateFeed/ (besides the duplicated record for "he" that invalidated the feed but, I assume, was just due to not noticing that we had it already) there is an important lesson to learn about HTTPS. When this is meant for a human using an ordinary browser, indeed we can do the change and if somebody feels this is better and more secure, no objections to doing so. When this is meant for a program, though, we must make sure that things will still work. In this case, switching to HTTPS broke since the XML namespace (which looks like a URL, but is not meant to be browsed) changed and OpenOffice was no longer able to recognize it, so my 4.1.3 was not finding the update. There is absolutely no advantage in changing XML namespaces to HTTPS, they are not real URLs and the only effect in changing them will be that OpenOffice won't detect the updates any longer. I kept the HTTPS in download URL instead: with our current model, we ask the user to open a browser anyway, so this won't break. Let's do this: I'll push the update feeds for Italian 4.1.3 only, within a couple hours, just to check that everything still works the way it should; then I'll leave you free to take over. OK, I would then proceed according to your list. Italian done. Actually I decided to keep Mac on hold, since I'd like to know more about https://bz.apache.org/ooo/show_bug.cgi?id=127568 before pushing the update to all users. If others feel the same, we can keep Mac notifications pending for the time being. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Post-release steps for 4.1.4
Am 28.10.2017 um 20:07 schrieb Andrea Pescetti: > Matthias Seidel wrote: >> Am 26.10.2017 um 22:58 schrieb Andrea Pescetti: >>> - Enable feeds for 4.1.3 in French, German, Italian (three random >>> "medium-size" languages) within the next 24 hours. >> I was a bit curious and looked around. ;-) >> https://svn.apache.org/repos/asf/openoffice/devtools/genUpdateFeed/ > > You didn't only look around, you committed stuff and I'll now try to > review it. But yes, I confirm that one is the tool we use. Only small changes for https... I couldn't resist! ;-) > >> I would like to give the first step a try, if you don't mind? > > Let's do this: I'll push the update feeds for Italian 4.1.3 only, > within a couple hours, just to check that everything still works the > way it should; then I'll leave you free to take over. OK, I would then proceed according to your list. Regards, Matthias > > Regards, > Andrea. > > - > 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
Re: Post-release steps for 4.1.4
Matthias Seidel wrote: Am 26.10.2017 um 22:58 schrieb Andrea Pescetti: - Enable feeds for 4.1.3 in French, German, Italian (three random "medium-size" languages) within the next 24 hours. I was a bit curious and looked around. ;-) https://svn.apache.org/repos/asf/openoffice/devtools/genUpdateFeed/ You didn't only look around, you committed stuff and I'll now try to review it. But yes, I confirm that one is the tool we use. I would like to give the first step a try, if you don't mind? Let's do this: I'll push the update feeds for Italian 4.1.3 only, within a couple hours, just to check that everything still works the way it should; then I'll leave you free to take over. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Post-release steps for 4.1.4
Am 26.10.2017 um 22:58 schrieb Andrea Pescetti: > A short summary of the post-release steps for 4.1.4 I'm going to take > care of, since we are now at the "7 days after release" mark: > > 1) Security reports for 4.1.4 are now published at > https://www.openoffice.org/security/bulletin.html > Nothing special, the usual handful of fixes we do at every release; > but I'll now send a notice to the announce@ list with this link. > > 2) Update feeds haven't been updated yet. They are organized by > language and version (i.e., there is a feed that will be shown to > current users of version 4.1.3 in Italian, one for version 4.1.2 in > French, one for 4.1.2 in German, one for 4.1.1 in German...), so a lot > of combinations. > > I plan to: > - Enable feeds for 4.1.3 in French, German, Italian (three random > "medium-size" languages) within the next 24 hours. > - 24/48 hours later, enable feeds for 4.1.3 in all other languages > including English > - As time allows, enable feeds for users of versions < 4.1.3 I was a bit curious and looked around. ;-) It seems quite easy to generate the update feeds using these scripts: https://svn.apache.org/repos/asf/openoffice/devtools/genUpdateFeed/ I would like to give the first step a try, if you don't mind? Regards, Matthias > > Regards, > Andrea. > > - > 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
Re: Post-release steps for 4.1.4
Am 26.10.2017 um 22:58 schrieb Andrea Pescetti: > A short summary of the post-release steps for 4.1.4 I'm going to take > care of, since we are now at the "7 days after release" mark: > > 1) Security reports for 4.1.4 are now published at > https://www.openoffice.org/security/bulletin.html > Nothing special, the usual handful of fixes we do at every release; > but I'll now send a notice to the announce@ list with this link. > > 2) Update feeds haven't been updated yet. They are organized by > language and version (i.e., there is a feed that will be shown to > current users of version 4.1.3 in Italian, one for version 4.1.2 in > French, one for 4.1.2 in German, one for 4.1.1 in German...), so a lot > of combinations. > > I plan to: > - Enable feeds for 4.1.3 in French, German, Italian (three random > "medium-size" languages) within the next 24 hours. > - 24/48 hours later, enable feeds for 4.1.3 in all other languages > including English > - As time allows, enable feeds for users of versions < 4.1.3 Hi Andrea, That sounds great and is right on time for the OpenRheinRuhr (https://openrheinruhr.de/aussteller/liste/) next weekend. Michael and his family will hopefully have a lot of visitors (including me on Sunday) ;-) Additional tasks: I think the tag for 4.1.4 is missing. https://svn.apache.org/repos/asf/openoffice/tags/ Is this somehow related to the Github tag (which was created premature)? https://github.com/apache/openoffice/releases Regards, Matthias > > Regards, > Andrea. > > - > 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
Post-release steps for 4.1.4
A short summary of the post-release steps for 4.1.4 I'm going to take care of, since we are now at the "7 days after release" mark: 1) Security reports for 4.1.4 are now published at https://www.openoffice.org/security/bulletin.html Nothing special, the usual handful of fixes we do at every release; but I'll now send a notice to the announce@ list with this link. 2) Update feeds haven't been updated yet. They are organized by language and version (i.e., there is a feed that will be shown to current users of version 4.1.3 in Italian, one for version 4.1.2 in French, one for 4.1.2 in German, one for 4.1.1 in German...), so a lot of combinations. I plan to: - Enable feeds for 4.1.3 in French, German, Italian (three random "medium-size" languages) within the next 24 hours. - 24/48 hours later, enable feeds for 4.1.3 in all other languages including English - As time allows, enable feeds for users of versions < 4.1.3 Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
