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
