This is a tracker bug for releasing Firefox 3 oc. This bug is not that detailed, but as we get particular work items, they should block this bug for tracking, and better discoverability.
Component: Other → oc / Occitan
QA Contact: occitan.oc
Ok, I have landed Occitan both on CVS and Hg. I did some edits on the initial commit to cvs that can be followed in the hg commits, http://hg.mozilla.org/l10n-central/oc/pushloghtml. Please use both as the basis for the ongoing work. On cvs, we will work towards fx 3.0.x, and on hg work will go on towards fx 3.1. Your locale is currently only built for firefox 3.0.x. Build feedback will appear on http://l10n.mozilla.org/dashboard/ and on http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-l10n-oc (that needs to cycle for a bit still), testing builds should show up on http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla1.9.0-l10n/ over the next few hours. From now on, the content on hg and cvs are disconnected, that is, you should make conscious decisions on which changes to land where. In particular, it's probably a good idea to land the patches that we work on towards fx3.0.x in terms of search et al on hg, too.
Dear Yannig: As you may know, code freeze for the release of Firefox 3.0.4 is tomorrow (October 24, 2008). We would like to include oc as a beta version in this minor update. Part of this process is getting a confirmation that you would like to do this. Can you please respond to this bug that you would like to opt-in for this release? We just want to confirm that you are OK with this decision. Congratulations on all the hard work! We are excited to move you into beta for this release. Best regards, Seth
I'd love to have oc as a beta version. Thanks for that.
You're out of beta for a while now, closing this bug, thanks and congrats. Good opportunity to point out that we're posting announcements in mozilla.dev.l10n about the beta program towards the release of Firefox 4. Please make sure to follow those.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.