[haiku-development] Re: Moving away from Subversion (pt 4)
- From: "Adrien Destugues" <adestugu@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Mon, 06 Dec 2010 19:01:41 +0100
> This does not have to be a problem for the binary searching use case
> though. The only thing is that in communicating the broken changeset,
> the changeset id is probably a better communication tool.
Nothing is impossible. If there's no strict ordering on the commits, we
can still try them one after the other to find the one that created the
problem.
The good thing about the sequential number is it allows the users to
help
in doing the binary search easily. Just download an images from a week
(or month) ago from haiku-files, and test it to see if the bug is
there. If it is, try an older one, if it isn't try newer.
This can usually reduce the bug creation range to about 10 revs, from
which a dev can often guess the one that actually broke something by
looking at the commit diffs.
With unreadable tags, this kind of workflow seems to be less smooth. So
yes, in a sense, it's kind of spelling the numbers on the phone.
There may be other ways to do this with a DCVS. But please, just don't
tell we don't need the numbers, learn us how we can do without them.
What would be the workflow for finding the commit that created a bug ?
Can we make the result as efficient as "happenned in between r34567 and
r34578" ? Can the bug reporter help with it, or does the dev need to do
all the work, for lack of a convenient way to track down changes ?
The other use of svn rev numbers is to uniquely identify the
Haikuversion you have on your hard disk. With it you can exactly say
which features are in and which are out, and decide if you should
update :)
A buid date tag would work as well, but would be a bit more coarse. And
the tag would map to features differently depending on if you got your
image from BOM or built it yourself. Getting a report starting with
'this is haiku r12345' lets you know exactly what the user uses. With a
DCVS I don't really see how that's posible. But I hope you can prove me
wrong :)
--
Adrien.
Other related posts:
