Closed Bug 401749 Opened 17 years ago Closed 17 years ago

Unlock prebuilt Talkback packages for Sunbird 0.8pre

Categories

(Calendar :: Build Config, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: ssitter, Assigned: ause)

References

Details

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.9pre) Gecko/20071030 Calendar/0.8pre

The prebuilt Talkback packages currently only work with Sunbird 0.7pre to 0.7.

The install.rdf should be updated to support Sunbird 0.8pre to 0.8. 
According to the config files the packages are located on the tinderboxen in

linux: 
/builds/tinderbox/Sb-Mozilla1.8/talkback-sunbird-1.8-linux.tar.bz2

macosx: 
/builds/tinderbox/Sunbird-Mozilla1.8/talkback-sunbird-1.8-mac.tar.bz2

win32: 
/cygdrive/c/builds/tinderbox/Sb-Mozilla1.8/talkback-sunbird-1.8-win32.tar.bz2
Blocks: 396013
i tend to switch <em:maxVersion> to 0.9 (see http://wiki.mozilla.org/Build:CommunitySelfHelp) to be done with it until sunbird 1.0
Assignee: nobody → ause
prepared some tarballs unlocking up to 0.9. will put them in place if there are not objections.

it's not yet clear to me how to deal with a major version change (e.g. 0.x->1.0)
From my understanding it just depends on the branch used. As long as Sunbird is build from MOZILLA_1_8_BRANCH the packages should just work.
(In reply to comment #3)
> From my understanding it just depends on the branch used. As long as Sunbird is
> build from MOZILLA_1_8_BRANCH the packages should just work.

This is correct. 

talkback tarballs changed, checks pending
Fix verified in today's nightly builds:

    <em:targetApplication>
      <!-- Sunbird -->
      <Description>
        <em:id>{718e30fb-e89b-41dd-9da7-e25a45638b28}</em:id>
        <em:minVersion>0.7pre</em:minVersion>
        <em:maxVersion>0.9</em:maxVersion>
      </Description>
    </em:targetApplication>
Status: NEW → ASSIGNED
done
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Target Milestone: --- → 0.8
Verified per comment#6.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.