On 12/17/06, vyznev@svn.wikimedia.org vyznev@svn.wikimedia.org wrote:
Modified: trunk/phase3/RELEASE-NOTES
--- trunk/phase3/RELEASE-NOTES 2006-12-17 15:53:50 UTC (rev 18402) +++ trunk/phase3/RELEASE-NOTES 2006-12-17 16:51:01 UTC (rev 18403) @@ -336,6 +336,8 @@
- (bug 8274) Wrap edit tools in a <div> with a specified class
- Detect PHP 5.0.x 64-bit bug and abort in WebStart.php; too many things break mysteriously otherwise (detection code copied from install-utils.inc)
+* (bug 8295) Change handling of <center> tags in doBlockLevels() to match that
- of <div>
== Languages updated ==
In general, it's probably best if RELEASE-NOTES messages reflect changes as visible to end users, since that's who they're there for. The average end user isn't going to know or care what doBlockLevels() does; they'll want a message like "Fixed handling of paragraph breaks in <center>". Or at least that's my view.
On 17/12/06, Simetrical Simetrical+wikitech@gmail.com wrote:
In general, it's probably best if RELEASE-NOTES messages reflect changes as visible to end users, since that's who they're there for. The average end user isn't going to know or care what doBlockLevels() does; they'll want a message like "Fixed handling of paragraph breaks in <center>". Or at least that's my view.
...though in cases where there was a significant rewrite of something which produces no user visible effects, but still needs to be noted, some technical detail is helpful, especially for people who have to maintain a lot of third party extensions and so forth.
Rob Church
wikitech-l@lists.wikimedia.org