On Mon, Jul 22, 2013 at 4:47 PM, Jacek Cała <jacek.c...@gmail.com> wrote: > Hi all, > > My 2 cents below regarding ticket numbering: > > 2013/7/22 Stephan Beal <sgb...@googlemail.com> >> >> >>> * built-in persistent integer ticket numbers in addition to the SHA1 >>> ticket/artifact ID. The SHA1 hexdigest fragments are too geeky for >>> management during the weekly status meeting. >> >> >> Stable incremental numbers are literally not possible to solve for >> DCVS systems, which is why the SHA's (geeky/unwieldy as they are) are >> used. > > I wrote some time ago about this as I think you can have a simple, > relatively easy to grasp ticket numbering in DCVS (not integer > though). It involves three simple steps: > > - project create initializes internal repo ticket number with '1', > - project clone adds suffix '.1' to the repo ticket number,
Like this? Origin: 1 Clone Origin to A: 1.1 Clone Origin to B: 1.2 Clone A to C: 1.1.1 Clone A to D: 1.1.2 Clone B to E: 1.2.1 Clone B to F: 1.2.2 A creates ticket: 1.1.1 B creates ticket: 1.2.1 Regards. -- Isaac Jurado "The noblest pleasure is the joy of understanding" Leonardo da Vinci _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
