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, - creating a ticket increases the last number after the last dot or the only number if it is the primary project repository. Having this you would end up with a tree of ticket numbers like: '1', '2',... '1.1', '1.2', ... '2.1', '2.2', ... and it would reflect the tree structure of all repositories of a project. Cheers, Jacek
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
