Hi all,
We're rapidly approaching the 1.26 release. General guilting e-mail to get some extra eyes on the things currently tagged against the release.
https://phabricator.wikimedia.org/maniphest/query/jcSXdUecbcLp/#R
Buggy releases -> sad times. Let's wrap this one up :)
-Chad
On 2015-10-27, Chad innocentkiller@gmail.com wrote:
Hi all,
We're rapidly approaching the 1.26 release. General guilting e-mail to get some extra eyes on the things currently tagged against the release.
https://phabricator.wikimedia.org/maniphest/query/jcSXdUecbcLp/#R
Buggy releases -> sad times. Let's wrap this one up :)
What is the correct use of MW-1.26-release and MW-1.26-release-notes tags in ze Phab?
1) Should I add RELEASE NOTES entry in every change that closes a bug? 2) When should I tag MW-1.26-release-notes ? 3) How should I tag changes that are in master but should be backported?
examples: https://phabricator.wikimedia.org/T116374 https://phabricator.wikimedia.org/T116375 https://phabricator.wikimedia.org/T75031
~saper
Hej hej,
On Wed, 2015-10-28 at 13:53 +0000, Marcin Cieslak wrote:
- Should I add RELEASE NOTES entry in every change that closes a
bug?
To be answered by someone who knows. My uneducated guess is Yes.
- When should I tag MW-1.26-release-notes ?
You are welcome to add #MW-1.26-release to any task that got fixed for the 1.26.x tarball release. #MW-1.26-release-notes does not exist.
For 1.27, #MW-1.27-release is to be used for tasks that shall get fixed for the tarball release of 1.27.x. #MW-1.27-release-notes shall be used for any tasks that got fixed for 1.27. For more background, see https://phabricator.wikimedia.org/T113628
- How should I tag changes that are in master but should be
backported?
I wonder how much https://www.mediawiki.org/wiki/Backporting_fixes#Backports_to_stable.2Fsuppo... still reflects the reality. There is a #MediaWiki-Tarball-Backports in Phabricator but I'm not sure if anyone really uses it.
andre
On Wed, Oct 28, 2015 at 7:34 AM Andre Klapper aklapper@wikimedia.org wrote:
Hej hej,
On Wed, 2015-10-28 at 13:53 +0000, Marcin Cieslak wrote:
- Should I add RELEASE NOTES entry in every change that closes a
bug?
To be answered by someone who knows. My uneducated guess is Yes.
- When should I tag MW-1.26-release-notes ?
You are welcome to add #MW-1.26-release to any task that got fixed for the 1.26.x tarball release. #MW-1.26-release-notes does not exist.
Please do not do this. I'm using the 1.26-release tag to track things that need to be done prior to the release. I've been actively removing the (mostly automated, from the release tagger bot) 1.26 tag from things that are just "fixed and will be in the branch."
I have a very unorganized board: https://phabricator.wikimedia.org/tag/mw-1.26-release/board/
For 1.27, #MW-1.27-release is to be used for tasks that shall get fixed for the tarball release of 1.27.x. #MW-1.27-release-notes shall be used for any tasks that got fixed for 1.27. For more background, see https://phabricator.wikimedia.org/T113628
This is what I want to do.
- How should I tag changes that are in master but should be
backported?
My preferred mechanism is just creating the branch cherry-pick to the release branch...I actively keep an eye on all REL* branches of mw core so I'll notice. If there's an existing task for a bug, you can continue to reference that, I don't see a need to file a second one.
-Chad
On Wed, 2015-10-28 at 16:05 +0000, Chad wrote:
Please do not do this. I'm using the 1.26-release tag to track things that need to be done prior to the release. I've been actively removing the (mostly automated, from the release tagger bot) 1.26 tag from things that are just "fixed and will be in the branch."
I stand corrected. Thanks Chad!
andre
wikitech-l@lists.wikimedia.org