ericonr
/
util-linux
mirror of https://github.com/ericonr/util-linux.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

docs: improve grammar and wording of the release-schedule text 

Signed-off-by: Benno Schulenberg <bensberg@justemail.net>
This commit is contained in:
Benno Schulenberg 2013-10-05 18:08:59 +02:00 committed by Karel Zak
parent e9c58f6d55
commit 55fb046138
1 changed files with 21 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

41
Documentation/release-schedule.txt
View File

@ -1,37 +1,38 @@
Release schedule Release schedule
---------------- ----------------
The util-linux uses <major>.<minor>.<maint> version numbering. The util-linux package uses the <major>.<minor>.<maintenaince> version
Since the major version is pretty much fixed the release means an numbering scheme. Since the major version is pretty much fixed, any
upgrade of minor number. Minor version is update roughly twice release means an increment of the minor number. The minor version is
per year. Easiest way to estimate when next version will occur is incremented roughly twice per year. The easiest way to estimate when
to see time stamp of previous release. the next version will appear, is to look at the time stamp of the last
release.
Before a release there are few release candidates, which will be Before each release there are a few release candidates, which will be
collectively tested. During test period changes to code base are collectively tested. During the test period changes to the code base
restricted. Usually there are two release candidates. are restricted. Usually there are two release candidates.
what length what will be accepted to upstream what length what will be accepted into upstream
------------------------------------------------------- ---------------------------------------------------------
rc1 1-2 weeks bug fixes only rc1 1-2 weeks bug fixes only
rc2 1-2 weeks translations, fatal/trivial bug fixes rc2 1-2 weeks translations, fatal/trivial bug fixes
The period between a release and next release candidate can be considered as The period between a release and the next release candidate can be considered
merge window. as the merge window.
Release criteria Release criteria
---------------- ----------------
For all releases is required: For all releases it is required that:
- make checkincludes pass - make checkincludes passes
- make checkconfig pass - make checkconfig passes
- make distcheck pass - make distcheck passes
- cd tests && ./run.sh pass - cd tests && ./run.sh passes
- out-of-tree build works - an out-of-tree build works
cd .. && mkdir build && cd build && ../util-linux/configure && make (cd .. && mkdir build && cd build && ../util-linux/configure && make)
- ideally: build with uClibc, --with-slang - ideally: a build with uClibc works, and --with-slang works
See also See also
-------- --------