Commit Graph

4 Commits

Author SHA1 Message Date
Paul Bone
2877f1cd9d Revert my earlier change to VERSION
My earlier change was a mistake caused by a misudernstanding.

VERSION:
    As above.
2014-01-03 17:26:15 +11:00
Paul Bone
d4d59bf99e Fixup notes about updating the version number.
The version number is kept in VERSION, however since README is no-longer
dynamically generated we must also update the version number there.
This change adds a note to this effect in VERSION.

VERSION:
    As above.
2014-01-03 15:02:48 +11:00
Peter Ross
d96cb9e22b Document the change to the release naming scheme.
Estimated hours taken: 0.25
Branches: main

NEWS:
	Document the change to the release naming scheme.

VERSION:
	Document how major releases are to be named.
2010-02-05 03:57:12 +00:00
Fergus Henderson
9777cf86b5 Localize the definition of the version number into a single file.
Estimated hours taken: 2

Localize the definition of the version number into a single file.
Automate the building of releases, including daily "rotd"
(release-of-the-day) releases.

VERSION:
	New file, defines the version number.
	Also document the general scheme for assigning version numbers.

Mmake.common.in:
	Add `include VERSION'.

Mmakefile:
bindist/Mmakefile:
configure.in:
	Use the version number in VERSION rather than hard-coding it
	in multiple places.

Mmakefile:
README:
.README.in:
INSTALL:
.INSTALL.in:
	Change things so that README and INSTALL are automatically
	generated from .README.in and .INSTALL.in respectively, using
	the version number defined in VERSION.

BUGS:
	Remove an unnecessary reference to the version number.

RELEASE_NOTES:
	Change this file so that the version number is only mentioned
	in one place.  Bump the version number here to 0.7 in preparation
	for the next release.

library/Mmakefile:
library/library.m:
library/library.m.in:
	Change things so that library.m is automatically generated from
	library.m.in using the version number in VERSION.
	Also change it so that library__version says which architecture
	it was configured for.

tools/test_mercury:
	Override the version specified in the VERSION file in the CVS
	repository with either `rotd-YYYY-MM-DD' or (when making a release)
	with a specified $RELEASE_VERSION.
	When running on murliboobo, if the version built passes all its
	tests, copy it to the /pub/mercury/beta-releases directory on
	ftp://turiel.cs.mu.oz.au.

compiler/notes/release_checklist.m:
	Change the release checklist to say that you only need to
	update the version number in VERSION rather than in 6 different
	places.  Also change the procedure for building the final
	tar file to reflect the above changes to the `test_mercury' script.
1997-07-28 08:51:53 +00:00