projects / thirdparty / util-linux.git / blame
| Commit | Line | Data |
|---|---|---|
| b6459b51 SK |
1 | Release schedule |
| 2 | ---------------- | |
| 3 | ||
| 55fb0461 BS |
4 | The util-linux package uses the <major>.<minor>.<maintenaince> version |
| 5 | numbering scheme. Since the major version is pretty much fixed, any | |
| 6 | release means an increment of the minor number. The minor version is | |
| 7 | incremented roughly twice per year. The easiest way to estimate when | |
| 8 | the next version will appear, is to look at the time stamp of the last | |
| 9 | release. | |
| 10 | ||
| 11 | Before each release there are a few release candidates, which will be | |
| 12 | collectively tested. During the test period changes to the code base | |
| 13 | are restricted. Usually there are two release candidates. | |
| 14 | ||
| 15 | what length what will be accepted into upstream | |
| 16 | --------------------------------------------------------- | |
| b6459b51 SK |
17 | rc1 1-2 weeks bug fixes only |
| 18 | rc2 1-2 weeks translations, fatal/trivial bug fixes | |
| 19 | ||
| 55fb0461 BS |
20 | The period between a release and the next release candidate can be considered |
| 21 | as the merge window. | |
| b6459b51 | 22 | |
| 2b70f022 KZ |
23 | The release tarball is generated by "make distcheck" command. |
| 24 | ||
| b6459b51 SK |
25 | Release criteria |
| 26 | ---------------- | |
| 27 | ||
| 55fb0461 | 28 | For all releases it is required that: |
| b6459b51 | 29 | |
| 55fb0461 BS |
30 | - make checkincludes passes |
| 31 | - make checkconfig passes | |
| 32 | - make distcheck passes | |
| 33 | - cd tests && ./run.sh passes | |
| 34 | - an out-of-tree build works | |
| 35 | (cd .. && mkdir build && cd build && ../util-linux/configure && make) | |
| b6459b51 | 36 | |
| 55fb0461 | 37 | - ideally: a build with uClibc works, and --with-slang works |
| b6459b51 SK |
38 | |
| 39 | See also | |
| 40 | -------- | |
| 41 | ||
| 42 | Documentation/source-code-management.txt |