Gentoo Archives: gentoo-dev

From: Mike Frysinger <vapier@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-arch/bzip2: bzip2-1.0.5-r1.ebuild
Date: Tue, 07 Jun 2011 23:01:19
Message-Id: 201106071824.52253.vapier@gentoo.org
In Reply to: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-arch/bzip2: bzip2-1.0.5-r1.ebuild by Matt Turner
1 On Tuesday, June 07, 2011 18:08:17 Matt Turner wrote:
2 > There _was_ a policy before, but it was unclear about documenting
3 > version removals and arguably didn't require it, so after a few
4 > developers (you've been often mentioned as one of them) refused to
5 > document version removals in the changelog, even after prompting on
6 > gentoo-dev@ the council fixed the policy.
7
8 i'm aware of the history. it still doesnt validate the logic cited earlier.
9
10 > Of course the policy doesn't exist simply because you disagree with
11 > others, the policy exists (and was instituted/clarified) because you
12 > wouldn't do something that most developers and users find useful and
13 > thought was already policy, even after being asked.
14 >
15 > Why does this have to be such a struggle. It's pretty clear that the
16 > policy is going to be changed again to fix the oversight of silly
17 > situations like I mentioned previously, but there's a near unanimous
18 > agreement that documenting version removals _is_ useful. So, please,
19 > just start doing it. It's really not a lot of work. I'm sure something
20 > more can be done to make this more automated, but until then please
21 > just fucking do it and let's stop all this silliness.
22
23 seems we gauge things differently as i dont think it's that black & white,
24 although it probably is further in your white than in my black. further, i
25 dont believe people actually get useful information out of this, they just
26 think they do (perception vs reality). when an actual bug arises, the
27 information contained in the ChangeLog doesnt assist in the bug triage/fixing.
28 depgraph broken -> file removed -> reason is irrelevant to the user.
29 maintainer of the package causing the depgraph breakage gets a bug in bugzilla
30 and they address it by either re-adding, or trimming more, or tweaking deps,
31 or something else. so if someone wants a fuzzy security blanket, they can
32 look to autogeneration and then it's no longer my problem.
33 -mike

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies