Re: [Libreoffice-qa] Updater improvements
Hi, Would it be an idea to use mirrorbrain for this? That has already the supported versions. We could patch it so it can give us the files in JSON/XML-format rather then create our own little program for this. The downside is that mirrorbrain hasn't had a release in 1,5 years. So I don't know how active that is. Where is the check.php stored. It would be usefull to see what format that gives the data to LibreOffice to see what it expects. -- Greetings, Rob Snelders On 06-12-13 11:02, Rob Snelders wrote: So to sum up, my suggestion is that we store version information in a database such that it can be - Updated by the official build/upload process - Updated by the person(s) who picks the 'stable' build - Queried by the BSA - Queried by various websites that need the information Did I forget anything? I don't think so. But can we create some XML/JSON API against that? Then anybody can read that information in any system. It is no confidential information so we can just let anyone read this and they can use that info. ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/ ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] Updater improvements
On Sun, Dec 8, 2013 at 11:58 AM, Rob Snelders r...@ertai.nl wrote: Hi, Would it be an idea to use mirrorbrain for this? That has already the supported versions. We could patch it so it can give us the files in JSON/XML-format rather then create our own little program for this. The downside is that mirrorbrain hasn't had a release in 1,5 years. So I don't know how active that is. Building the info into mirrorbrain is interesting. I assume that mirrorbrain is regarded as critical infra, which would be useful here because we'd be adding it as a dependency to the BSA, updater, wiki, and a few other websites. Where is the check.php stored. It would be usefull to see what format that gives the data to LibreOffice to see what it expects. http://cgit.freedesktop.org/libreoffice/website/tree/check.php?h=update Cheers, --R ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] Updater improvements
Cloph - Thoughts? On Fri, Dec 6, 2013 at 3:22 AM, Robinson Tryon bishop.robin...@gmail.com wrote: Hi all, We've chatted a bit about some of the shortcomings of the updater lately, and I've come up with a couple of suggestions for improving not only the updater, but parts of our build system and bug tracker as well. 1) Problem: It's hard to add new build hashes to the updater The updater mixes code and data in a single file, making it a bit tricky to add new build hashes. Suggestion: Factor-out the data from the updater and store it in a database[1]. 2) Problem: Build hashes don't automatically get entered into the updater Suggestion: Tweak the build process (perhaps during the upload step) so that the build hash is fed into the updater database automatically. 3) Problem: We have to manually update various websites whenever the current stable and latest versions change. For example: On Thu, Dec 5, 2013 at 4:25 AM, Christian Lohmaier lohma...@googlemail.com wrote: 4.0 version has reached end-of-life, i.e. no fixes will be provided by TDF anymore. If your site has links to 4.0 downloads, please consider changing that to something else...We'd like to remove that version from the mirrornetwork soon...So in order to avoid [problems], please update your nl-website. Suggestion: Keep track of the current stable and latest version in the updater db. Create some code snippets that can be reused by various NL sites, templates on the wiki, etc... so that they always display the right info. 4) Problem: The BSA needs to know the list of currently-supported versions of LibreOffice Suggestion: This information could be easily added to/queried from the updater database. --- So to sum up, my suggestion is that we store version information in a database such that it can be - Updated by the official build/upload process - Updated by the person(s) who picks the 'stable' build - Queried by the BSA - Queried by various websites that need the information Did I forget anything? Cheers, --R [1] Any database is fine, as long as it's not the one that the wikis lock up each night... :P ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] Updater improvements
Hello Robinson, *, On Freitag, 6. Dezember 2013 09:22 Robinson Tryon wrote: We've chatted a bit about some of the shortcomings of the updater lately, and I've come up with a couple of suggestions for improving not only the updater, but parts of our build system and bug tracker as well. snip So to sum up, my suggestion is that we store version information in a database such that it can be - Updated by the official build/upload process - Updated by the person(s) who picks the 'stable' build - Queried by the BSA - Queried by various websites that need the information Did I forget anything? I do not know, but as a user, who prefers to use bugzilla directly instead of BSA ... ;) What about the version field in bugzilla? Would it be possible to add/remove versions there too, if needed? Or would this rate among your BSA proposal ;? Have a nice day Thomas. -- When Dexter's on the Internet, can Hell be far behind? ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] Updater improvements
So to sum up, my suggestion is that we store version information in a database such that it can be - Updated by the official build/upload process - Updated by the person(s) who picks the 'stable' build - Queried by the BSA - Queried by various websites that need the information Did I forget anything? I don't think so. But can we create some XML/JSON API against that? Then anybody can read that information in any system. It is no confidential information so we can just let anyone read this and they can use that info. ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
