From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: Karel Zak <kzak@redhat.com>, util-linux@vger.kernel.org
Subject: Re: versioning
Date: Wed, 17 May 2017 12:36:09 -0500 [thread overview]
Message-ID: <591C8A09.6070100@gmail.com> (raw)
In-Reply-To: <20170517074741.ltxnoawwvj56gc3m@ws.net.home>
Karel Zak wrote:
>
> Hi,
>
> Sami has good point on IRC... do we really want to continue with the
> current versioning schema? Now we use:
>
> v2.xx[.y]
>
> I don't expect v3 or v4, so the prefix v2 does not provide any
> information... and the 'xx' ('30' now) is already large number.
>
> Suggestions:
>
> 1) do nothing; nobody cares and v2.31 looks good
>
> 2) remove '2' from the version:
>
> major release: v31
> update release: v31.1
>
>
> 3) <your suggestion>?
In managing about 1000 packages, I see a lot of different version
numbering. The vast majority of packages use (my terminology)
major.minor.point for numbering. The major number really should only be
increased when there are incompatibilities introduced in a package update.
Sometimes the numbering gets large, For instance the current lvm2 package
number is 2.02.171. But that is OK. It tells us that the packages is
updated frequently, but there is an effort to maintain backward compatibility.
When a package like firefox is at 53.0.2, what does that tell us about the
changes?
Sometimes the numbering is downright silly. I'll suggest that chromium at
58.0.3029.96 falls into that category.
To give you an idea of what other packages use, take a look at
http://wiki.linuxfromscratch.org/blfs/browser/trunk/BOOK/packages.ent
The bottom line is that from our point of view, x.y.z works fine. There
is no need to change the current numbering scheme.
-- Bruce Dubbs
linuxfromscratch.org
next prev parent reply other threads:[~2017-05-17 17:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 7:47 versioning Karel Zak
2017-05-17 8:42 ` versioning Ruediger Meier
2017-05-17 8:47 ` versioning Ruediger Meier
2017-05-17 13:23 ` versioning Bernhard Voelker
2017-05-17 13:51 ` versioning Karel Zak
2017-05-17 15:04 ` versioning Karel Zak
2017-05-17 16:08 ` versioning Ruediger Meier
2017-05-17 17:36 ` Bruce Dubbs [this message]
2017-05-17 19:07 ` versioning Ruediger Meier
2017-05-17 21:09 ` versioning Karel Zak
2017-05-18 9:29 ` versioning Sami Kerola
2017-05-18 10:36 ` versioning Karel Zak
2017-05-18 18:08 ` versioning J William Piggott
2017-05-18 19:56 ` versioning Karel Zak
2017-05-18 20:55 ` versioning Rüdiger Meier
2017-05-19 8:12 ` versioning Karel Zak
2017-05-19 19:00 ` versioning J William Piggott
2017-05-20 19:34 ` versioning Karel Zak
2017-05-22 21:37 ` versioning J William Piggott
2017-05-23 7:57 ` versioning Karel Zak
2017-05-23 8:05 ` versioning Karel Zak
2017-05-23 20:54 ` versioning J William Piggott
2017-05-24 10:02 ` versioning Ruediger Meier
2017-05-27 18:55 ` versioning J William Piggott
2017-05-29 10:22 ` versioning Karel Zak
2017-05-18 10:43 ` versioning Ruediger Meier
2017-05-17 17:46 ` versioning J William Piggott
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=591C8A09.6070100@gmail.com \
--to=bruce.dubbs@gmail.com \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox