Ticket #4357 (closed task: fixed)
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
Attachments
Change History
comment:2 Changed 3 years ago by andrew_b
- Blocking 4358 added
(In #4358) Thanks!
Applied in 4357_cleanup branch.
comment:3 Changed 3 years ago by andrew_b
Merged to master: [6f2833a422bcca69d7924b7425f3fcde48e873a0].
git log --pretty-oneline 0e583d756..6f2833a42
comment:5 Changed 3 years ago by andrew_b
Branch: 4357_cleanup
Initial changeset:52fd6215b0bdfc07c34729ab379948ac6742319a
comment:6 Changed 3 years ago by andrew_b
mc-4357-input.c-fix-maybe-uninitialize-warning.patch: applied.
comment:7 Changed 2 years ago by andrew_b
- Blocking 4400 added
(In #4400) Thanks!
Committed to 4357_cleanup branch.
comment:8 Changed 2 years ago by andrew_b
Merged to master: [38bd3ece9e5a65b5c679d570bc86216f09117a0c].
git log --pretty=oneline e48cd98ac..38bd3ece9
comment:10 Changed 2 years 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.
comment:11 Changed 2 years 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
TODO:
- write an announcement: list user visible changes (bugs and features)
- close ticket for release
- close current milestone
comment:12 Changed 2 years 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 2 years ago by zaytsev
- Status changed from new to closed
- Resolution set to fixed
Tarballs rebuilt, tag pushed, announcement sent.
Branch: 4357_cleanup
Initial changeset:a046fd678e8fc33a80cd62b0d5ad288678823696