Re: [Mageia-dev] Firefox 5
On Thu, 23 Jun 2011, Luc Menut wrote: Le 23/06/2011 07:58, Dexter Morgan a écrit : On Thu, Jun 23, 2011 at 7:29 AM, Thierry Vignaud thierry.vign...@gmail.com wrote: On 22 June 2011 19:41, Florian Hubolddoktor5...@arcor.de wrote: Well, it's quite possible that we have to include that in Mageia 1 as well, as this will be security update for Firefox 4. If we don't want to patch every CVE then we have to include it into Mageia 1 as well.. ... But i think sec team need to speak of FF5 first because i think this will be a candidate for updates regarding new firefox upstream policy Yes, I think Firefox 5 should be an updates. Firefox 5 is a security update for Firefox 4 and 4.0.1. There will be no Firefox 4.0.2. Yes, as patch to fix security are not provided for firefox 4, and not easy to backport, it needs to be updated to version 5. It is listed as an exception on the updates policy page : http://mageia.org/wiki/doku.php?id=updates_policy
Re: [Mageia-dev] Firefox 5
Le 23/06/2011 07:58, Dexter Morgan a écrit : On Thu, Jun 23, 2011 at 7:29 AM, Thierry Vignaud thierry.vign...@gmail.com wrote: On 22 June 2011 19:41, Florian Hubolddoktor5...@arcor.de wrote: Well, it's quite possible that we have to include that in Mageia 1 as well, as this will be security update for Firefox 4. If we don't want to patch every CVE then we have to include it into Mageia 1 as well.. ... But i think sec team need to speak of FF5 first because i think this will be a candidate for updates regarding new firefox upstream policy Yes, I think Firefox 5 should be an updates. Firefox 5 is a security update for Firefox 4 and 4.0.1. There will be no Firefox 4.0.2. http://www.mozilla.org/security/known-vulnerabilities/ (Firefox 4 and newer) http://www.mozilla.org/security/known-vulnerabilities/firefox.html http://blogzinet.free.fr/blog/index.php?post/2011/06/21/Mozilla-Firefox-5 (sorry, in french)
Re: [Mageia-dev] Firefox 5
Am 23.06.2011 09:28, schrieb Luc Menut: Le 23/06/2011 07:58, Dexter Morgan a écrit : On Thu, Jun 23, 2011 at 7:29 AM, Thierry Vignaud thierry.vign...@gmail.com wrote: On 22 June 2011 19:41, Florian Hubolddoktor5...@arcor.de wrote: Well, it's quite possible that we have to include that in Mageia 1 as well, as this will be security update for Firefox 4. If we don't want to patch every CVE then we have to include it into Mageia 1 as well.. ... But i think sec team need to speak of FF5 first because i think this will be a candidate for updates regarding new firefox upstream policy Yes, I think Firefox 5 should be an updates. Firefox 5 is a security update for Firefox 4 and 4.0.1. There will be no Firefox 4.0.2. And Firefox 6 will be released in the next two or three months, and will also be a security update to Firefox 5. So we definitely need a policy for that.
Re: [Mageia-dev] Firefox 5
On 23 June 2011 07:58, Dexter Morgan dmorga...@gmail.com wrote: On Thu, Jun 23, 2011 at 7:29 AM, Thierry Vignaud thierry.vign...@gmail.com wrote: On 22 June 2011 19:41, Florian Hubold doktor5...@arcor.de wrote: Well, it's quite possible that we have to include that in Mageia 1 as well, as this will be security update for Firefox 4. If we don't want to patch every CVE then we have to include it into Mageia 1 as well.. Would be nice to know, if this is planned? I have rebuild FF5 here locally for Mageia 1, and the only addons that i lost is Linkification, but that is merely due to it's developers who already messed up with FF4. They don't offer the proper update on Firefox Addons site. So, please, what about Firefox 5 for Mageia 1 as an update (backport?) Humm, MGA is stricter than MDV and refuses to backport packages directly from cauldron: mgarepo submit --define section=core/backports -t 1 /dev/null Submitting xulrunner at revision 110647 URL: svn+ssh://svn.mageia.org/svn/packages/cauldron/xulrunner error: command failed: ssh pkgsubmit.mageia.org /usr/local/bin/submit_package -t 1 --define sid=4845bffd-7f94-4c8c-931e-cfb746d01a0d --define section=core/backports -r 110647 svn+ssh://svn.mageia.org/svn/packages/cauldron/xulrunner error: svn+ssh://svn.mageia.org/svn/packages/cauldron/xulrunner is not allowed for this target yes it needs to go to backports_testing before iirc Got a link to a thread on -dev ML / irc meeting log / insert your favourite communication method here, where this was decided? But i think sec team need to speak of FF5 first because i think this will be a candidate for updates regarding new firefox upstream policy -- Ahmad Samir
Re: [Mageia-dev] Firefox 5
On Thu, Jun 23, 2011 at 9:52 PM, Ahmad Samir ahmadsamir3...@gmail.com wrote: On 23 June 2011 07:58, Dexter Morgan dmorga...@gmail.com wrote: On Thu, Jun 23, 2011 at 7:29 AM, Thierry Vignaud thierry.vign...@gmail.com wrote: On 22 June 2011 19:41, Florian Hubold doktor5...@arcor.de wrote: Well, it's quite possible that we have to include that in Mageia 1 as well, as this will be security update for Firefox 4. If we don't want to patch every CVE then we have to include it into Mageia 1 as well.. Would be nice to know, if this is planned? I have rebuild FF5 here locally for Mageia 1, and the only addons that i lost is Linkification, but that is merely due to it's developers who already messed up with FF4. They don't offer the proper update on Firefox Addons site. So, please, what about Firefox 5 for Mageia 1 as an update (backport?) Humm, MGA is stricter than MDV and refuses to backport packages directly from cauldron: mgarepo submit --define section=core/backports -t 1 /dev/null Submitting xulrunner at revision 110647 URL: svn+ssh://svn.mageia.org/svn/packages/cauldron/xulrunner error: command failed: ssh pkgsubmit.mageia.org /usr/local/bin/submit_package -t 1 --define sid=4845bffd-7f94-4c8c-931e-cfb746d01a0d --define section=core/backports -r 110647 svn+ssh://svn.mageia.org/svn/packages/cauldron/xulrunner error: svn+ssh://svn.mageia.org/svn/packages/cauldron/xulrunner is not allowed for this target yes it needs to go to backports_testing before iirc Got a link to a thread on -dev ML / irc meeting log / insert your favourite communication method here, where this was decided? i told iirc so this is something i recall not something i tell it must be done. i think the most important part of my sentence is the last part but maybe you didn't read it ... But i think sec team need to speak of FF5 first because i think this will be a candidate for updates regarding new firefox upstream policy -- Ahmad Samir
Re: [Mageia-dev] Firefox 5
On 23 June 2011 22:12, Dexter Morgan dmorga...@gmail.com wrote: On Thu, Jun 23, 2011 at 9:52 PM, Ahmad Samir ahmadsamir3...@gmail.com wrote: yes it needs to go to backports_testing before iirc Got a link to a thread on -dev ML / irc meeting log / insert your favourite communication method here, where this was decided? i told iirc so this is something i recall not something i tell it must be done. i think the most important part of my sentence is the last part but maybe you didn't read it ... I did read it, however my question wasn't only about firefox, but rather about the backports policy in general, since your yes it needs to go to backports_testing before iirc wasn't about firefox only, was it? :) But i think sec team need to speak of FF5 first because i think this will be a candidate for updates regarding new firefox upstream policy -- Ahmad Samir -- Ahmad Samir
Re: [Mageia-dev] Firefox 5
On Thu, 23 Jun 2011 15:52:30 -0400, Ahmad Samir ahmadsamir3...@gmail.com wrote: On 23 June 2011 07:58, Dexter Morgan dmorga...@gmail.com wrote: yes it needs to go to backports_testing before iirc Got a link to a thread on -dev ML / irc meeting log / insert your favourite communication method here, where this was decided? This mailing list, thread Release cycles proposals, and discussion, messageid BANLkTimrPR-=ugqonfvakqpft80lni9...@mail.gmail.com Where Anne posted ... exactly what I had in mind. Having backports can allow choice between the last version of and the stable version with which I'm happy with. But indeed we need more quality in backport rpms that is policy and tests. In order for the qa team to perform the tests, before they go to the backports repository, they have to go to to the testing repository first. Something that works in cauldron may not work when moved to backports, if a dependency is missed. By using backports_testing, we can catch that before it hits the average user. Regards, Dave Hodgins
Re: [Mageia-dev] Firefox 5
Le jeudi 23 juin 2011 à 17:48 -0400, David W. Hodgins a écrit : On Thu, 23 Jun 2011 15:52:30 -0400, Ahmad Samir ahmadsamir3...@gmail.com wrote: On 23 June 2011 07:58, Dexter Morgan dmorga...@gmail.com wrote: yes it needs to go to backports_testing before iirc Got a link to a thread on -dev ML / irc meeting log / insert your favourite communication method here, where this was decided? This mailing list, thread Release cycles proposals, and discussion, messageid BANLkTimrPR-=ugqonfvakqpft80lni9...@mail.gmail.com Where Anne posted ... exactly what I had in mind. Having backports can allow choice between the last version of and the stable version with which I'm happy with. But indeed we need more quality in backport rpms that is policy and tests. In order for the qa team to perform the tests, before they go to the backports repository, they have to go to to the testing repository first. Something that works in cauldron may not work when moved to backports, if a dependency is missed. By using backports_testing, we can catch that before it hits the average user. I think the question of ahmad was about backport vs updates. And I think firefox is suitable for the list of package exceptions that should be backported rather than using a patch ( see http://mageia.org/wiki/doku.php?id=updates_policy ). And so, since I guess everybody assume that ff and chromium can go in the list, as they are unsupported upstream _and_ too complex to fix with a patch. And to answer to am -- Michael Scherer
Re: [Mageia-dev] Firefox 5
-Original Message- From: Ahmad Samir ahmadsamir3...@gmail.com Sent: Jun 23, 2011 3:44 PM To: Mageia development mailing-list mageia-dev@mageia.org Subject: Re: [Mageia-dev] Firefox 5 On 23 June 2011 22:12, Dexter Morgan dmorga...@gmail.com wrote: On Thu, Jun 23, 2011 at 9:52 PM, Ahmad Samir ahmadsamir3...@gmail.com wrote: yes it needs to go to backports_testing before iirc Got a link to a thread on -dev ML / irc meeting log / insert your favourite communication method here, where this was decided? i told iirc so this is something i recall not something i tell it must be done. i think the most important part of my sentence is the last part but maybe you didn't read it ... I did read it, however my question wasn't only about firefox, but rather about the backports policy in general, since your yes it needs to go to backports_testing before iirc wasn't about firefox only, was it? :) But i think sec team need to speak of FF5 first because i think this will be a candidate for updates regarding new firefox upstream policy -- Ahmad Samir From what I have been reading due to Mozilla's rapid release schedule it appears that some distros are moving to a standalone version of Firefox. A standalone version means that Firefox does not require a separate libxulrunner package.
Re: [Mageia-dev] Firefox 5
On 23 June 2011 23:48, David W. Hodgins davidwhodg...@gmail.com wrote: On Thu, 23 Jun 2011 15:52:30 -0400, Ahmad Samir ahmadsamir3...@gmail.com wrote: On 23 June 2011 07:58, Dexter Morgan dmorga...@gmail.com wrote: yes it needs to go to backports_testing before iirc Got a link to a thread on -dev ML / irc meeting log / insert your favourite communication method here, where this was decided? This mailing list, thread Release cycles proposals, and discussion, messageid BANLkTimrPR-=ugqonfvakqpft80lni9...@mail.gmail.com Where Anne posted ... exactly what I had in mind. Having backports can allow choice between the last version of and the stable version with which I'm happy with. But indeed we need more quality in backport rpms that is policy and tests. In order for the qa team to perform the tests, before they go to the backports repository, they have to go to to the testing repository first. 1) It doesn't say we're going to use backports_testing, does it? guessing != an instated policy 2) IMHO, QA is too small to handle backports too Something that works in cauldron may not work when moved to backports, if a dependency is missed. By using backports_testing, we can catch that before it hits the average user. Regards, Dave Hodgins Right so, the plan is: - A packager submits to backports_testing and assigns to QA - QA tests, the package is good to go - The report is assigned to whoever has privileges to move packages from backports_testing to backports, atm that's sysadm team - Package is moved and the report closed Caveats: - QA is too small, and it'll take time/effort to get through the backported packages requiring tests, unless you depend on the user asking for the backport to have tested the package properly, the user will say it works if it works on his box for the arch he's using, he won't do both archs, not just because he's lazy, but maybe he has one Mageia box for example - Sysadm team is already overworked with many other tasks, meaning the packages requiring a move will rot for a while in backports_testing. Now compare that to what's used in e.g. mdv: - User asks for a backport - Packager submits the backport and closes the report Do you see the problem I am talking about yet? adding more complexity to backporting may result in less backports; the more the hoops, the less the backports, the more the users' complaints about I-want-the-latest-version-of-foo-yesterday. The quality of backports is a sentence that lacks statistics and numbers; in e.g. mdv, how many packages were backported to release foo? how many of them worked(tm)? how many of them didn't work and required a bit of fixing? how many of them didn't work and won't work due to any number of reasons? I think backports in mdv worked pretty well all those years, not all of them worked, but most of them did. -- Ahmad Samir
Re: [Mageia-dev] Firefox 5
On 24 June 2011 00:06, Michael Scherer m...@zarb.org wrote: Le jeudi 23 juin 2011 à 17:48 -0400, David W. Hodgins a écrit : On Thu, 23 Jun 2011 15:52:30 -0400, Ahmad Samir ahmadsamir3...@gmail.com wrote: On 23 June 2011 07:58, Dexter Morgan dmorga...@gmail.com wrote: yes it needs to go to backports_testing before iirc Got a link to a thread on -dev ML / irc meeting log / insert your favourite communication method here, where this was decided? This mailing list, thread Release cycles proposals, and discussion, messageid BANLkTimrPR-=ugqonfvakqpft80lni9...@mail.gmail.com Where Anne posted ... exactly what I had in mind. Having backports can allow choice between the last version of and the stable version with which I'm happy with. But indeed we need more quality in backport rpms that is policy and tests. In order for the qa team to perform the tests, before they go to the backports repository, they have to go to to the testing repository first. Something that works in cauldron may not work when moved to backports, if a dependency is missed. By using backports_testing, we can catch that before it hits the average user. I think the question of ahmad was about backport vs updates. And I think firefox is suitable for the list of package exceptions that should be backported rather than using a patch ( see http://mageia.org/wiki/doku.php?id=updates_policy ). And so, since I guess everybody assume that ff and chromium can go in the list, as they are unsupported upstream _and_ too complex to fix with a patch. And to answer to am -- Michael Scherer Actually no, I meant the submit to backports privileges vs. only being able to submit to backports_testing. -- Ahmad Samir
Re: [Mageia-dev] Firefox 5
Le vendredi 24 juin 2011 à 01:17 +0300, Ahmad Samir a écrit : On 23 June 2011 23:48, David W. Hodgins davidwhodg...@gmail.com wrote: On Thu, 23 Jun 2011 15:52:30 -0400, Ahmad Samir ahmadsamir3...@gmail.com wrote: On 23 June 2011 07:58, Dexter Morgan dmorga...@gmail.com wrote: yes it needs to go to backports_testing before iirc Got a link to a thread on -dev ML / irc meeting log / insert your favourite communication method here, where this was decided? This mailing list, thread Release cycles proposals, and discussion, messageid BANLkTimrPR-=ugqonfvakqpft80lni9...@mail.gmail.com Where Anne posted ... exactly what I had in mind. Having backports can allow choice between the last version of and the stable version with which I'm happy with. But indeed we need more quality in backport rpms that is policy and tests. In order for the qa team to perform the tests, before they go to the backports repository, they have to go to to the testing repository first. 1) It doesn't say we're going to use backports_testing, does it? guessing != an instated policy 2) IMHO, QA is too small to handle backports too Something that works in cauldron may not work when moved to backports, if a dependency is missed. By using backports_testing, we can catch that before it hits the average user. Regards, Dave Hodgins Right so, the plan is: - A packager submits to backports_testing and assigns to QA - QA tests, the package is good to go - The report is assigned to whoever has privileges to move packages from backports_testing to backports, atm that's sysadm team - Package is moved and the report closed Caveats: - QA is too small, and it'll take time/effort to get through the backported packages requiring tests, unless you depend on the user asking for the backport to have tested the package properly, the user will say it works if it works on his box for the arch he's using, he won't do both archs, not just because he's lazy, but maybe he has one Mageia box for example - Sysadm team is already overworked with many other tasks, meaning the packages requiring a move will rot for a while in backports_testing. Now compare that to what's used in e.g. mdv: - User asks for a backport - Packager submits the backport and closes the report Do you see the problem I am talking about yet? adding more complexity to backporting may result in less backports; the more the hoops, the less the backports, the more the users' complaints about I-want-the-latest-version-of-foo-yesterday. Then we should have a way to turn complaint into productive behavior, like asking to people to do QA of package they request the backport for. The quality of backports is a sentence that lacks statistics and numbers; in e.g. mdv, how many packages were backported to release foo? how many of them worked(tm)? how many of them didn't work and required a bit of fixing? how many of them didn't work and won't work due to any number of reasons? I think backports in mdv worked pretty well all those years, not all of them worked, but most of them did. And everybody said do not use backport, they are not supported, and they can eat your cat if you use them. As said in the meeting, I wanted to send a proposal later for that, but you shooted first, so let's start. Your points are valid, and I took them in account in the proposal, who is based on previous years feedback, based on Stormi ideas mainly, and on your points. So I will open 3 separate thread, to answer to the 3 questions I see : - what process for backports - what policy for backports - what about updates of backports Using 3 mails, I hope to have a more manageable discussion that having a big one. -- Michael Scherer
Re: [Mageia-dev] Firefox 5
Am 16.06.2011 17:14, schrieb Sander Lepik: 16.06.2011 17:18, Daniel Kreuter kirjutas: Ok Mozilla has the RC1 released. Final shall come on Tuesday 21st June so yeah we will include that in Mageia 2 I think (as least this one, maybe FF6 or 7 depending on which version will be available i think) Well, it's quite possible that we have to include that in Mageia 1 as well, as this will be security update for Firefox 4. If we don't want to patch every CVE then we have to include it into Mageia 1 as well.. -- Sander Would be nice to know, if this is planned? I have rebuild FF5 here locally for Mageia 1, and the only addons that i lost is Linkification, but that is merely due to it's developers who already messed up with FF4. They don't offer the proper update on Firefox Addons site. So, please, what about Firefox 5 for Mageia 1 as an update (backport?)
Re: [Mageia-dev] Firefox 5
On 22 June 2011 19:41, Florian Hubold doktor5...@arcor.de wrote: Well, it's quite possible that we have to include that in Mageia 1 as well, as this will be security update for Firefox 4. If we don't want to patch every CVE then we have to include it into Mageia 1 as well.. Would be nice to know, if this is planned? I have rebuild FF5 here locally for Mageia 1, and the only addons that i lost is Linkification, but that is merely due to it's developers who already messed up with FF4. They don't offer the proper update on Firefox Addons site. So, please, what about Firefox 5 for Mageia 1 as an update (backport?) Humm, MGA is stricter than MDV and refuses to backport packages directly from cauldron: mgarepo submit --define section=core/backports -t 1 /dev/null Submitting xulrunner at revision 110647 URL: svn+ssh://svn.mageia.org/svn/packages/cauldron/xulrunner error: command failed: ssh pkgsubmit.mageia.org /usr/local/bin/submit_package -t 1 --define sid=4845bffd-7f94-4c8c-931e-cfb746d01a0d --define section=core/backports -r 110647 svn+ssh://svn.mageia.org/svn/packages/cauldron/xulrunner error: svn+ssh://svn.mageia.org/svn/packages/cauldron/xulrunner is not allowed for this target
Re: [Mageia-dev] Firefox 5
On Thu, Jun 23, 2011 at 7:29 AM, Thierry Vignaud thierry.vign...@gmail.com wrote: On 22 June 2011 19:41, Florian Hubold doktor5...@arcor.de wrote: Well, it's quite possible that we have to include that in Mageia 1 as well, as this will be security update for Firefox 4. If we don't want to patch every CVE then we have to include it into Mageia 1 as well.. Would be nice to know, if this is planned? I have rebuild FF5 here locally for Mageia 1, and the only addons that i lost is Linkification, but that is merely due to it's developers who already messed up with FF4. They don't offer the proper update on Firefox Addons site. So, please, what about Firefox 5 for Mageia 1 as an update (backport?) Humm, MGA is stricter than MDV and refuses to backport packages directly from cauldron: mgarepo submit --define section=core/backports -t 1 /dev/null Submitting xulrunner at revision 110647 URL: svn+ssh://svn.mageia.org/svn/packages/cauldron/xulrunner error: command failed: ssh pkgsubmit.mageia.org /usr/local/bin/submit_package -t 1 --define sid=4845bffd-7f94-4c8c-931e-cfb746d01a0d --define section=core/backports -r 110647 svn+ssh://svn.mageia.org/svn/packages/cauldron/xulrunner error: svn+ssh://svn.mageia.org/svn/packages/cauldron/xulrunner is not allowed for this target yes it needs to go to backports_testing before iirc But i think sec team need to speak of FF5 first because i think this will be a candidate for updates regarding new firefox upstream policy
Re: [Mageia-dev] Firefox 5
On Wed, Jun 15, 2011 at 10:38 PM, Donald Stewart watersnowr...@gmail.comwrote:
On 15 June 2011 13:35, Ahmad Samir ahmadsamir3...@gmail.com wrote:
On 14 June 2011 14:32, Frank Griffin f...@roadrunner.com wrote:
On 06/14/2011 08:22 AM, Thierry Vignaud wrote:
Upgrading stable firefox to firefox5rc and importing
firefox-{beta,aurora}
are two distinct orthogonal things IMHO.
since firefox5 is near being released, I think we should update
main xulrunner+firefox to 5 anyway
Whatever we do, please don't put it in Core to replace FF4 until the
add-ons
have been updated. It was really annoying to lose the Tor add-on for
months
because the beta FF4 just showed up and replaced FF3, and the Tor add-on
wasn't updated until the release or just before.
As I said, we have to have the Beta versions, so as to work out the
niggles to be ready to push the stable version to stable releases
(Mageia 1).
You can always workaround the compatibility, either:
- Adding it manually
http://kb.mozillazine.org/Extensions.checkCompatibility OR
- Using this extension
https://addons.mozilla.org/en-US/firefox/addon/add-on-compatibility-reporter/
in my experience, 90% of the time the addon will work with a new
version of FF (but then again I use a limited number of addons).
--
Ahmad Samir
I'm with Ahmad, going for beta for testing seems right. The beta
release stage should be long enough for issues to be sorted so aurora
isn't needed.
Ok Mozilla has the RC1 released. Final shall come on Tuesday 21st June so
yeah we will include that in Mageia 2 I think (as least this one, maybe FF6
or 7 depending on which version will be available i think)
--
Mit freundlichen Grüßen
Greetings
Daniel Kreuter
Re: [Mageia-dev] Firefox 5
16.06.2011 17:18, Daniel Kreuter kirjutas: Ok Mozilla has the RC1 released. Final shall come on Tuesday 21st June so yeah we will include that in Mageia 2 I think (as least this one, maybe FF6 or 7 depending on which version will be available i think) Well, it's quite possible that we have to include that in Mageia 1 as well, as this will be security update for Firefox 4. If we don't want to patch every CVE then we have to include it into Mageia 1 as well.. -- Sander
Re: [Mageia-dev] Firefox 5
On 14 June 2011 17:54, Antoine Pitrou solip...@pitrou.net wrote: do we wait firefox 5 rc or we can start to update to firefox 5 soon ? Mandriva now has several packages for firefox (like for chromium), following the upstream channels, maybe we could envision doing it too ? As a user, I will download the mozilla.org binaries if I want to try/test a non-stable release. Not sure there's any point for Mageia in packaging beta versions (except to get feedback for distro-specific patches). Well, a mdv package would integrate nicely with gnome kde, aka it would run oowriter to open a document instead of asking you to choose an app...
Re: [Mageia-dev] Firefox 5
On 14 June 2011 17:54, Antoine Pitrou solip...@pitrou.net wrote: On Tue, 14 Jun 2011 14:14:02 +0200 Samuel Verschelde sto...@laposte.net wrote: Le mardi 14 juin 2011 13:56:29, Dexter Morgan a écrit : Hello, do we wait firefox 5 rc or we can start to update to firefox 5 soon ? Mandriva now has several packages for firefox (like for chromium), following the upstream channels, maybe we could envision doing it too ? As a user, I will download the mozilla.org binaries if I want to try/test a non-stable release. Not sure there's any point for Mageia in packaging beta versions (except to get feedback for distro-specific patches). Just my 2 cents. Regards Antoine. The whole alpha/beta/rc concept has changed a lot in Firefox upstream: https://developer.mozilla.org/devnews/index.php/2011/04/07/new-development-channels-and-repositories-for-rapid-releases/ So, we have to have the Beta versions, so as to work out the niggles to be ready to push the stable version to stable releases (Mageia 1). As for Aurora... I don't know I think Beta should be enough, for the brave souls they can use the upstream binary tarballs, I think -- Ahmad Samir
Re: [Mageia-dev] Firefox 5
On 14 June 2011 14:32, Frank Griffin f...@roadrunner.com wrote:
On 06/14/2011 08:22 AM, Thierry Vignaud wrote:
Upgrading stable firefox to firefox5rc and importing firefox-{beta,aurora}
are two distinct orthogonal things IMHO.
since firefox5 is near being released, I think we should update
main xulrunner+firefox to 5 anyway
Whatever we do, please don't put it in Core to replace FF4 until the add-ons
have been updated. It was really annoying to lose the Tor add-on for months
because the beta FF4 just showed up and replaced FF3, and the Tor add-on
wasn't updated until the release or just before.
As I said, we have to have the Beta versions, so as to work out the
niggles to be ready to push the stable version to stable releases
(Mageia 1).
You can always workaround the compatibility, either:
- Adding it manually http://kb.mozillazine.org/Extensions.checkCompatibility OR
- Using this extension
https://addons.mozilla.org/en-US/firefox/addon/add-on-compatibility-reporter/
in my experience, 90% of the time the addon will work with a new
version of FF (but then again I use a limited number of addons).
--
Ahmad Samir
Re: [Mageia-dev] Firefox 5
On 15 June 2011 13:35, Ahmad Samir ahmadsamir3...@gmail.com wrote:
On 14 June 2011 14:32, Frank Griffin f...@roadrunner.com wrote:
On 06/14/2011 08:22 AM, Thierry Vignaud wrote:
Upgrading stable firefox to firefox5rc and importing firefox-{beta,aurora}
are two distinct orthogonal things IMHO.
since firefox5 is near being released, I think we should update
main xulrunner+firefox to 5 anyway
Whatever we do, please don't put it in Core to replace FF4 until the add-ons
have been updated. It was really annoying to lose the Tor add-on for months
because the beta FF4 just showed up and replaced FF3, and the Tor add-on
wasn't updated until the release or just before.
As I said, we have to have the Beta versions, so as to work out the
niggles to be ready to push the stable version to stable releases
(Mageia 1).
You can always workaround the compatibility, either:
- Adding it manually http://kb.mozillazine.org/Extensions.checkCompatibility
OR
- Using this extension
https://addons.mozilla.org/en-US/firefox/addon/add-on-compatibility-reporter/
in my experience, 90% of the time the addon will work with a new
version of FF (but then again I use a limited number of addons).
--
Ahmad Samir
I'm with Ahmad, going for beta for testing seems right. The beta
release stage should be long enough for issues to be sorted so aurora
isn't needed.
[Mageia-dev] Firefox 5
Hello, do we wait firefox 5 rc or we can start to update to firefox 5 soon ?
Re: [Mageia-dev] Firefox 5
Le mardi 14 juin 2011 08:56:29, Dexter Morgan a écrit : Hello, do we wait firefox 5 rc or we can start to update to firefox 5 soon ? I noticed that mandriva is now providing a -stable, -beta and -devel version of firefox, maybe we can use this solution. Regards, -- Balcaen John Jabber ID: mik...@jabber.littleboboy.net
Re: [Mageia-dev] Firefox 5
Le mardi 14 juin 2011 13:56:29, Dexter Morgan a écrit : Hello, do we wait firefox 5 rc or we can start to update to firefox 5 soon ? Mandriva now has several packages for firefox (like for chromium), following the upstream channels, maybe we could envision doing it too ? Samuel
Re: [Mageia-dev] Firefox 5
On Tue, Jun 14, 2011 at 2:13 PM, Balcaen John mik...@mageia.org wrote: Le mardi 14 juin 2011 08:56:29, Dexter Morgan a écrit : Hello, do we wait firefox 5 rc or we can start to update to firefox 5 soon ? I noticed that mandriva is now providing a -stable, -beta and -devel version of firefox, maybe we can use this solution. Regards, -- Balcaen John Jabber ID: mik...@jabber.littleboboy.net We are already using this for the chromium-browser i just noticed that this morning. When I remember correct Mozilla doesn't plan to bring out a RC?? Maybe I'm wrong with that. But providing FF5 for Mga2 would be nice (maybe we can just go to Version 6 or 7 when it's out. When their new release cycle works FF7 will be out before mga2) -- Mit freundlichen Grüßen Greetings Daniel Kreuter
Re: [Mageia-dev] Firefox 5
14.06.2011 15:30, Michael Scherer kirjutas: Le mardi 14 juin 2011 à 14:14 +0200, Samuel Verschelde a écrit : Le mardi 14 juin 2011 13:56:29, Dexter Morgan a écrit : Hello, do we wait firefox 5 rc or we can start to update to firefox 5 soon ? Mandriva now has several packages for firefox (like for chromium), following the upstream channels, maybe we could envision doing it too ? That's 3 times the work however, especially for extensions. IMHO extensions and plugins should be same for all. They might not work but this will be the choice of the user. -- Sander
Re: [Mageia-dev] Firefox 5
14.06.2011 15:32, Frank Griffin kirjutas:
On 06/14/2011 08:22 AM, Thierry Vignaud wrote:
Upgrading stable firefox to firefox5rc and importing firefox-{beta,aurora}
are two distinct orthogonal things IMHO.
since firefox5 is near being released, I think we should update
main xulrunner+firefox to 5 anyway
Whatever we do, please don't put it in Core to replace FF4 until the add-ons have been
updated. It was really annoying to lose the Tor add-on for months because the beta FF4
just showed up and replaced FF3, and the Tor add-on wasn't updated until the release or
just before.
Addons must be updated faster this time around. Firefox 5 will be next security update for
Firefox 4.0.1. This is Mozillas new policy. They won't support Firefox 4 any longer this time.
--
Sander
Re: [Mageia-dev] Firefox 5
On 06/14/2011 08:22 AM, Thierry Vignaud wrote:
Upgrading stable firefox to firefox5rc and importing firefox-{beta,aurora}
are two distinct orthogonal things IMHO.
since firefox5 is near being released, I think we should update
main xulrunner+firefox to 5 anyway
Whatever we do, please don't put it in Core to replace FF4 until the
add-ons have been updated. It was really annoying to lose the Tor
add-on for months because the beta FF4 just showed up and replaced FF3,
and the Tor add-on wasn't updated until the release or just before.
Re: [Mageia-dev] Firefox 5
On 14 June 2011 14:30, Michael Scherer m...@zarb.org wrote: do we wait firefox 5 rc or we can start to update to firefox 5 soon ? Mandriva now has several packages for firefox (like for chromium), following the upstream channels, maybe we could envision doing it too ? That's 3 times the work however, especially for extensions. No. Either they're compat with firefox-4/5/6 or not (any combinaison)
Re: [Mageia-dev] Firefox 5
On Tue, 14 Jun 2011 14:14:02 +0200 Samuel Verschelde sto...@laposte.net wrote: Le mardi 14 juin 2011 13:56:29, Dexter Morgan a écrit : Hello, do we wait firefox 5 rc or we can start to update to firefox 5 soon ? Mandriva now has several packages for firefox (like for chromium), following the upstream channels, maybe we could envision doing it too ? As a user, I will download the mozilla.org binaries if I want to try/test a non-stable release. Not sure there's any point for Mageia in packaging beta versions (except to get feedback for distro-specific patches). Just my 2 cents. Regards Antoine.
