Seems sensible, but knowing history I don't think it will be updated correctly.
We're a different team now. Whaddya say we give it a try?
I think the updating of VERSION.txt really needs to be automated. Can we have a script that can be run bumps the version number and generates these logs by searching for keywords e.g. 'Bug:' 'Feature:' and generates this list. I think without this, this is a nice idea but will be disastrous.
https://github.com/tj/git-extras/wiki/Commands#git-changelog is one of the many solutions to this turned up by a quick Google :)
–Sam
My biggest concern is blocking merges on badly formatted release notes. I see this all the time with core and the merge conflicts associated due to multiple people editing the text file.
If we can have a tool that generates these consistently I'm all for release notes. Versioning seems like a no brainer but I'd rather have no release notes than bad release notes.
On Tue, Mar 24, 2015 at 10:42 AM, Sam Smith samsmith@wikimedia.org wrote:
Seems sensible, but knowing history I don't think it will be updated
correctly.
We're a different team now. Whaddya say we give it a try?
I think the updating of VERSION.txt really needs to be automated. Can we have a script that can be run bumps the version number and generates these logs by searching for keywords e.g. 'Bug:' 'Feature:' and generates this list. I think without this, this is a nice idea but will be disastrous.
https://github.com/tj/git-extras/wiki/Commands#git-changelog is one of the many solutions to this turned up by a quick Google :)
–Sam
My biggest concern is blocking merges on badly formatted release notes. I see this all the time with core and the merge conflicts associated due to multiple people editing the text file.
Yeah. That sucks. How about we push a single change to VERSIONS.txtmediawikidown at the end of every release cycle? We could even collaborate on them that way.
–Sam
Great link, Sam. We should use it.
On Mar 24, 2015, at 1:42 PM, Sam Smith samsmith@wikimedia.org wrote:
Seems sensible, but knowing history I don't think it will be updated correctly.
We're a different team now. Whaddya say we give it a try?
I think the updating of VERSION.txt really needs to be automated. Can we have a script that can be run bumps the version number and generates these logs by searching for keywords e.g. 'Bug:' 'Feature:' and generates this list. I think without this, this is a nice idea but will be disastrous.
https://github.com/tj/git-extras/wiki/Commands#git-changelog https://github.com/tj/git-extras/wiki/Commands#git-changelog is one of the many solutions to this turned up by a quick Google :)
–Sam _______________________________________________ Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l
Hint:
For a better wiki-formatted output (e.g. with {{git}} and {{phabricator}} we could reuse mediawiki-tools-release[1]. With the following command (e.g.) you can create a new changelog of MF:
$ cd /var/www/.../extensions/MobileFrontend/
$../../../mediawiki-release/make-deploy-notes/make-deploy-notes origin/wmf/1.25wmf20 origin/wmf/1.25wmf21
(depends on where you cloned mediawiki-tools-release)
The output would be: https://phabricator.wikimedia.org/P431 [1]
(== Core == are the changes of MobileFrontend, the exceptions and errors are, because the script isn't designed to run from an extension dir, but we could ignore them, or rewrite the script).
That's how we create the changelogs for wmf-versions[2].
[1] https://github.com/wikimedia/mediawiki-tools-release [2]
[2] https://www.mediawiki.org/wiki/Category:WMF_Releases [3]
Freundliche Grüße / Kind regards Florian Schmidt
-----Original-Nachricht-----
Betreff: Re: [WikimediaMobile] Versioning MobileFrontend
Datum: Tue, 24 Mar 2015 18:42:48 +0100
Von: Sam Smith samsmith@wikimedia.org
An: Jon Robson jrobson@wikimedia.org, mobile-l mobile-l@lists.wikimedia.org
Seems sensible, but knowing history I don't think it will be updated correctly. We're a different team now. Whaddya say we give it a try? I think the updating of VERSION.txt really needs to be automated. Can we have a script that can be run bumps the version number and generates these logs by searching for keywords e.g. 'Bug:' 'Feature:' and generates this list. I think without this, this is a nice idea but will be disastrous. https://github.com/tj/git-extras/wiki/Commands#git-changelog [4] is one of the many solutions to this turned up by a quick Google :) –Sam
Links: ------ [1] https://phabricator.wikimedia.org/P431 [2] https://github.com/wikimedia/mediawiki-tools-release [3] https://www.mediawiki.org/wiki/Category:WMF_Releases [4] https://github.com/tj/git-extras/wiki/Commands#git-changelog
That’s great Florian. Jon, does that address your concern?
On Mar 25, 2015, at 2:46 AM, florian.schmidt.welzow@t-online.de wrote:
Hint: For a better wiki-formatted output (e.g. with {{git}} and {{phabricator}} we could reuse mediawiki-tools-release[1]. With the following command (e.g.) you can create a new changelog of MF:
$ cd /var/www/.../extensions/MobileFrontend/ $../../../mediawiki-release/make-deploy-notes/make-deploy-notes origin/wmf/1.25wmf20 origin/wmf/1.25wmf21 (depends on where you cloned mediawiki-tools-release)
The output would be: https://phabricator.wikimedia.org/P431 https://phabricator.wikimedia.org/P431 (== Core == are the changes of MobileFrontend, the exceptions and errors are, because the script isn't designed to run from an extension dir, but we could ignore them, or rewrite the script).
That's how we create the changelogs for wmf-versions[2].
[1] https://github.com/wikimedia/mediawiki-tools-release https://github.com/wikimedia/mediawiki-tools-release [2] https://www.mediawiki.org/wiki/Category:WMF_Releases https://www.mediawiki.org/wiki/Category:WMF_Releases
Freundliche Grüße / Kind regards Florian Schmidt
-----Original-Nachricht----- Betreff: Re: [WikimediaMobile] Versioning MobileFrontend Datum: Tue, 24 Mar 2015 18:42:48 +0100 Von: Sam Smith samsmith@wikimedia.org An: Jon Robson jrobson@wikimedia.org, mobile-l mobile-l@lists.wikimedia.org
Seems sensible, but knowing history I don't think it will be updated correctly.
We're a different team now. Whaddya say we give it a try?
I think the updating of VERSION.txt really needs to be automated. Can we have a script that can be run bumps the version number and generates these logs by searching for keywords e.g. 'Bug:' 'Feature:' and generates this list. I think without this, this is a nice idea but will be disastrous.
https://github.com/tj/git-extras/wiki/Commands#git-changelog https://github.com/tj/git-extras/wiki/Commands#git-changelog is one of the many solutions to this turned up by a quick Google :)
–Sam
Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l
Looks like the awesome Katie made it so that works for me. As long as the release schedule is owned by someone and documented on wiki I'm happy for us to go ahead with this. On 25 Mar 2015 3:49 am, "Bahodir Mansurov" bmansurov@wikimedia.org wrote:
That’s great Florian. Jon, does that address your concern?
On Mar 25, 2015, at 2:46 AM, florian.schmidt.welzow@t-online.de wrote:
Hint: For a better wiki-formatted output (e.g. with {{git}} and {{phabricator}} we could reuse mediawiki-tools-release[1]. With the following command (e.g.) you can create a new changelog of MF:
$ cd /var/www/.../extensions/MobileFrontend/ $../../../mediawiki-release/make-deploy-notes/make-deploy-notes origin/wmf/1.25wmf20 origin/wmf/1.25wmf21 (depends on where you cloned mediawiki-tools-release)
The output would be: https://phabricator.wikimedia.org/P431 (== Core == are the changes of MobileFrontend, the exceptions and errors are, because the script isn't designed to run from an extension dir, but we could ignore them, or rewrite the script).
That's how we create the changelogs for wmf-versions[2].
[1] https://github.com/wikimedia/mediawiki-tools-release [2] https://www.mediawiki.org/wiki/Category:WMF_Releases
Freundliche Grüße / Kind regards Florian Schmidt
-----Original-Nachricht----- Betreff: Re: [WikimediaMobile] Versioning MobileFrontend Datum: Tue, 24 Mar 2015 18:42:48 +0100 Von: Sam Smith samsmith@wikimedia.org An: Jon Robson jrobson@wikimedia.org, mobile-l < mobile-l@lists.wikimedia.org>
Seems sensible, but knowing history I don't think it will be updated correctly.
We're a different team now. Whaddya say we give it a try?
I think the updating of VERSION.txt really needs to be automated. Can we have a script that can be run bumps the version number and generates these logs by searching for keywords e.g. 'Bug:' 'Feature:' and generates this list. I think without this, this is a nice idea but will be disastrous.
https://github.com/tj/git-extras/wiki/Commands#git-changelog is one of the many solutions to this turned up by a quick Google :)
–Sam
Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l