On Wed, 2009-01-28 at 21:00 +0530, Rahul Sundaram wrote: > Mark McLoughlin wrote: > > On Wed, 2009-01-28 at 15:50 +0530, Rahul Sundaram wrote: > >> Mark McLoughlin wrote: > >> > >>> I'd suggest the tone should be less prescriptive - i.e. not so much "you > >>> must do foo" - and also give some rationale. > >>> > >>> e.g. "when preparing your update, consider what the user will see and > >>> how they will decide whether they should apply the update". > >> I am probably not going to be very good at doing this. Do you want to try? > > > > Okay, here's an attempt: > > > > https://fedoraproject.org/wiki/User:Markmc/Draft_package_update_guidelines > > Thanks. I have made a minor edit making it explicit that this doesn't > apply to rawhide or new packages. Looks good to me. I will be sending > this over to FESCo (cc'ing Jon Stanley) unless anybody has other > specific feedback. > How about this rewording in the first sentence: from "to update a package on a release branch" to "to update a package on an already-released branch" to make it clearer that it's only talking about updates to released versions of Fedora. -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
