Re: Add warning message for unknown characters (2889) / Fix assertion (2983) (issue 6625078)
Uh, oh, I failed to use git-cl correctly, so this Rietvield issue is used for two tracker items... Sorry. https://codereview.appspot.com/6625078/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
GUB and updating the website
I'm sending this information as a mail message as a cheap and quick way of documenting what I believe I've discovered about how GUB updates the website, and how it is done otherwise. GUB builds and uploads the binaries and the documentation. The upload is done as a separate step from the build - it requires the builder to check that all has gone well before doing the upload. The upload is about 700 Megs in total, and on my DSL system takes around 4 hours. The upload uses rsync with the delay-updates option, which I understand to mean that it doesn't apply the changes until all the files are uploaded. However, it also has a number of separate rsync steps (e.g. the tarball is a separate step) so I believe the documentation is treated as an atomic set, but not the whole update. I think that browsing the website once the upload has completed can take you the latest (recently uploaded documentation) whereas the website says it's still at the previous version. This is because GUB uploads the binaries and documentation, but does not rebuild the website. To make the website appear to be at the latest version, we need to update VERSION and news-front - and this is an important feature - in master. If you're wondering why the website still says 2.16.1, it's because I'd not cottoned on to this. I'd updated stable/2.16 but not master. The website runs 2 cron jobs every hour. The first pulls git master. The second (essentially) runs make website - so the website we see is based solely on the contents of the master branch. In summary: GUB updates the documents and the binaries; git master controls the contents of the website via cronjobs. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Dual license the files under mf/ using OFL. (issue 6970046)
LGTM https://codereview.appspot.com/6970046/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Bug squad metrics for Oct to Dec 2012
Hi, If you read this mailing list you are probably aware of the Bug Squad, a small team within the Lilypond project. Their role is described in [1] as follows: The Bug Squad is mainly composed of non-programmers – their job is to organize issues, not solve them. Their duties include removing false bug reports, ensuring that any real bug report contains enough information for developers, and checking that a developer’s fix actually resolves the problem. Right now the bug squad is Eluze, Marek Klein, Ralph Palmer and I with help from other contributors including Phil Holmes, David Kastrup, Keith O'Hara, James, Graham Percival, Reinhold Kainhofer. As stated here [2] we aim to respond to bug reports within four days. Graham Percival wrote some scripts [3] to analyse the response time performance of the bug squad and I have just run them for the last calendar quarter of 2012. Response category Number % of total -- Less than 24 hours 77 67.54% 24 to 48 hours 18 15.79% More than 48 hours 12 10.53% Never replied 7 6.14% As you can see, we responded to over 83% of the reports in 48 hours or less, which I think is pretty good. Never replied includes some administrative emails (that need no reply), so it's not always a bad thing to have some emails in this category. Just email me if you would like a copy of the full report. If you would like to help us improve on this by joining the bug squad, please get in touch. I have one new applicant-in-waiting, Joe Wakeling, but we could use one or two more! Cheers, Colin. [1] http://lilypond.org/doc/v2.17/Documentation/contributor/introduction-to-issues [2] http://lilypond.org/bug-reports.html [3] https://github.com/gperciva/lilypond-extra/tree/master/bug-squad -- Colin Hall Bug Meister ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
