Closed Bug 764897 (bmo4.2) Opened 8 years ago Closed 7 years ago

Upgrade BMO to 4.2 (Tracking Bug)

Categories

(bugzilla.mozilla.org :: General, defect)

Production
defect
Not set

Tracking

()

RESOLVED FIXED

People

(Reporter: glob, Unassigned)

References

(Depends on 1 open bug)

Details

(Keywords: meta)

No description provided.
Depends on: 764430
Depends on: 765143
Depends on: 767570
Depends on: 767583
Depends on: 769829
No longer depends on: 769829
Alias: bmo4.2
Depends on: 770545
Depends on: 771875
Depends on: 772953
Depends on: 773327
Depends on: 774194
Depends on: 770105
Now that we branched for 4.4, wouldn't it make sense to upgrade bmo to the 4.4 branch directly? I don't expect any major change on this branch anymore, only some new WebServices methods and stabilization. I think it would be much easier for you to maintain bmo/4.4 than to backport tons of features to the bmo/4.2 branch again.
(In reply to Frédéric Buclin from comment #1)
> Now that we branched for 4.4, wouldn't it make sense to upgrade bmo to the
> 4.4 branch directly? I don't expect any major change on this branch anymore,
> only some new WebServices methods and stabilization. I think it would be
> much easier for you to maintain bmo/4.4 than to backport tons of features to
> the bmo/4.2 branch again.

We discussed this and decided that we would still go forward with out plan to upgrade to 4.2 this month. 4.4 is not expected til close to the end of the year. After 4.2 is done we will start working on porting to 4.4 and hope to release soon after general availability.

dkl
Blocks: 802451
No longer depends on: 780820
Depends on: 677757
No longer depends on: 677757
Depends on: 780820
Depends on: 821070
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.