starting to use ditrack - dev roadmap

[Pavel Shramov]

On Fri, Feb 08, 2008 at 02:28:34PM -0500, Luke Kenneth Casson Leighton wrote:
> i have a couple of issues that need to be resolved - one of them
> is that any changes can result in conflict - there's no race-condition
> checking on creation of new issues, creation of new comments, etc.
... skip ...
> obviously, this can't be done in an offline situation: under
> such circumstances, #1 #2 #3 etc. etc. isn't good enough,
> you'd need to prefix by username or some other unique
> identifier, or have random numbering large enough to not
> have conflicts.
>
> _after_ a commit, _then_ a nice unique ordered numbering
> could be applied.

Current numbering scheme has disadvantages but it's simple and may be used 
'inline' in mail, chat, etc... I think You won't write to somebody 

"I've closed issue #c675522f-76ef-47a1-bb24-107ea83534eb" :)

> basically, ditrack as it stands is perfect for a single user,
> and.... i'm not planning on using it as a single user system.
> 
> anyway have you seen git? it looks _far_ more interesting
> than svn as a back-end:
> http://www.tuxmachines.org/node/23855
> http://www.advogato.org/person/apenwarr/diary/371.html

I tried to use ditrack with git but problems with numbering You'd 
mentioned above make this hybrid unusable.

P.S I'm not ditrack developer or expert or even advanced
user :)