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

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 CHANGELOG [edit section]

update the CREDITS file [edit section]

change the VERSION number [edit section]

update reference materials for testing [edit section]

push changes to bitbucket [edit section]

test changes since last release [edit section]

pull patches from next to master [edit section]

tag the release [edit section]

NOTE: IMPORTANT tag the release NAME first, then the number, so that 'git describe' will show releases with the number, not the name.

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

push fuego and 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.

old information [edit section]

manual steps (legacy) [edit section]

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