Hi,
with this mail, I propose we drop support for FireFox > 2 releases in rapps. The motivation is crystal clear: with their new release plan, they are releasing too often, and they don't maintain old links nor they provide a symbolic link to latest version. So, FireFox links in rapps are too often dead. So, they require a constant attention we can't offer (we have other cats to fry!). So, let's drop these multiple versions from rapps, and let just our 2.0. This will let users install a web browser and then install the browser they like using it.
Anyone against this proposal? Otherwise, I'll drop all those links in a week.
Regards, Pierre
Hi Pierre,
Why not just drop support for FF entirely from rapps? I'd say better no browser than a terribly outdated one.
If users want FF they can do this: C:\ReactOS> ftp ftp> open ftp.mozilla.org ftp> cd pub/firefox/releases/8.0/win32/en-GB ftp> get Firefox Setup 8.0.exe
;)
On 15 January 2012 15:26, Pierre Schweitzer pierre@reactos.org wrote:
Hi,
with this mail, I propose we drop support for FireFox > 2 releases in rapps. The motivation is crystal clear: with their new release plan, they are releasing too often, and they don't maintain old links nor they provide a symbolic link to latest version. So, FireFox links in rapps are too often dead. So, they require a constant attention we can't offer (we have other cats to fry!). So, let's drop these multiple versions from rapps, and let just our 2.0. This will let users install a web browser and then install the browser they like using it.
Anyone against this proposal? Otherwise, I'll drop all those links in a week.
Regards, Pierre
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Op 15-1-2012 16:34, Andrew Faulds schreef:
Why not just drop support for FF entirely from rapps? I'd say better no browser than a terribly outdated one.
If users want FF they can do this: C:\ReactOS> ftp ftp> open ftp.mozilla.org ftp> cd pub/firefox/releases/8.0/win32/en-GB ftp> get Firefox Setup 8.0.exe
You're a version behind already ^^ Perhaps they should create a "/current" or "/latest" and offer "FireFox Setup.exe" there.
I'm not understanding the original mail. Is it proposed to: a) drop all FireFox versions? b) only offer version 2.0 ? Why 2.0 specific? c) only offer 2 versions? One modern and 1 reference/test?
As usefull as old versions are for regression testing, users generally like having an updated, or latest, version of everything.
When installing Windows the first thing done also is opening Internet Explorer to download FF (Chrome or Chromium could also, I guess), and for me that's the last time IE is used.
Le dimanche 15 janvier 2012 à 16:51 +0100, Bernd Blaauw a écrit :
Op 15-1-2012 16:34, Andrew Faulds schreef:
Why not just drop support for FF entirely from rapps? I'd say better no browser than a terribly outdated one.
If users want FF they can do this: C:\ReactOS> ftp ftp> open ftp.mozilla.org ftp> cd pub/firefox/releases/8.0/win32/en-GB ftp> get Firefox Setup 8.0.exe
This is not suitable. We have to keep something user-friendly. And regarding that point, as usual, the less CLI, the better.
b) only offer version 2.0 ? Why 2.0 specific?
Yes. Because 2.0 is frozen and we provide exe download on our servers.
c) only offer 2 versions? One modern and 1 reference/test?
The was done before, but once again regarding the releasing method of FF this isn't possible any longer.
As usefull as old versions are for regression testing, users generally like having an updated, or latest, version of everything.
This is why they would have FF2. To download the last available version.
On 15.01.2012 16:51, Bernd Blaauw wrote:
Op 15-1-2012 16:34, Andrew Faulds schreef:
Why not just drop support for FF entirely from rapps? I'd say better no browser than a terribly outdated one.
If users want FF they can do this: C:\ReactOS> ftp ftp> open ftp.mozilla.org ftp> cd pub/firefox/releases/8.0/win32/en-GB ftp> get Firefox Setup 8.0.exe
You're a version behind already ^^ Perhaps they should create a "/current" or "/latest" and offer "FireFox Setup.exe" there.
At least on their "high bandwidth FTP server" releases.mozilla.org (see the message when opening ftp.mozilla.org in a web browser) there is a "latest" in their FireFox folder: http://releases.mozilla.org/pub/mozilla.org/firefox/releases/
Regards, Sven
Ah yes, good point. I just randomly guessed ftp.mozilla.org - but it doesn't allow downloads of high-traffic releases.
On 15 January 2012 17:16, Sven Barth pascaldragon@googlemail.com wrote:
On 15.01.2012 16:51, Bernd Blaauw wrote:
Op 15-1-2012 16:34, Andrew Faulds schreef:
Why not just drop support for FF entirely from rapps? I'd say better no browser than a terribly outdated one.
If users want FF they can do this: C:\ReactOS> ftp ftp> open ftp.mozilla.org ftp> cd pub/firefox/releases/8.0/win32/en-GB ftp> get Firefox Setup 8.0.exe
You're a version behind already ^^ Perhaps they should create a "/current" or "/latest" and offer "FireFox Setup.exe" there.
At least on their "high bandwidth FTP server" releases.mozilla.org (see the message when opening ftp.mozilla.org in a web browser) there is a "latest" in their FireFox folder: http://releases.mozilla.org/pub/mozilla.org/firefox/releases/
Regards, Sven
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Guys, you know that we already host FF 2 on our SVN Server? Check the link. It will NEVER become outdated
Am 15.01.2012 19:04, schrieb Andrew Faulds:
Ah yes, good point. I just randomly guessed ftp.mozilla.org - but it doesn't allow downloads of high-traffic releases.
On 15 January 2012 17:16, Sven Barthpascaldragon@googlemail.com wrote:
On 15.01.2012 16:51, Bernd Blaauw wrote:
Op 15-1-2012 16:34, Andrew Faulds schreef:
Why not just drop support for FF entirely from rapps? I'd say better no browser than a terribly outdated one.
If users want FF they can do this: C:\ReactOS> ftp ftp> open ftp.mozilla.org ftp> cd pub/firefox/releases/8.0/win32/en-GB ftp> get Firefox Setup 8.0.exe
You're a version behind already ^^ Perhaps they should create a "/current" or "/latest" and offer "FireFox Setup.exe" there.
At least on their "high bandwidth FTP server" releases.mozilla.org (see the message when opening ftp.mozilla.org in a web browser) there is a "latest" in their FireFox folder: http://releases.mozilla.org/pub/mozilla.org/firefox/releases/
Regards, Sven
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
You know that we're not talking about FF 2, but newer releases?
Pierre already wrote that he wants to keep FF 2 in his original mail, but we're trying to convince him/the rest to allow a newer release as well.
Btw: Mozilla wants to publish "long term support" releases in the next time (based either on FF 8 or FF 9) which shall be supported around ~45 weeks. Maybe this will be a solution?
Regards, Sven
On 15.01.2012 19:56, Daniel Reimer wrote:
Guys, you know that we already host FF 2 on our SVN Server? Check the link. It will NEVER become outdated
Am 15.01.2012 19:04, schrieb Andrew Faulds:
Ah yes, good point. I just randomly guessed ftp.mozilla.org - but it doesn't allow downloads of high-traffic releases.
On 15 January 2012 17:16, Sven Barthpascaldragon@googlemail.com wrote:
On 15.01.2012 16:51, Bernd Blaauw wrote:
Op 15-1-2012 16:34, Andrew Faulds schreef:
Why not just drop support for FF entirely from rapps? I'd say better no browser than a terribly outdated one.
If users want FF they can do this: C:\ReactOS> ftp ftp> open ftp.mozilla.org ftp> cd pub/firefox/releases/8.0/win32/en-GB ftp> get Firefox Setup 8.0.exe
You're a version behind already ^^ Perhaps they should create a "/current" or "/latest" and offer "FireFox Setup.exe" there.
At least on their "high bandwidth FTP server" releases.mozilla.org (see the message when opening ftp.mozilla.org in a web browser) there is a "latest" in their FireFox folder: http://releases.mozilla.org/pub/mozilla.org/firefox/releases/
Regards, Sven
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
If ROS is going to drop FF rosapps support, i would upload a newer FF version to SVN (2.x is too outdated) and restart with it.
On Sun, Jan 15, 2012 at 8:05 PM, Sven Barth pascaldragon@googlemail.comwrote:
You know that we're not talking about FF 2, but newer releases?
Pierre already wrote that he wants to keep FF 2 in his original mail, but we're trying to convince him/the rest to allow a newer release as well.
Btw: Mozilla wants to publish "long term support" releases in the next time (based either on FF 8 or FF 9) which shall be supported around ~45 weeks. Maybe this will be a solution?
Regards, Sven
On 15.01.2012 19:56, Daniel Reimer wrote:
Guys, you know that we already host FF 2 on our SVN Server? Check the link. It will NEVER become outdated
Am 15.01.2012 19:04, schrieb Andrew Faulds:
Ah yes, good point. I just randomly guessed ftp.mozilla.org - but it doesn't allow downloads of high-traffic releases.
On 15 January 2012 17:16, Sven Barth<pascaldragon@googlemail.**compascaldragon@googlemail.com> wrote:
On 15.01.2012 16:51, Bernd Blaauw wrote:
Op 15-1-2012 16:34, Andrew Faulds schreef:
Why not just drop support for FF entirely from rapps? I'd say better no browser than a terribly outdated one.
If users want FF they can do this: C:\ReactOS> ftp ftp> open ftp.mozilla.org ftp> cd pub/firefox/releases/8.0/**win32/en-GB ftp> get Firefox Setup 8.0.exe
You're a version behind already ^^ Perhaps they should create a "/current" or "/latest" and offer "FireFox Setup.exe" there.
At least on their "high bandwidth FTP server" releases.mozilla.org (see the message when opening ftp.mozilla.org in a web browser) there is a "latest" in their FireFox folder: http://releases.mozilla.org/**pub/mozilla.org/firefox/**releases/http://releases.mozilla.org/pub/mozilla.org/firefox/releases/
Regards, Sven
______________________________**_________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/**mailman/listinfo/ros-devhttp://www.reactos.org/mailman/listinfo/ros-dev
______________________________**_________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/**mailman/listinfo/ros-devhttp://www.reactos.org/mailman/listinfo/ros-dev
______________________________**_________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/**mailman/listinfo/ros-devhttp://www.reactos.org/mailman/listinfo/ros-dev
Le dimanche 15 janvier 2012 à 20:05 +0100, Sven Barth a écrit :
Btw: Mozilla wants to publish "long term support" releases in the next time (based either on FF 8 or FF 9) which shall be supported around ~45 weeks. Maybe this will be a solution?
The main problem is not that they easily jump version number. The problem is that they release too often. Even if we get stuck at some LTS, if they release X.0.[1..100] every month, that won't do the job.
Is the download link provided by Microsoft's browser choice web page static? You could always link to that for the latest release.
http://www.browserchoice.eu http://go.microsoft.com/fwlink/?LinkID=166932
-----Original Message----- From: ros-dev-bounces@reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of Pierre Schweitzer Sent: 15 January 2012 21:58 To: ros-dev@reactos.org Subject: Re: [ros-dev] Proposal for FF support drop
Le dimanche 15 janvier 2012 à 20:05 +0100, Sven Barth a écrit :
Btw: Mozilla wants to publish "long term support" releases in the next time (based either on FF 8 or FF 9) which shall be supported around ~45 weeks. Maybe this will be a solution?
The main problem is not that they easily jump version number. The problem is that they release too often. Even if we get stuck at some LTS, if they release X.0.[1..100] every month, that won't do the job.
That actually redirects to: http://download-eu.mozilla.org/?product=firefox-latest-euballot&os=win&a... which redirects to latest exe.
So we should use that URL. (removing the -euballot breaks it, it seems, so it only works for the EU ballot version)
On 15 January 2012 22:16, Ged Murphy gedmurphy.maillists@gmail.com wrote:
Is the download link provided by Microsoft's browser choice web page static? You could always link to that for the latest release.
http://www.browserchoice.eu http://go.microsoft.com/fwlink/?LinkID=166932
-----Original Message----- From: ros-dev-bounces@reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of Pierre Schweitzer Sent: 15 January 2012 21:58 To: ros-dev@reactos.org Subject: Re: [ros-dev] Proposal for FF support drop
Le dimanche 15 janvier 2012 à 20:05 +0100, Sven Barth a écrit :
Btw: Mozilla wants to publish "long term support" releases in the next time (based either on FF 8 or FF 9) which shall be supported around ~45 weeks. Maybe this will be a solution?
The main problem is not that they easily jump version number. The problem is that they release too often. Even if we get stuck at some LTS, if they release X.0.[1..100] every month, that won't do the job.
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Le dimanche 15 janvier 2012 à 22:25 +0000, Andrew Faulds a écrit :
That actually redirects to: http://download-eu.mozilla.org/?product=firefox-latest-euballot&os=win&a... which redirects to latest exe.
So we should use that URL. (removing the -euballot breaks it, it seems, so it only works for the EU ballot version)
It appears we have here the solution. And it even supports language selection.
Last point: do we really need FireFox 3.6 support? Which is also in rapps?
Since 3.6 is obsolete, I'd personally not keep it.
I'd say we should have FF2 and FF "latest".
On 16 January 2012 19:07, Pierre Schweitzer pierre@reactos.org wrote:
Le dimanche 15 janvier 2012 à 22:25 +0000, Andrew Faulds a écrit :
That actually redirects to: http://download-eu.mozilla.org/?product=firefox-latest-euballot&os=win&a... which redirects to latest exe.
So we should use that URL. (removing the -euballot breaks it, it seems, so it only works for the EU ballot version)
It appears we have here the solution. And it even supports language selection.
Last point: do we really need FireFox 3.6 support? Which is also in rapps?
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Since 3.6 is obsolete, I'd personally not keep it.
I'd say we should have FF2 and FF "latest".
FF2 is even more obsolete than FF3.6 I'd just keep the more stable version of each app. Rapps is supposed to be a showroom of apps working "relatively" well in ReactOS. It doesn't have too much sense of showing apps which doesnt work at all, unless they are regressions..and we should try to fix them.
On 16 January 2012 19:07, Pierre Schweitzer pierre@reactos.org wrote:
Le dimanche 15 janvier 2012 à 22:25 +0000, Andrew Faulds a écrit :
That actually redirects to: http://download-eu.mozilla.org/?product=firefox-latest-euballot&os=win&a... which redirects to latest exe.
So we should use that URL. (removing the -euballot breaks it, it seems, so it only works for the EU ballot version)
It appears we have here the solution. And it even supports language selection.
Last point: do we really need FireFox 3.6 support? Which is also in rapps?
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
-- Andrew Faulds (AJF) http://ajf.me/
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Again, why cant we host a file with all the links in some format, like xml, accessible via (Win)SCP and simply point Rapps to download it? This way, we can edit it relatively easy, without any fuss and wasting commits. A simple, daily copy for backup would suffice, with one month of upkeep. This file doesn't really need to be in svn...
On Mon, Jan 16, 2012, at 07:42 PM, victor martinez wrote:
Since 3.6 is obsolete, I'd personally not keep it.
I'd say we should have FF2 and FF "latest".
FF2 is even more obsolete than FF3.6 I'd just keep the more stable version of each app. Rapps is supposed to be a showroom of apps working "relatively" well in ReactOS. It doesn't have too much sense of showing apps which doesnt work at all, unless they are regressions..and we should try to fix them.
On 16 January 2012 19:07, Pierre Schweitzer pierre@reactos.org wrote:
Le dimanche 15 janvier 2012 à 22:25 +0000, Andrew Faulds a écrit :
That actually redirects to: http://download-eu.mozilla.org/?product=firefox-latest-euballot&os=win&a... which redirects to latest exe.
So we should use that URL. (removing the -euballot breaks it, it seems, so it only works for the EU ballot version)
It appears we have here the solution. And it even supports language selection.
Last point: do we really need FireFox 3.6 support? Which is also in rapps?
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
-- Andrew Faulds (AJF) http://ajf.me/
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Yeah, it surprises me we don't already do this. Rapps requires an internet connection anyway, so making it download the apps list isn't a problem.
On 16 January 2012 20:41, caemyr@myopera.com wrote:
Again, why cant we host a file with all the links in some format, like xml, accessible via (Win)SCP and simply point Rapps to download it? This way, we can edit it relatively easy, without any fuss and wasting commits. A simple, daily copy for backup would suffice, with one month of upkeep. This file doesn't really need to be in svn...
On Mon, Jan 16, 2012, at 07:42 PM, victor martinez wrote:
Since 3.6 is obsolete, I'd personally not keep it.
I'd say we should have FF2 and FF "latest".
FF2 is even more obsolete than FF3.6 I'd just keep the more stable version of each app. Rapps is supposed to be a showroom of apps working "relatively" well in ReactOS. It doesn't have too much sense of showing apps which doesnt work at all, unless they are regressions..and we should try to fix them.
On 16 January 2012 19:07, Pierre Schweitzer pierre@reactos.org wrote:
Le dimanche 15 janvier 2012 à 22:25 +0000, Andrew Faulds a écrit :
That actually redirects to: http://download-eu.mozilla.org/?product=firefox-latest-euballot&os=win&a... which redirects to latest exe.
So we should use that URL. (removing the -euballot breaks it, it seems, so it only works for the EU ballot version)
It appears we have here the solution. And it even supports language selection.
Last point: do we really need FireFox 3.6 support? Which is also in rapps?
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
-- Andrew Faulds (AJF) http://ajf.me/
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
-- With best regards Caemyr
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Am 16.01.2012 21:57, schrieb Andrew Faulds:
Yeah, it surprises me we don't already do this. Rapps requires an internet connection anyway, so making it download the apps list isn't a problem.
It's already done that way since ages. What we would need is an easy to use webinterface to update the links and a script, running on a daily basis detecting broken links.
It's already done that way since ages. What we would need is an easy to use webinterface to update the links and a script, running on a daily basis detecting broken links.
Yes. The file is downloaded the first time RAPPS is run and used to fill all the sections. Just to add some more info..
If so, why does updating links needs SVN commit?? It should be placed beyond SVN.
On Tue, Jan 17, 2012, at 09:41 AM, Timo Kreuzer wrote:
Am 16.01.2012 21:57, schrieb Andrew Faulds:
Yeah, it surprises me we don't already do this. Rapps requires an internet connection anyway, so making it download the apps list isn't a problem.
It's already done that way since ages. What we would need is an easy to use webinterface to update the links and a script, running on a daily basis detecting broken links.
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Op 15-1-2012 19:56, Daniel Reimer schreef:
Guys, you know that we already host FF 2 on our SVN Server? Check the link. It will NEVER become outdated
Oops the link displayed by rapps includes a version number in the binary instead of some [ ftp://ftp.reactos.org/reactos/rapps/firefox-2in32.exe ]. Would it be possible to replace the hosted binary by version 9.01 and create a symlink on the server so the 2.0.20 link stays working but downloads 9.0 instead?
Slightly offtopic: any public notes available of the most recent (December/January) private meeting? Unless it's private private ofcourse.
Le dimanche 15 janvier 2012 à 20:19 +0100, Bernd Blaauw a écrit :
Oops the link displayed by rapps includes a version number in the binary instead of some [ ftp://ftp.reactos.org/reactos/rapps/firefox-2in32.exe ]. Would it be possible to replace the hosted binary by version 9.01 and create a symlink on the server so the 2.0.20 link stays working but downloads 9.0 instead?
This would, indeed, solve the problem of broken link, but not the problem of outdated version. And imagine everyone would be releasing that way... We can't host half-the web just for having working rapps.
Major point also is that 2.0 is only available in English (it's more here for reg-testing purposes). All the other releases are proposed in several langages. We can't host a binary for every supported language. Or we become an official Mozilla mirror, but that's not planned.
One thing I could do, is putting some php script on one of our servers (something like that: foo.reactos.org/getFireFox.php?lang=en-US), that would use the link pointed by Sven Barth to get latest version and redirect to it. A bit overkill, but could do job.
Slightly offtopic: any public notes available of the most recent (December/January) private meeting? Unless it's private private ofcourse.
They should be available any time soon. Only few parts of the meeting were private.
+1 for this
On Sun, Jan 15, 2012 at 6:16 PM, Sven Barth pascaldragon@googlemail.comwrote:
On 15.01.2012 16:51, Bernd Blaauw wrote:
Op 15-1-2012 16:34, Andrew Faulds schreef:
Why not just drop support for FF entirely from rapps? I'd say better no browser than a terribly outdated one.
If users want FF they can do this: C:\ReactOS> ftp ftp> open ftp.mozilla.org ftp> cd pub/firefox/releases/8.0/**win32/en-GB ftp> get Firefox Setup 8.0.exe
You're a version behind already ^^ Perhaps they should create a "/current" or "/latest" and offer "FireFox Setup.exe" there.
At least on their "high bandwidth FTP server" releases.mozilla.org (see the message when opening ftp.mozilla.org in a web browser) there is a "latest" in their FireFox folder: http://releases.mozilla.org/** pub/mozilla.org/firefox/**releases/http://releases.mozilla.org/pub/mozilla.org/firefox/releases/
Regards, Sven
______________________________**_________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/**mailman/listinfo/ros-devhttp://www.reactos.org/mailman/listinfo/ros-dev
Le dimanche 15 janvier 2012 à 18:16 +0100, Sven Barth a écrit :
At least on their "high bandwidth FTP server" releases.mozilla.org (see the message when opening ftp.mozilla.org in a web browser) there is a "latest" in their FireFox folder: http://releases.mozilla.org/pub/mozilla.org/firefox/releases/
Unfortunately, this won't help. If we follow the latest link, we end with that link: http://releases.mozilla.org/pub/mozilla.org/firefox/releases/latest/win32/en... We still have version number in link, and it will be outdated in a short while.
What they should do would be more something like: http://releases.mozilla.org/pub/mozilla.org/firefox/releases/latest/win32/en... That would be ALWAYS pointing to the latest version. This would be helpful.
Maybe we could email mozilla and ask them to do this when releasing?
On 15 January 2012 21:44, Pierre Schweitzer pierre@reactos.org wrote:
Le dimanche 15 janvier 2012 à 18:16 +0100, Sven Barth a écrit :
At least on their "high bandwidth FTP server" releases.mozilla.org (see the message when opening ftp.mozilla.org in a web browser) there is a "latest" in their FireFox folder: http://releases.mozilla.org/pub/mozilla.org/firefox/releases/
Unfortunately, this won't help. If we follow the latest link, we end with that link: http://releases.mozilla.org/pub/mozilla.org/firefox/releases/latest/win32/en... We still have version number in link, and it will be outdated in a short while.
What they should do would be more something like: http://releases.mozilla.org/pub/mozilla.org/firefox/releases/latest/win32/en... That would be ALWAYS pointing to the latest version. This would be helpful.
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Why not to upload FF into some other place? I can host zip.
From: Pierre Schweitzer pierre@reactos.org To: ros-dev@reactos.org Sent: Sunday, 15 January 2012, 17:26 Subject: [ros-dev] Proposal for FF support drop
Hi,
with this mail, I propose we drop support for FireFox > 2 releases in rapps. The motivation is crystal clear: with their new release plan, they are releasing too often, and they don't maintain old links nor they provide a symbolic link to latest version. So, FireFox links in rapps are too often dead. So, they require a constant attention we can't offer (we have other cats to fry!). So, let's drop these multiple versions from rapps, and let just our 2.0. This will let users install a web browser and then install the browser they like using it.
Anyone against this proposal? Otherwise, I'll drop all those links in a week.
Regards, Pierre
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev