[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#765732: marked as done (unblock: firetray/0.5.2 [Pre-approval])

Your message dated Mon, 20 Oct 2014 22:37:24 -0400
with message-id <5445C6E4.9010001@debian.org>
and subject line Re: Bug#765732: unblock: firetray/0.5.2 [Pre-approval]
has caused the Debian Bug report #765732,
regarding unblock: firetray/0.5.2 [Pre-approval]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
765732: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765732
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Hi

I’d like to request in advance an unblock of package firetray.

The current version 0.4.8 of firetray in Sid and Jessie is one year old.
The upcoming version 0.5 fixes at least one important bug (#719545).
The 0.5 branch is updated in experimental for three months now.

More detailed explanation:

The 0.5 branch is mature [1] in my humble opinion, but the current amo
review process will a priori delay the actual 0.5.2 version to be
published early November.

	1: the diffstat between 0.5.1~rc1+dfsg-1 and 0.5.2~rc1+dfsg-1 is
	   not too big:
	     14 files changed, 143 insertions(+), 96 deletions(-)

I’m uneasy to publish an RC version of firetray to unstable so close to
the freeze, but if you’d pre-approve the principle of unblocking the
final release, that could be a worthy option.

The actual diffstat between the version 0.4.8 currently in Jessie and
the latest 0.5.2~rc1+dfsg-1 in experimental is huge:
  147 files changed, 5694 insertions(+), 2507 deletions(-)
and I’d prefer not imposing its review to you, that’s why I’m looking
for advice in advance.

unblock firetray/0.5.2

If the current amo review process of the latest 0.5.2~rc1 succeeds, the
upstream diff between 0.5.2~rc1 and should be null, but if it fails,
I’d propose to unblock firetray/0.5.3 with a hopefully minimal diff.

(Of course, if firetray becomes incompatible with the latest version of
Mozilla products pushed by the security team, I may propose a more
insane upgrade latter during the freeze or even during Jessie’s
lifetime, but that shouldn’t stop us to try and follow the more
rationale course of action if possible…)

Thanks in advance for considering.

Regards

David

P.-S.: sorry to bother with so many words for a such a non important
       request.

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Emilio,

Le 20/10/2014 13:10, Emilio Pozuelo Monfort a écrit :
> On 17/10/14 18:06, David Prévot wrote:

> It's not very clear to me what you're asking here.

I was merely seeking for advice (the situation is/was not all clear to
me). Thank you for taking the time to answer and provide some.

> So it's up to you to upload to sid now, get 0.5.2~rc1 into testing, and
> then ask for a (minor) update to 0.5.2 final in November, or stay at 0.4.8.

Thank you for sharing your thoughts. I finally made up my mind and
uploaded it to Sid. I’ll follow up later if needed/it’s worth it, so
let’s remove this issue from your radar in the mean time.

Regards

David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBCAAGBQJURcbkAAoJEAWMHPlE9r08jxIH/3ML0+W19ogc/kHMy65v9rXe
bLwWtgm1eGMLLxfw1Z4LSrfC05Otqeaiv4Bx9erObQghw9t1tz7+407vuuFxu106
K666ZKtUjMCmePVidExYVKMYxwG3rZZICJ/0Q6imHrPZtO+d8D/YFgtgSM2vzJJt
PiqCEPpkUWQ5Cfu8tyaEFVIFqWbu+pyBedz8yj8RrPGChhPVQPTvYhiJNvd414+s
96dAjczdHj4lhilIZ1l1mkGyxwn2fbP5ZsmTTdM96IendRseYpiH6rCgRzAB105m
7VaOHEEs+Wm5wr++5Vbb75Tze66e2lUiS+Vfxs7mBvjaSiE6GtUxUzF8pONNGlo=
=HNCp
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: