ReleaseEngineering - Revision history

Admin: 13 revisions imported

2016-04-06T20:36:15Z

13 revisions imported

← Older revision		Revision as of 16:36, 6 April 2016
(No difference)

67.183.142.187: /* • Update and release RT::Client::CLI */ Fix code block with a nowiki tag.

2013-08-13T00:47:35Z

• Update and release RT::Client::CLI: Fix code block with a nowiki tag.

← Older revision		Revision as of 20:47, 12 August 2013
Line 86:		Line 86:
	milla authordeps \| cpanm		milla authordeps \| cpanm
	milla test		milla test
	vim Changes # add notes to Changes file under {{$NEXT}}		vim Changes # add notes to Changes file under <nowiki>{{$NEXT}}</nowiki>
	milla release # specify correct 4.0.x version		milla release # specify correct 4.0.x version

67.183.142.187: How to release RT::Client::CLI when a new RT version is out

2013-08-13T00:02:50Z

How to release RT::Client::CLI when a new RT version is out

← Older revision		Revision as of 20:02, 12 August 2013
Line 74:		Line 74:

	See checkmarkable.		See checkmarkable.

			=== • Update and release RT::Client::CLI ===

			You may skip this if bin/rt.in is unchanged from the last RT release (and RT::Client::CLI is up to date with the last release).

			cd RT-Client-CLI/
			./devel/import-rt
			git diff
			git commit -am 'Update to 4.0.x'
			git push
			milla authordeps \| cpanm
			milla test
			vim Changes # add notes to Changes file under {{$NEXT}}
			milla release # specify correct 4.0.x version

			The last step will increment version numbers, tag, commit, upload to cpan, and push it all to git, with a prompt or two in between.

	=== • Cleanup and preserve history ===		=== • Cleanup and preserve history ===

67.183.142.187: Flip path names around for docs and release-notes

2013-08-12T23:57:21Z

Flip path names around for docs and release-notes

← Older revision		Revision as of 19:57, 12 August 2013
Line 26:		Line 26:
	make snapshot		make snapshot

	This will build you a snapshot tarball, GPG sign it and give you SHA1 sums. On 3.8, you'll need to sign and generate SHA1 sums yourself:		This will build you a snapshot tarball, GPG sign it and give you SHA1 sums. On 3.8, you'll need to sign and generate SHA1 sums yourself:

	gpg --detach-sign rt-3.8.18.tar.gz		gpg --detach-sign rt-3.8.18.tar.gz
	sha1sum rt-3.8.18.tar.gz*		sha1sum rt-3.8.18.tar.gz*

	Do not skip reconfiguring, as it ensures you have a fresh build and Makefile. This is especially important if you're releasing 4.0 and 3.8 at the same time from the same clone (i.e. rolling security releases).		Do not skip reconfiguring, as it ensures you have a fresh build and Makefile. This is especially important if you're releasing 4.0 and 3.8 at the same time from the same clone (i.e. rolling security releases).

	=== • Sanity check tarball and signature ===		=== • Sanity check tarball and signature ===
Line 58:		Line 58:

	devel/tools/rt-static-docs --source rt-X.Y.Z.tar.gz \		devel/tools/rt-static-docs --source rt-X.Y.Z.tar.gz \
	--to /path/to/bestpracticalsite/web/static/rt~~/docs~~/X.Y.Z		--to /path/to/bestpracticalsite/web/static/docs/rt/X.Y.Z

	Commit the changes to the bestpracticalsite repo.		Commit the changes to the bestpracticalsite repo.
Line 67:		Line 67:

	rsync -av --delete release-notes/[1-9].*.{release,changes} \		rsync -av --delete release-notes/[1-9].*.{release,changes} \
	bestpracticalsite/web/static~~/rt~~/release-notes/		bestpracticalsite/web/static/release-notes/rt/

	Commit the changes to the bestpracticalsite repo.		Commit the changes to the bestpracticalsite repo.

67.183.142.187: /* • Generate docs */ Update option name

2013-08-12T23:56:32Z

• Generate docs: Update option name

New page

=== • Create releng branch ===

git checkout -b 4.0.14-releng 4.0-trunk

=== • If necessary, git cherry-pick -x sha1 to pull changes from trunk to branch ===

=== • Make sure translations are uploaded to Rosetta with enough time to be translated ===

=== • Import translations ===

=== • Check if jsmin should be updated on download.bestpractical.com/mirror/ ===

=== • If 3.8, update configure.ac for the correct version ===

