Right now, if you grab source from a nightly or from git directly, it
claims to be the last committed version. I'd like it to claim to be
the sha1 of the last commit. this doesn't work perfectly but gives a
better idea than now.

Problem: tagged versions should be able to be regenerated and have the
version embedded in a small set of files.
Proposal: each release will be done on a branch containing just the
version number changes
Implementation: the release script takes a tagpoint. Instead it will
either know which files to update and given a sha1 to tag, branch,
make its changes, commit and tag, or do something otherwise
equivalent.

-- 
Derrick
_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel

Reply via email to