Closed
Bug 1161531
Opened 11 years ago
Closed 11 years ago
Change mozilla-release status flag setting to 38.0.5
Categories
(Tree Management :: Bugherder, defect)
Tree Management
Bugherder
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: RyanVM, Unassigned)
Details
Attachments
(1 file)
beta merged to release yesterday, so 38.0.5 is now on m-r instead of m-b.
This should fix it. I'm just going to merge it r=me because it's trivial and I tested it locally so I know it works.
Do I need to move the end date up a week at some point also, though? Or is that fine to leave it as ending on May 29?
Flags: needinfo?(ryanvm)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 3•11 years ago
|
||
(In reply to Wes Kocher (:KWierso) from comment #1)
> Do I need to move the end date up a week at some point also, though? Or is
> that fine to leave it as ending on May 29?
We're going to want it to set 38.0.5 until one week prior to the end of the next release cycle when Beta39 merges to release and Fx39 RC is spun - so June 22nd AFAICT. If there's any Fx 38.0 chemspilling on a relbranch prior to the release of 38.0.5 in early June, we'll just need to deal with manually setting the correct flag.
Flags: needinfo?(ryanvm)
(In reply to Wes Kocher (:KWierso) from comment #1)
> Do I need to move the end date up a week at some point also, though? Or is
> that fine to leave it as ending on May 29?
I hate JS dates. That should be June 29. So we're both right, I need to move it up by a week, I guess.
Flags: needinfo?(wkocher)
(In reply to Wes Kocher (:KWierso) from comment #4)
> (In reply to Wes Kocher (:KWierso) from comment #1)
> > Do I need to move the end date up a week at some point also, though? Or is
> > that fine to leave it as ending on May 29?
>
> I hate JS dates. That should be June 29. So we're both right, I need to move
> it up by a week, I guess.
Made this change in https://github.com/mozilla/Bugherder/commit/2dbf62b188f8bf4fe883dcfb62c24fbdc1989a28
Flags: needinfo?(wkocher)
You need to log in
before you can comment on or make changes to this bug.
Description
•