The default bug view has changed. See this FAQ.

Adjust comm-central version numbers to distinguish builds from comm-1.9.1 and comm-central

RESOLVED FIXED

Status

Calendar
Build Config
RESOLVED FIXED
8 years ago
7 years ago

People

(Reporter: Stefan Sitter, Assigned: Stefan Sitter)

Tracking

Details

Attachments

(1 attachment)

(Assignee)

Description

8 years ago
Created attachment 412246 [details] [diff] [review]
comm-central patch

I think we should adjust version numbers to distinguish comm-1.9.1 and comm-central builds. This patch proposal raises the calendar version to 1.1a1pre and sets the minVersion for Thunderbird/SeaMonkey to the currently used ones.
Attachment #412246 - Flags: review?(philipp)
Comment on attachment 412246 [details] [diff] [review]
comm-central patch

Sounds fine to me, this will be applying only on comm-central, right?
Attachment #412246 - Flags: review?(philipp) → review+
(Assignee)

Comment 2

8 years ago
Correct, no changes for the comm-1.9.1 branch. Pushed to comm-central <https://hg.mozilla.org/comm-central/rev/2d8598b18ea0> -> Fixed.
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED

Comment 3

7 years ago
So gdata now requires Lightning 1.1a1pre.
How about Lightning 1.0b2pre (1.9.2 branch?)
Why can't you keep @CALENDAR_VERSION@ in gdata's em:requires section?
(Assignee)

Comment 4

7 years ago
Steffen, see Bug 544858.
You need to log in before you can comment on or make changes to this bug.