-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jeroen Roovers wrote:
>      Hi fellow developers,
> 
> 
> it seems I've run into a minor issue with fellow bug wrangler carlo
> (who has been putting a lot of work into that, for which we should all
> be grateful).
> 
> Carsten has a cut-and-paste message that he posts in comments to
> version bump bug reports that he finds have been filed on the day the
> software version in question was released/announced. The gist of the
> message is that none of or most ebuild developers do not like these
> "0-day requests" and that users (and developers) should refrain from
> filing them on the same day. Waiting a week would be OK, the message
> seems to say.
> 
> Being an ebuild developer myself, I have to say that I do not hold that
> stance and that I welcome early version bump requests. Therefore, I
> refrain from adding such messages to the bugs that I wrangle and indeed
> welcome any bump requests[1].
> 
> Finding myself in conflict with someone I have come to share a certain
> workload with, notably someone who has a few more years of Gentoo
> experience, I wonder what the majority of our ebuild developers
> actually think. In that spirit, I hope the following questions are
> neutral enough for everyone to *not* start a flamewar over this. :)
> 
> 
> -----
> 1) How do you feel when you receive an early version bump request?

Since current mores make sure there are not so many, I don't mind them.

> 2) If you had your way, would you discourage users from filing early
> version bump requests?

To prevent every package from getting a 0-day bump request, I'd say give it a
day or two at least, unless you have some info other than that there is a new
version. For example that the current ebuild still works with the new version or
that it doesn't. It helps with gauging which bumps are trivial and which aren't.

If someone only wants to tell me some new version is out, I prefer they ping me
on irc.

> -----
> 
> I know, it's not a particularly good survey, but I hope the plenty and
> diversity of your answers will shed more light on the matter. :)
> 
> 
> Thank you and kind regards,
>      JeR
> 
> 
> [1] In fact I regularly use the opportunity to check on the HOMEPAGE
> whether the release was security related, and I assign directly to
> security@ when that is the case (CC'ing the package's maintainers) and
> perhaps pasting ChangeLog or advisory info in a comment.

Marijn

- --
Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML
<http://www.gentoo.org/proj/en/lisp/>, #gentoo-{lisp,ml} on FreeNode
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkht4WkACgkQp/VmCx0OL2xJ6QCfbX/IvrzARx3AY2FzAHW4sD2P
TasAn2NTD0c+HE0ehaG3wd9bFdk+yzSh
=pj1H
-----END PGP SIGNATURE-----
-- 
gentoo-dev@g.o mailing list