On 05/01/2017 05:15 AM, Niels de Vos wrote: >> [2] Tag for 3.11.0beta1 : >> https://github.com/gluster/glusterfs/tree/v3.11.0beta1 > > With tags like this we need to add a release note that users who tested > packages with this version will need to downgrade when GA is done. This > is because > > $ rpmdev-vercmp 3.11.0beta1 3.11.0-1 > 3.11.0beta1 > 3.11.0-1 > > The previous scheme (like 3.10rc1) forced updates to users when the .0 > release became available. Why was this changed?
It hasn't been changed. There has bee sloppiness with the tags used for betas and RCs in the past. We had some tags like v3.8rc1 and v3.8.0rc2. I asked that we be consistent and expressed a slight preference for 3.11.0rc1 as it makes fedora packaging slightly less painful. And, e.g., in fedora packages we use — per Fedora guidelines — an NVR of 3.10.0-0.1rc1 [1]. When we GA the NVR becomes 3.10.0-1 and upgrades "just work." -- Kaleb [1] We've had to respin builds of a few of the RCs, so there hasn't always been a strict 0.x -> RCx mapping. We've had things like 3.8.0-0.1rc1, 3.8.0-0.2rc1, 3.8.0-0.3rc2, ...
signature.asc
Description: OpenPGP digital signature
_______________________________________________ maintainers mailing list [email protected] http://lists.gluster.org/mailman/listinfo/maintainers
