On Sat, Oct 29, 2011 at 2:58 PM, Dan Nessett <[email protected]> wrote:
> On Fri, 28 Oct 2011 23:30:10 +0200, Platonides wrote: > > > Dan Nessett wrote: > >> After testing, it appears moving to 1.16.5 solves the problem. Should I > >> file a bug against 1.16.2 and mention it is fixed in 1.16.5? This might > >> help those who run 1.16.x, x < 5 if, if they run into the same problem > > > > Such bug wouldn't get any action. Bugs in 1.16.x are fixed in a new > > release 1.16.y (y > x). This is already fixed, Nothing we can do to > > solve people in old versions. > > I think you have missed the point. The bug is already fixed in 1.16.5 > (and I presume in later releases). However, many wikis don't upgrade > regularly. If their situation is like ours, there is a very small tech > staff and it is unrealistic to upgrade often (we ran 1.13.2 for 3 years > before upgrading to 1.16.2). In addition, in our case we modify the > standard distribution with a patchkit, so deploying a new release of MW > requires applying that kit and testing before going live with it. This is > not a trivial amount of work. > > Consequently, I would guess there are many wikis running 1.16.x, x < 5. > If they run up against the bug described in this thread and search > Bugzilla for a fix, they won't find it. If I file a bug describing the > problem and indicate it is fixed in 1.16.5, it provides those sites with > knowledge about the problem without posting a question here or elsewhere. > > -- > -- Dan Nessett This thread has been educational on both the topic and patching conventions. A well worded bug report, as you suggest, with a link back to this thread, would be a benefit without risk. Please also provide this thread with a link to that bug report. Thanks! --Fred _______________________________________________ MediaWiki-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
