Fuego release process

Here are the steps in the Fuego release process.

This assumes that changes to be released are in the 'next' branches of the repositories on bitbucket.org.

Overview [edit section]

where is the version found [edit section]

Detailed steps [edit section]

select a volcano or fire-related name [edit section]

If this is a major release, it should get a name for the release.

See Volcano Names or Fire Names for a tentative list and resources for finding a name.

update the change log [edit section]

change the version number [edit section]

update the CREDITS file [edit section]

test changes since last release [edit section]

manual steps (legacy) [edit section]

This is now scripts, but here are the previous manual steps.

pull patches from next to master [edit section]

tag the release [edit section]

Where M= Major, m = minor, r = revision,

push fuego-core master to bitbucket [edit section]

update the release table [edit section]

announce on the fuego mailing list [edit section]

Notes on specific releases [edit section]

See Releases for references to pages with notes and testing information about specific Fuego releases.

1.0 release [edit section]

git log fuego [edit section]

e41dea4 README: fix columns in README
7fbef4b tests.info: reboot has only a time plot at the moment
6e88fdd proxy: add support for environments behind a proxy
f9f8139 Dockerfile: whitespace cleanups
04fb120 Add script for creating a container that can talk through USB
2209f9b Add .gitignore files to ignore generated files
39c0601 nologger: change to nologread

git log fuego-core [edit section]

df134e0 reboot: fix the reboot test
00b129b logger: remove dependency on logging mechanism
46e054e nosyslogd.dist: support targets without syslogd
f679cca dist: rename nologger.dist to nologread.dist
39c8ecc gitignore: add a gitignore file
0fd8885 FUEGO_'HOME: create automatically if not provided
876e6f9 bzip2: add support for busybox version of bzip2

changelog list [edit section]