Closed Bug 528540 Opened 14 years ago Closed 14 years ago

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

Categories

(Calendar :: Build Config, defect)

Product:
Calendar
Component:
Build Config
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: ssitter, Assigned: ssitter)

Details

Attachments

(1 file)

comm-central patch
5.81 KB, patch
Fallen
: review+
Details | Diff | Splinter Review 
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+
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
Closed: 14 years ago
Resolution: --- → FIXED
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?
Steffen, see Bug 544858.
You need to log in before you can comment on or make changes to this bug.