In the Wikimedia wikis, right now, we succeed to a varied degree at
letting communities know about deployments that affect them. We're
definitely getting better, and the 1.20wmf1 page is an example of
release notes done well:
http://www.mediawiki.org/wiki/MediaWiki_1.20/wmf1
http://www.mediawiki.o
As part of the pre flight steps the mobile team generates a list of
gerrit changes that have gone into the deployment branch. We then
throw it on a wiki page so that its much easier to trace back what
changed. Our current list is here
http://www.mediawiki.org/wiki/Extension:MobileFrontend/Deployme
2012/5/3 Erik Moeller :
> So how can we do better? I'd posit that it should be impossible to
> deploy code without leaving an exposed audit trail generated from
> commit messages, which can in turn be expanded by any interested
> volunteer into a human-readable and translated summary.
>
> I'd sugge
> This combined with Special:SiteChanges would be great in the glorious
future.
+1. It would indeed be a good step in the right direction.
Alolita
On Thu, May 3, 2012 at 8:18 AM, Strainu wrote:
> 2012/5/3 Erik Moeller :
> > So how can we do better? I'd posit that it should be impossible to
>
On Thu, May 3, 2012 at 12:04 AM, Erik Moeller wrote:
> I'd suggest exposing this information to a special page directly in
> the relevant wiki, say "Special:SiteChanges".
+1
> In the magical database backed configuration future,
> Special:SiteChanges might also be able to list out config changes,
