Documentation/release-schedule.txt

   1 Release schedule
   2 ----------------
   3
   4 The util-linux uses <major>.<minor>.<maint> version numbering.
   5 Since the major version is pretty much fixed the release means an
   6 upgrade of minor number. Minor version is update roughly twice
   7 per year. Easiest way to estimate when next version will occur is
   8 to see time stamp of previous release.
   9
  10 Before a release there are few release candidates, which will be
  11 collectively tested. During test period changes to code base are
  12 restricted. Usually there are two release candidates.
  13
  14   what   lenght         what will be accepted to upstream
  15   -------------------------------------------------------
  16   rc1    1-2 weeks      bug fixes only
  17   rc2    1-2 weeks      translations, fatal/trivial bug fixes
  18
  19 The period between a release and next release candidate can be considered as
  20 merge window.
  21
  22 Release criteria
  23 ----------------
  24
  25 For all releases is required:
  26
  27    - make checkincludes pass
  28    - make checkconfig pass
  29    - make distcheck pass
  30    - cd tests && ./run.sh pass
  31    - out-of-tree build works
  32      cd .. && mkdir build && cd build && ../util-linux/configure && make
  33
  34    - ideally: build with uClibc, --with-slang
  35
  36 See also
  37 --------
  38
  39 Documentation/source-code-management.txt