8:57 a.m.
-----Original Message-----
From: fedora-devel-list-bounces(a)redhat.com
[mailto:fedora-devel-list-bounces@redhat.com]On Behalf Of
Ralf Corsepius
Sent: Tuesday, January 27, 2009 9:50 AM
To: Development discussions related to Fedora
Subject: Re: how to show upstream changes to the user
Jóhann B. Guðmundsson wrote:
> Michael Schwendt wrote:
>> On Tue, 27 Jan 2009 13:57:34 +0100, Dan wrote:
>
> This tell testers absolutely nothing
>
> - New upstream version
> - Update to
Untrue. It tells those people who are interested into
details, to look
into upstreams.
Ralf
Please don't force packagers to have to bug upstream about what changed. Unless
another set of Fedora people
want to dig for that information to update the packager. Some of us don't have the
time to nag upstream about what they changed.
Be happy you GET a package, don't be greedy :)
--
fedora-devel-list mailing list
fedora-devel-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
9:13 a.m.
New subject: how to show upstream changes to the user
Shawn Starr wrote:
> -----Original Message-----
> From: fedora-devel-list-bounces(a)redhat.com
> [mailto:fedora-devel-list-bounces@redhat.com]On Behalf Of
> Ralf Corsepius
> Sent: Tuesday, January 27, 2009 9:50 AM
> To: Development discussions related to Fedora
> Subject: Re: how to show upstream changes to the user
>
>
> Jóhann B. Guðmundsson wrote:
>> Michael Schwendt wrote:
>>> On Tue, 27 Jan 2009 13:57:34 +0100, Dan wrote:
>> This tell testers absolutely nothing
>>
>> - New upstream version
>> - Update to
> Untrue. It tells those people who are interested into
> details, to look
> into upstreams.
>
> Ralf
Please don't force packagers to have to bug upstream about what changed.
To put this clear: I do not want these changelog URLs and consider
Mr. Sundaram's proposal to be a unhelpful campaign to adding yet more
bureaucracy to the already overboarding bureaucracy, package maintainers
in Fedora are confronted with.
Unless another set of Fedora people
want to dig for that information to update the packager.
Some of us don't have the time to nag upstream about what they
changed.
Agreed.
Be happy you GET a package, don't be greedy :)
Agreed.
Ralf
10:04 a.m.
New subject: how to show upstream changes to the user
Shawn Starr (sstarr(a)platform.com) said:
Please don't force packagers to have to bug upstream about what
changed. Unless another set of Fedora people
want to dig for that information to update the packager. Some of us don't have the
time to nag upstream about what they changed.
If you don't have the time to find out, *as a maintainer*, what changed,
you shouldn't be maintaining it.
Bill
1:38 p.m.
New subject: how to show upstream changes to the user
On Tue, Jan 27, 2009 at 11:04:47AM -0500, Bill Nottingham wrote:
Shawn Starr (sstarr(a)platform.com) said:
> Please don't force packagers to have to bug upstream about what changed. Unless
another set of Fedora people
> want to dig for that information to update the packager. Some of us don't have
the time to nag upstream about what they changed.
If you don't have the time to find out, *as a maintainer*, what changed,
you shouldn't be maintaining it.
I don't think that's true at all. As a *packager*, my job is to
package correctly and respond to packaging bugs. Sometimes that
involves a little bit of code maintenance -- so you need to be a jack
of all trades^Wprogramming languages -- but I am by no means an expert
on the ins and outs of every version of every package I look after.
Rich.
--
Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones
virt-p2v converts physical machines to virtual machines. Boot with a
live CD or over the network (PXE) and turn machines into Xen guests.
http://et.redhat.com/~rjones/virt-p2v
10:50 a.m.
New subject: how to show upstream changes to the user
Richard W.M. Jones (rjones(a)redhat.com) said:
> If you don't have the time to find out, *as a maintainer*,
what changed,
> you shouldn't be maintaining it.
I don't think that's true at all. As a *packager*, my job is to
package correctly and respond to packaging bugs. Sometimes that
involves a little bit of code maintenance -- so you need to be a jack
of all trades^Wprogramming languages -- but I am by no means an expert
on the ins and outs of every version of every package I look after.
'Expert on the ins and outs'? You don't have to be able to rewrite
the program from scratch, but you should at least *look* when there's
a new release to get some idea of what changed, if for no other reason
than that will help you if you get bugs on it later.
Bill
5569
days inactive
5570
days old
4 comments
4 participants
participants (4)
-
Bill Nottingham -
Ralf Corsepius -
Richard W.M. Jones -
Shawn Starr