Firefox 11
-
- Posts:105
- Joined:Tue Jul 12, 2005 8:56 pm
It is my sad duty to announce that Firefox 11 will be released tomorrow.
- DraconPern
- Site Admin
- Posts:1218
- Joined:Thu Oct 30, 2003 11:47 pm
- Location:Texas
- Contact:
-
- Posts:105
- Joined:Tue Jul 12, 2005 8:56 pm
Re: Firefox 11
Dracon,
Any time frame on this being released?
Any time frame on this being released?
Re: Firefox 11
I would cheerfully pay $250/year to get Community Edition released as an MSI within a week of release. I know I can't legitimately complain about what I got for free, but I'm starting to get nervous about all the users I support, stuck with an insecure version for three weeks now.
-
- Posts:105
- Joined:Tue Jul 12, 2005 8:56 pm
Re: Firefox 11
I'm starting to move away from Firefox all together. Relying on this site will become difficult over time especially with the ESR version and the releases every 6 weeks. Honestly check out Google Chrome for Business. Built in policy support directly from Google. Steady releases every 8 weeks or so. I love this project but honestly I'm surprised he keep it running for so long with little support from Mozilla.
Re: Firefox 11
ESR brings nothing to the table for me with no MSI installer.
Dracon, what is the most time consuming part of the process to build your release? Is it including all the languages? Are there many changes in the code each release that cause excessive testing to be done?
Dracon, what is the most time consuming part of the process to build your release? Is it including all the languages? Are there many changes in the code each release that cause excessive testing to be done?
- DraconPern
- Site Admin
- Posts:1218
- Joined:Thu Oct 30, 2003 11:47 pm
- Location:Texas
- Contact:
Re: Firefox 11
3.6.28, 11.0, and ESR 10.0.3 all released.
In terms of time.... there are several places that takes time.
For the official binary, I need to go through and change some of the js to disable updates, browser defaults, etc. With FF4+ I have to unpack the omni.ja file and manually fix the component references in chrom.manifest. This takes about 30mins or so for each version. For the CE version, I have to apply the code patches which includes the policy stuff, plus the css changes, the versioning info, themes, etc. make sure it's all good, compile the 3 versions. This takes a few hours for each compile. Then do some of the similar changes as the official binary packages.
After the base package is done, then it takes about 5 mins to build one package. So.. since there are about 70-80 languages multiply that by 3 versions of regular binary and 3 versions of the CE versions... it takes a while. The packager puts out en-US versions first, so I can check for things like , is policy working? icon? color? etc. If something isn't right, I have to start the builds over.
I have progressively automated things as much as possible, but things like applying code patches still results in rejections which have to be fixed manually.
In terms of time.... there are several places that takes time.
For the official binary, I need to go through and change some of the js to disable updates, browser defaults, etc. With FF4+ I have to unpack the omni.ja file and manually fix the component references in chrom.manifest. This takes about 30mins or so for each version. For the CE version, I have to apply the code patches which includes the policy stuff, plus the css changes, the versioning info, themes, etc. make sure it's all good, compile the 3 versions. This takes a few hours for each compile. Then do some of the similar changes as the official binary packages.
After the base package is done, then it takes about 5 mins to build one package. So.. since there are about 70-80 languages multiply that by 3 versions of regular binary and 3 versions of the CE versions... it takes a while. The packager puts out en-US versions first, so I can check for things like , is policy working? icon? color? etc. If something isn't right, I have to start the builds over.
I have progressively automated things as much as possible, but things like applying code patches still results in rejections which have to be fixed manually.
FrontMotion Lead Developer