What should we do with iceweasel/xulrunner/libmozjs?

2011-02-18 Thread Mike Hommey
Hi, Now that squeeze is released, it's time to start pushing new things to unstable. I've been asked several times already how things would be evolving in the near future, to which I answered it would quite stay the way it is now until upstream releases 4.0, at which point I'd upload 4.0 to

Re: What should we do with iceweasel/xulrunner/libmozjs?

2011-02-18 Thread Benjamin Drung
Am Freitag, den 18.02.2011, 10:12 +0100 schrieb Mike Hommey: Hi, Now that squeeze is released, it's time to start pushing new things to unstable. I've been asked several times already how things would be evolving in the near future, to which I answered it would quite stay the way it is now

Re: What should we do with iceweasel/xulrunner/libmozjs?

2011-02-18 Thread Marco d'Itri
On Feb 18, Mike Hommey m...@glandium.org wrote: - Suggest your own if you have better ideas (really, I mean it). I support option #2: I have been using it since you started packaging it and it works great: better than 3.6 and hugely better than 3.5. s390, sparc and ia64 are not exactly popular

Re: What should we do with iceweasel/xulrunner/libmozjs?

2011-02-18 Thread Mike Hommey
On Fri, Feb 18, 2011 at 10:12:42AM +0100, Mike Hommey wrote: snip As I mentioned above, my initial idea was to go with the second option, breaking most rdeps in the process, but then I remembered that 4.0 doesn't work on all our architectures, and I'm hesitating, now. So, fellow developers,

Re: What should we do with iceweasel/xulrunner/libmozjs?

2011-02-18 Thread Axel Beckert
Hi, Mike Hommey wrote: - Push 3.6 to unstable and the last 4.0 betas/rc to experimental. Push 4.0 to unstable when it's out. That would be my favourite. I use Conkeror (which is a XULRunner application and hence depends on xulrunner) with 3.6 since it is in experimental and it works without

Re: What should we do with iceweasel/xulrunner/libmozjs?

2011-02-18 Thread Josselin Mouette
Le vendredi 18 février 2011 à 10:29 +0100, Benjamin Drung a écrit : I favor a combination of idea one and two, which is: Keep 3.5 in unstable and push the last 4.0 betas/rc to experimental. Push 4.0 to unstable when it's out. Then we have one big break and a tested 4.0 in unstable. I’d

Re: What should we do with iceweasel/xulrunner/libmozjs?

2011-02-18 Thread Adam Borowski
On Fri, Feb 18, 2011 at 10:12:42AM +0100, Mike Hommey wrote: [iceweasel] - Push 3.6 to unstable and the last 4.0 betas/rc to experimental. Push 4.0 to unstable when it's out. Extra effort for you. - Keep 3.5 in unstable, 3.6 in experimental, and push 4.0 to experimental when it's

Re: What should we do with iceweasel/xulrunner/libmozjs?

2011-02-18 Thread Mike Hommey
On Fri, Feb 18, 2011 at 12:59:46PM +0100, Josselin Mouette wrote: Le vendredi 18 février 2011 à 10:29 +0100, Benjamin Drung a écrit : I favor a combination of idea one and two, which is: Keep 3.5 in unstable and push the last 4.0 betas/rc to experimental. Push 4.0 to unstable when it's

Re: What should we do with iceweasel/xulrunner/libmozjs?

2011-02-18 Thread Josselin Mouette
Le vendredi 18 février 2011 à 13:34 +0100, Mike Hommey a écrit : On Fri, Feb 18, 2011 at 12:59:46PM +0100, Josselin Mouette wrote: I’d favor that one too. The sooner we can adapt reverse dependencies to 4.0 in experimental, the better. And no need to do the work twice. There have been

Re: What should we do with iceweasel/xulrunner/libmozjs?

2011-02-18 Thread Ron Johnson
On 02/18/2011 05:42 AM, Axel Beckert wrote: Hi, Mike Hommey wrote: - Push 3.6 to unstable and the last 4.0 betas/rc to experimental. Push 4.0 to unstable when it's out. That would be my favourite. I use Conkeror (which is a XULRunner application and hence depends on xulrunner) with 3.6