perl -pi -e s/3.8.HEAD/3.8.18/ configure.ac
git commit -m 'Bump version for 3.8.18' configure.ac

=== • Tag the release ===

git tag -sm 'release 4.0.14' rt-4.0.14

=== • Make the archive ===

rm -rf autom4te.cache
./configure.ac
make snapshot

This will build you a snapshot tarball, GPG sign it and give you SHA1 sums. On 3.8, you'll need to sign and generate SHA1 sums yourself:

gpg --detach-sign rt-3.8.18.tar.gz
sha1sum rt-3.8.18.tar.gz*

Do not skip reconfiguring, as it ensures you have a fresh build and Makefile. This is especially important if you're releasing 4.0 and 3.8 at the same time from the same clone (i.e. rolling security releases).

=== • Sanity check tarball and signature ===

This should include running tests from inside the tarball (with MySQL or Pg), verifying the embedded version (esp. on 3.8), checking that RT starts up on a fresh database, and checking the signature.

It's nice to let other folks kick the tires as well.

=== • Upload it ===

chmod a+rx rt-4.0.14*
scp -rvp rt-4.0.14.tar.gz* download.bestpractical.com:/opt/web/hosted/download.bestpractical.com/html/pub/rt/release/
scp -rvp rt-4.0.14-third-party-source.tar.gz* download.bestpractical.com:/opt/web/hosted/download.bestpractical.com/html/pub/rt/release/third-party-source/

When making a non-developer release, files live in pub/rt/release and you need to make sure to update the rt.tar.gz symlink:

ssh download.bestpractical.com ln -svf /opt/web/hosted/download.bestpractical.com/html/pub/rt/release/{rt-4.0.14,rt}.tar.gz

As soon as you upload a new version into pub/rt/release/, it will be displayed on the corporate site's front page and RT product page.

Developer releases such as RCs go in pub/rt/devel/.

=== • Generate docs ===

From inside a git clone on at least 4.0-trunk:

devel/tools/rt-static-docs --source rt-X.Y.Z.tar.gz \
--to /path/to/bestpracticalsite/web/static/rt/docs/X.Y.Z

Commit the changes to the bestpracticalsite repo.

Diff with previous version docs to check that nothing horrible changed.

=== • Update release notes in bestpractical.com repo ===

rsync -av --delete release-notes/[1-9].*.{release,changes} \
bestpracticalsite/web/static/rt/release-notes/

Commit the changes to the bestpracticalsite repo.

=== • Pull bestpractical.com live with updates ===

See checkmarkable.

=== • Cleanup and preserve history ===

For stable RT releases after 3.8:

git checkout 4.0-trunk
git merge --no-ff 4.0.14-releng

Replace 4.0-trunk with the appropriate trunk branch (e.g. master, 4.2-trunk, etc).

For RT 3.8:

git checkout 3.8-trunk
git merge --no-commit --no-ff 3.8.18-releng
git checkout HEAD -- configure.ac
git commit
Note in message that you undid the version bump from the branch

Alexmv: /* Upload it */

2011-06-13T23:03:59Z

Upload it

New page

=== Create releng branch ===

git checkout -b 3.8.5-releng 3.8-trunk

=== If necessary, git cherry-pick -x sha1 to pull changes from trunk to branch ===

=== Tag the release ===

git tag -s -m 'release 3.8.5' rt-3.8.5

=== Make the archive ===

make snapshot

This will build you a snapshot tarball, GPG sign it and give you SHA1 sums

If you need an updated lib/RT/Generated.pm locally, you need to remove autom4te.cache and rerun configure

=== Upload it ===

scp -rvp rt-3.8.5.tar.gz download.bestpractical.com:/opt/web/hosted/download.bestpractical.com/html/pub/rt/devel/
scp -rvp rt-3.8.5.tar.gz.sig download.bestpractical.com:/opt/web/hosted/download.bestpractical.com/html/pub/rt/devel/

When making a release, files live in rt/release and you need to make sure to update the rt.tar.gz symlink

As soon as you upload a new version into pub/rt/release/, it will be displayed on the corporate site's front page and RT product page.

=== Cleanup and preserve history ===

# For RT 3.8: # this guarantees that git can find tags made from releng branches

git checkout 3.8-trunk
git merge --no-commit --no-ff 3.8.5-releng
git checkout HEAD -- configure.ac
git commit
Note in message that you undid the version bump from the branch

# For stable RT releases after 3.8:

git checkout 4.0-trunk
git merge 4.0.1-releng