From: Petr Lautrbach <plautrba@redhat.com>
To: "selinux@vger.kernel.org" <selinux@vger.kernel.org>
Cc: hukeping <hukeping@huawei.com>,
"Zhengjunling (JRing, Task Force)" <zhengjunling@huawei.com>,
zhuangbiaowei <zhuangbiaowei@huawei.com>
Subject: Re: [RFC] Introduce MAJOR.MINOR.PATCH version for the whole project
Date: Mon, 23 Nov 2020 12:55:13 +0100 [thread overview]
Message-ID: <87d004wan2.fsf@redhat.com> (raw)
In-Reply-To: <f80deaf6f99c47f8a5a2bf88540c27c0@huawei.com>
hukeping <hukeping@huawei.com> writes:
> The current release tag for the whole project is 20200710<https://github.com/SELinuxProject/selinux/tree/20200710> , and for components is major.minor, for example: selinux-sandbox-3.1, libselinux-3.1
>
> Can we use the same type of version for the whole project for convenience?
I've no problem with this change. We would need to be update in
`scripts/release`.
If there's no objection from others I'll prepare a
patch so we can start with this starting 3.2.
Btw it's not relly MAJOR.MINOR, it's just X.Y. There were some big
changes in 2.3 and also the next release 3.2 will contain API/ABI
incompatible changes.
Petr
parent reply other threads:[~2020-11-23 11:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <f80deaf6f99c47f8a5a2bf88540c27c0@huawei.com>]
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=87d004wan2.fsf@redhat.com \
--to=plautrba@redhat.com \
--cc=hukeping@huawei.com \
--cc=selinux@vger.kernel.org \
--cc=zhengjunling@huawei.com \
--cc=zhuangbiaowei@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).