Re: Draft: simple update description guidelines

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

 



On Tue, Jan 27, 2009 at 11:48:45PM +0530, Rahul Sundaram wrote:
> * All Updates must refer to a upstream changelog or equivalent if one  
> exists. Otherwise a brief description (a couple of sentence at most)  
> justifying the need for an update must be provided by the maintainers  
> pushing the update.

I'm happy this applies only to released versions of Fedora[1].  But I
think this should also exclude 'newpackage' updates explicitly (ie.
where a new package is added to a released version of Fedora).

Rich.

[1] Although it will certainly mean I feel much less inclined to just
upgrade any released packages unless there's a security issue.

-- 
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

-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux