Bug#815006: Renaming Iceweasel to Firefox

[Mike Hommey]

mmmm, I had meant to send this to the bug, but somehow, the bug wasn't
in the Cc list...

Does the security team (now CCed) have a comment to make about stable
(see further below)?

On Thu, Feb 18, 2016 at 07:23:32AM +0900, Mike Hommey wrote:
> On Wed, Feb 17, 2016 at 04:55:42PM +0100, Sylvestre Ledru wrote:
> > diff --git a/debian/control.in b/debian/control.in
> > index 56184ad..b5785a0 100644
> > --- a/debian/control.in
> > +++ b/debian/control.in
> > @@ -1,4 +1,4 @@
> > -Source: iceweasel
> > +Source: firefox
> >  Section: web
> >  Priority: optional
> >  Maintainer: Maintainers of Mozilla-related packages <pkg-mozilla-maintainers at lists.alioth.debian.org>
> > @@ -159,6 +159,15 @@ Description: Development files for the Gecko engine library
> >   same form as the one you may find on mozilla.org in /usr/lib/xulrunner/sdk.
> >  Homepage: http://wiki.mozilla.org/XUL:Lib_XUL
> >  
> > +%if browser == OFFICIAL_NAME
> > +Package: iceweasel
> > +Architecture: any
> > +Depends: @browser@
> > +Description: Mozilla Firefox web browser - transition package
> > + This is a transition package to the Firefox browser
> > +%endif
> 
> Don't we want the full Depends/Conflicts/Breaks boilerplate here?
> 
> On a separate note, what do we do for stable? Not necessarily for the
> coming version bump with 45, but the next one next year. Undoubtedly the
> branding is going to break somewhere in the middle (it broke multiple
> times between 38 and 45), and that will go unnoticed until then.
> 
> Also, there's the longstanding issue that we don't have much legroom
> for new releases, and where, for the longest time, releases are on
> experimental and esr on unstable/testing.
> 
> While it's unrelated, I think it's about time to introduce 2 packages,
> one firefox-esr, and one firefox. We may or may not decide to make only
> the former ship to stable, but that's something that doesn't need to be
> decided now. I think there's enough value having both esr and release
> available in testing/unstable.
> 
> IIRC, the packaging kind of supports this already, although there might
> need some minor adjustments.
> 
> Which bring me to this thought: maybe upload a firefox package now that
> doesn't have the iceweasel transition package, wait for 45 to be released,
> upload firefox 45 and firefox-esr 45 with the latter providing a
> transitional iceweasel package depending on it, so that iceweasel users
> end up on firefox-esr.
> 
> Mike