From: Steve Lawrence <slawrence@tresys.com>
To: SELinux <selinux@tycho.nsa.gov>
Subject: Bumping Version Numbers
Date: Tue, 26 Jul 2011 11:30:09 -0400 [thread overview]
Message-ID: <4E2EDD81.8080608@tresys.com> (raw)
A while ago ago we discussed bumping the minor version number and
resetting the revision version number when we do a release [1]. We are
now preparing for a release and wanted some feedback before we bumped
the version numbers.
We're thinking of only bumping minor version numbers if the revision
version number is non-zero.
So the version numbers will become:
checkpolicy-2.1.0
libselinux-2.1.0
libsepol-2.1.0
libsemanage-2.1.0
policycoreutils-2.1.0
sepolgen-1.1.0
We could alternatively always bump minor version numbers even if the
revision number was zero (i.e. no changes since the last release). This
has the advantange that all releases share the same version number. If
we do that, it might make sense to bump sepolgen to 2.1.0 this release
as well, unless there is some significance between 1.x and 2.x with
sepolgen.
Thoughts?
- Steve
[1] http://marc.info/?t=129962368300001&r=1&w=2
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next reply other threads:[~2011-07-26 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 15:30 Steve Lawrence [this message]
2011-07-26 17:51 ` Bumping Version Numbers Stephen Smalley
2011-07-26 18:04 ` Eric Paris
2011-07-27 14:53 ` Steve Lawrence
2011-07-26 18:10 ` Daniel J Walsh
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=4E2EDD81.8080608@tresys.com \
--to=slawrence@tresys.com \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.