lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 16 Oct 2007 23:01:49 -0400
From:	Dave Jones <>
To:	Pavel Roskin <>
Cc:	linux-kernel <>
Subject: Re: Distinguishing releases from pre-rc snapshots

On Tue, Oct 16, 2007 at 10:45:17PM -0400, Pavel Roskin wrote:
 > On Tue, 2007-10-16 at 22:34 -0400, Dave Jones wrote:
 > > On Tue, Oct 16, 2007 at 10:22:43PM -0400, Pavel Roskin wrote:
 > > 
 > >  > It would be nice to establish a rule to increment the version number
 > >  > immediately after the kernel release and have a suffix to indicate that
 > >  > it's a pre-rc version.  "rc0" is my personal favorite.
 > > 
 > > fwiw, rc0 is also what the Fedora kernel uses for versioning when we're
 > > shipping pre-rc1 kernels.
 > Thanks!  I didn't think of the possibility of anyone distributing
 > precompiled kernels from the "pre-rc" window, but if Fedora does it
 > (hopefully for beta-testers only), it should be absolutely clear that
 > it's not just a release with some minor fixes.

yeah, this is just in our 'development' pool (also known as 'rawhide')
Proper releases only ever get full point releases + -stable as updates.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists