Closed Bug 326354 Opened 20 years ago Closed 20 years ago

make sure channel is set correctly for 0.1 -> 0.2 update

Categories

(Calendar :: Lightning Only, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dmosedale, Assigned: dmosedale)

References

Details

Attachments

(1 file, 1 obsolete file)

I _think_ this probably just requires that we set the URL in install.rdf correctly, but we may also need a bit of the channel infrastructure in place.
Note that we're probably going to want the nightly builds to have a different update channel than the release builds, so it may be that this checkin should only go in along with the checkins that switch to release version numbers, and then be immediately backed out post-release along with those version number checkins.
Assignee: nobody → dmose
Whiteboard: [ETA 2/22]
Whiteboard: [ETA 2/22] → [ETA 2/24]
Whiteboard: [ETA 2/24] → [ETA 2/25]
Whiteboard: [ETA 2/25] → [ETA 2/28]
Whiteboard: [ETA 2/28] → [ETA 3/1]
Attached patch install.rdf patch, v1 (obsolete) — Splinter Review
This temporarily disables Firefox support as discussed on IRC, since that's not really ready for end-users. It also makes a bunch of other tweaks in order for tomorrows build to be a release candidate.
Attachment #213958 - Flags: first-review?(jminta)
Tweaked as per IRC discussion.
Attachment #213958 - Attachment is obsolete: true
Attachment #213962 - Flags: first-review?(jminta)
Attachment #213958 - Flags: first-review?(jminta)
Whiteboard: [ETA 3/1]
Comment on attachment 213962 [details] [diff] [review] install.rdf patch, v2 woohoo! release candidate! r=jminta
Attachment #213962 - Flags: first-review?(jminta) → first-review+
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
(In reply to comment #5) > woohoo! release candidate! Great! Two small nits: Using already defined @BUILD_ID@ for build date in install.rdf would have been same results with less pain and without red tinderbox ;-) Updating extension results in displayed message "An error occurred while trying to find updates for Lightning". Reason is that the extension manager tries to parse the 404 html error page as update manifest file. Error: mismatched tag. Expected: </link>. Source File: http://www.mozilla.org/projects/calendar/lightning/Linux_x86-gcc3/update.rdf Line: 14, Column: 3 Source Code: </head>--^ on win it's http://www.mozilla.org/projects/calendar/lightning/WINNT_x86-msvc/update.rdf that fail)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: