Noob Question: Build number
Jens Alfke
jens at mooseyard.com
Tue Nov 27 01:25:18 UTC 2007
On 26 Nov '07, at 4:40 PM, blr at robertsr.us wrote:
> Are you saying the "Single Central Repository" model
> (CVSLikePractice) won't work?
I don't believe Hg scales as well as SVN for large numbers of people
contending for the same repository, but I think it should work fine
for a team your size. (I haven't tried, though.) Matt posted some info
a few days ago on estimating the amount of contention.
> Developers
> check in fixes for a day or 2 before a new build goes out to the test
> servers. The testers need to know which fixes are in the build. If
> the
> build number is 175, then all the defects that are fixed in builds
> <= 175
> should be fixed.
Yup, this sounds like the way we do things where I work. We use SVN,
but the SVN revision numbers are only used internally; when submitting
a build for testing/integration, we number it consecutively from the
last build.
So when I check in a bug fix, I add "Committed as svn rev 189" to the
bug report, and the status of the bug goes to "integrate".
When we generate an official build, it gets a number like "12", the
SVN repository is tagged with "build-12", and all the bugs in the
"integrate" state get the message "Fixed in OurProduct build 12" and
have their state set to "verify".
So most people, like testers, just need to compare the build numbers.
It's only internally that I might need to compare my current SVN
revision number against the one that someone else's brand-new fix is
in, to see if I have the fix or not.
For your situation, just replace "SVN" with "Hg", and "revision
number" with "changeset hash".
--Jens
More information about the Mercurial
mailing list