On Mon, Jun 13, 2016 at 01:56:54PM +0100, Daniel P. Berrange wrote: [Snip some nice analysis about libvirt versioning history.] > I venture to suggest that the reasons for switching from feature to > time based release schedules, also apply to version numbers. IOW we > should switch to a time based version number change rule, instead of > a feature based version number change rule. > > > So what I'm suggesting is that we adopt the following rule > > - major: bumped for the first release of each year > - minor: bumped for every major release > - micro: bumped for stable branch releases > [...] > The stable release branch naming would just use the first major + minor > digit in its name.. eg the stable branch for 2.3.0 would use v2.3-maint > and do stable releases 2.3.1, 2.3.2, 2.3.3, etc. FWIW, as a user of libvirt, this proposed change is nice, and will be more clearer. -- /kashyap -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list