Yesterday, I made the RC2 release and listed only one known bug in the release. I decided to look through bugzilla for other as-yet-unaddressed bugs. I'd like to get these fixed before the tarball release May 15th. Please feel free to take them on so that we can get them fixed.
* http://bugzilla.wikimedia.org/46802 Enabling extensions during install process displays empty readonly textbox on status page
* http://bugzilla.wikimedia.org/46401 [Regression] mw.loader: Code should execute after styles being loaded (wait for async cssText buffering)
* https://bugzilla.wikimedia.org/44907 ResourceLoader: Invalid argument supplied for foreach
* https://bugzilla.wikimedia.org/44568 bin/ulimit5.sh isn't UNIX compliant
* https://bugzilla.wikimedia.org/44524 update.php should invalidate ResourceLoader message cache
* https://bugzilla.wikimedia.org/43817 Include short descriptions for extensions bundled in the release
Ideally, all of these would be fixed before Quim Gil's release testing next week, but if we can't achieve that, it would be good to at least have them looked at.
Thanks!
Hi Mark,
On Tue, 2013-04-09 at 09:43 -0400, Mark A. Hershberger wrote:
Yesterday, I made the RC2 release and listed only one known bug in the release. I decided to look through bugzilla for other as-yet-unaddressed bugs.
considering the six tickets that you listed https://bugzilla.wikimedia.org/buglist.cgi?bug_id=46802,46401,44907,44568,44... as "should-have"/"must-have"s, I took a quick look at the other 27 Bugzilla tickets with Target Milestone = 1.21.0: https://bugzilla.wikimedia.org/buglist.cgi?bug_id=10788,23580,25702,30713,34...
Out of these 27, * the following tickets have patches in Gerrit that have not been reviewed or merged yet: https://bugzilla.wikimedia.org/buglist.cgi?bug_id=23580,30713,38783,40588,42... * the following tickets have patches in Gerrit which need improvements before merging: https://bugzilla.wikimedia.org/buglist.cgi?bug_id=25702,35785,41337
For https://bugzilla.wikimedia.org/buglist.cgi?bug_id=39507 it's unclear if this still happens, so testing with 1.21rc* is highly welcome.
That leaves the following tickets which currently seem likely to not get fixed for 1.21.0: https://bugzilla.wikimedia.org/buglist.cgi?bug_id=34238,40812,41100,41315,42...
@Mark: https://bugzilla.wikimedia.org/show_bug.cgi?id=41100#c5 says it's worth to mention in the release notes, and https://bugzilla.wikimedia.org/show_bug.cgi?id=46934 might be worth to keep an eye on / add to the list of six tickets.
Cheers, andre
On 04/09/2013 04:10 PM, Andre Klapper wrote:
https://bugzilla.wikimedia.org/show_bug.cgi?id=41100#c5 says it's worth to mention in the release notes, and https://bugzilla.wikimedia.org/show_bug.cgi?id=46934 might be worth to keep an eye on / add to the list of six tickets.
Thank you so much for your help in corralling all of these bugs!
<quote name="Andre Klapper" date="2013-04-09" time="22:10:34 +0200">
... bug numbers galore ...
You know, if we can get the Bugzilla weekly report more accurate, these would be good summaries to have, something like:
# of bugs affecting current REL # of bugs affecting current REL with patches # of bugs affecting REL.next # of bugs affecting REL.next wtih patches
Then, if those numbers change much, graphs from Zeljko ;)
Greg
On Tue, Apr 9, 2013 at 10:37 PM, Greg Grossmeier greg@wikimedia.org wrote:
Then, if those numbers change much, graphs from Zeljko ;)
Give me numbers and there will be graphs. :)
Željko
wikitech-l@lists.wikimedia.org