what next?

[Vlad Skvortsov]

Vlad Skvortsov wrote:

[skipped]

I've opened issues to record all this.
> * We often reference mailing list threads from within issues, and it 
> breaks one of our principles: "being able to survive without network 
> connectivity". How about creating a utility/application that would watch 
> issue updates, filter out references to mailing list threads (only on 
> specified sites, obviously), download them and store in a repository? 
>   

i#145

> * We need to create some kind of database schema, so that a user might 
> add its own headers to issues and DITrack is able to check the 
> consistency. For example, one might want to add a "priority" header, 
> which would be described somewhat like this in the configuration:
>   

i#143

> * Local indexing. The invocation of 'ls' with or without filters should 
> provide results instantly. We might need to employ local indices and/or 
> cache to make that happen. The first step in approaching the problem 
> should be, of course, profiling.
>   

i#146

> * It would be nice if DITrack could somehow figure out the database 
> root. One of the ideas of how to do that is: when 'dt' is invoked, 
>   

i#147

> * Implement double-linking between revisions and issues, e.g. if one 
> commits a change with the following log message:
>   

i#148


-- 
Vlad Skvortsov, vss at 73rus.com, http://vss.73rus.com