Re: Rebase and incrementing version numbers
- From
PJ Weisberg <pj@irregularexpressions.net>
- Date
- Jan 19, 2012, 19:58 UTC
- Message-ID
- <CAJsNXTkDdHTMqmXCynT2nEYyuTmSF53RVtG2V+v7b+qcsYYufg@mail.gmail.com>
- In-Reply-To
- <CADo4Y9is9mBOJaU+YRTMedTz7FfDrMFoDiqiUvQpVxQpyariPQ@mail.gmail.com>
On Thu, Jan 19, 2012 at 10:48 AM, Michael Nahas <mike.nahas@gmail.com> wrote:
Show 11 quoted lines
> On Thu, Jan 19, 2012 at 1:12 PM, demerphq <demerphq@gmail.com> wrote: >> Stop using version numbers and start using the git sha1 of the code >> you are using. >> >> Yves > > 1. Others in the group use SVN. > 2. The version number needs to be increasing, to work with the current > process. SHA1's are random. > 3. The "git sha1" for the commit/snapshot cannot be put into the > config file, which is part of the snapshot.
Suggestion #1: Just put $Rev$ into the file and be done with it until the team moves over to Git (at which point you can figure something else out).
Suggestion #2: In your release process, put something like `sed -e "s/@@id@@/$(date +%s)/" source-dir/config > release-dir/config`
-PJ