1383442 - Set Target Milestone on bugs when closed by pulsebot reporting pushes to comm-central.

Status: NEW

(Thunderbird :: Build Config, task, P5)

Description

[Tom Prince [:tomprince]]

I recently enabled pulsebot (https://github.com/glandium/pulsebot/pull/16) on comm-central, so pushes to comm-central will close the associated bug.

When this happens, the target-milestone of the bug needs to set to the next release.

Glandium, would this be something that would be reasonable to add to pulsebot?

Comment 1

[Mike Hommey [:glandium]]

Sure. If you find a reliable way to get the right target milestone...

Comment 2

[Philipp Kewisch [:Fallen][📱📆]]

https://product-details.mozilla.org/1.0/firefox_versions.json might be of help, there is a similar file for thunderbird.

Comment 3

[Mike Hommey [:glandium]]

(In reply to Philipp Kewisch [:Fallen] from comment #2)
> https://product-details.mozilla.org/1.0/firefox_versions.json might be of
> help, there is a similar file for thunderbird.

This seems like the kind of information that would end up being wrong for a short moment after merges and version bumps on central.

Comment 5

[Rob Lemley [:rjl]]

(In reply to jassmank342 from comment #4)

P3
Did you have a question or perhaps a fix for this?

The only other way I can come up with is by looking at version.txt within the repository itself. I'm not even convinced this should be a pulsebot function in the first place though. This is handled by Bugherder for Firefox. It determines the milestone via a complicated look at the Bugzilla configuration data.