Ticket #4357 (closed task: fixed)

Opened 2 years ago

Last modified 13 months ago

Prepare for release mc-4.8.29

Reported by: zaytsev Owned by:
Priority: major Milestone: 4.8.29
Component: adm Version: master
Keywords: Cc:
Blocked By: Blocking:
Branch state: no branch Votes for changeset:

Description


Change History

comment:1 Changed 2 years ago by andrew_b

Last edited 22 months ago by andrew_b (previous) (diff)

comment:2 Changed 2 years ago by andrew_b

  • Blocking 4358 added

(In #4358) Thahks!
Applied in 4357_cleanup branch.

Version 0, edited 2 years ago by andrew_b (next)

comment:3 Changed 21 months ago by andrew_b

Merged to master: [6f2833a422bcca69d7924b7425f3fcde48e873a0].

git log --pretty-oneline 0e583d756..6f2833a42

comment:4 Changed 21 months ago by andrew_b

  • Blocking 4358 removed

comment:5 Changed 20 months ago by andrew_b

Last edited 17 months ago by andrew_b (previous) (diff)

comment:6 Changed 20 months ago by andrew_b

mc-4357-input.c-fix-maybe-uninitialize-warning.patch​: applied.

comment:7 Changed 18 months ago by andrew_b

  • Blocking 4400 added

(In #4400) Thanks!

Committed to 4357_cleanup branch.

comment:8 Changed 16 months ago by andrew_b

Merged to master: [38bd3ece9e5a65b5c679d570bc86216f09117a0c].

git log --pretty=oneline e48cd98ac..38bd3ece9

comment:9 Changed 16 months ago by andrew_b

  • Blocking 4400 removed

comment:10 Changed 14 months ago by cieply

If changes (like mc.ext in ini format and There is no fallback to previous mc.ext format) are so deep, why won't you call new version 4.9? Maybe keeping build count. That would be 4.9.29. Major version and then minor are more important than "build" or whatever you call the last number.

Last edited 14 months ago by cieply (previous) (diff)

comment:11 Changed 13 months ago by zaytsev

  • prepare repository for release
  • download PO-translations from Transifex.net
  • store translations in git repo
  • download the hint translations from Transifex.net
  • store translations in git repo
  • create new NEWS wiki page for next version
  • add content of current NEWS wiki page to the doc/NEWS file
  • new version in Trac
  • new milestone in Trac
  • create new tag in git
  • create tar.(bz2|xz) package files
  • make checksums for archives
  • upload source packages and checksums to the special upload area
  • developers should download tarballs, verify checksums, compile and install locally
  • upload source packages and checksums
  • run trigger
  • update Wiki start page with latest release number
  • create new ticket (type=task, component=adm) for the next release

#4426

TODO:

  • write an announcement: list user visible changes (bugs and features)
  • close ticket for release
  • close current milestone

comment:12 Changed 13 months ago by zaytsev

Tarballs will be rebuilt after the new tag is set, because a number of bugs have been discovered immediately after the release process.

comment:13 Changed 13 months ago by zaytsev

  • Status changed from new to closed
  • Resolution set to fixed

Tarballs rebuilt, tag pushed, announcement sent.

Note: See TracTickets for help on using tickets.