[ACTION REQUIRED v4] Retiring packages for F-18

Toshio Kuratomi a.badger at gmail.com
Fri Jul 27 18:29:20 UTC 2012


On Fri, Jul 27, 2012 at 11:11:24AM -0700, Jesse Keating wrote:
> On 07/27/2012 10:15 AM, Toshio Kuratomi wrote:
> >For endusers, the date is more handy for seeing whether the package is based
> >on newer or older upstream versions than the scm's hash.
> 
> But do we specifically say what you're supposed to put in the date
> field?  Is it the date the hash was created?  The date the hash was
> added to a specific branch?  The date the hash was checked out by the
> Fedora dev and built in the build system?
> 
> The guidelines say at one place that the date used should be the date
> the snapshot was made, which can be pretty disconnected from the date
> the hash was created or merged.
> 
> A date without clear rules or context is just meaningless digits.
> 
That's hyperbolic.  A date tells you something meaningful even if it is
specifying something that turns out to be a range of valid entries.

I might not know if 20120106 is more recent code than 20110610 but I know
that it isn't older code, for instance.

-Toshio
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20120727/566452a6/attachment.sig>


More information about the devel mailing list