* Re: [RFC] Introduce MAJOR.MINOR.PATCH version for the whole project [not found] <f80deaf6f99c47f8a5a2bf88540c27c0@huawei.com> @ 2020-11-23 11:55 ` Petr Lautrbach 0 siblings, 0 replies; only message in thread From: Petr Lautrbach @ 2020-11-23 11:55 UTC (permalink / raw) To: selinux@vger.kernel.org Cc: hukeping, Zhengjunling (JRing, Task Force), zhuangbiaowei 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 ^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-11-23 11:55 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <f80deaf6f99c47f8a5a2bf88540c27c0@huawei.com>
2020-11-23 11:55 ` [RFC] Introduce MAJOR.MINOR.PATCH version for the whole project Petr Lautrbach
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox