On 24 October 2013 10:09, Paul A. Bristow
Currently open bug reports can be viewed [@https://svn.boost.org/trac/boost/query?status=assigned&status=new&status=reopened&component=math&c ol=id&col=summary&col=status&col=type&col=milestone&col=component&order=priority here].
You can do something similar with all decent web based bug trackers.
They will work fine as long as we keep trac running. AFAIK there are no plans to turn it off (but maybe should prevent the creation of new tickets?).
So what would replace this very valuable function?
Possibly github's issue system, if we decide to use it. I was assuming in my last mail we were going to start using it, but I'm not sure if that has actually been decided. IIRC there was some resistance because it's a closed system. Maybe this is a subject for another thread.
But if we ever turn it off, I'm sure we'll set something up to maintain the links.
The implicit links in commit logs won't work on github (e.g. trac converts #6999 to a ticket link,
So these Trac #1234 links will still work as before?
To be clear, an example is the ticket link in a changeset like: https://svn.boost.org/trac/boost/changeset/86394 That will still be viewable on trac, so the link will work there. You can find the github entry in the history at: https://github.com/boostorg/config/commits/develop As you can see it isn't linked, but has at the end: [SVN r86394] Which can be easily translated to the trac link. We should set up something to make this as easy as possible, either in trac or outside of it.
r83728 to a link to a changeset, I don't think github offers a way to do that), but since every revision should include a subversion commit number it will be pretty easy to find the changeset on trac where everything will be linked. We could possibly set up our own git viewer to manage that.
I'm reassured by this, but feel that some Trac-like system is very valuable, both for users and developers, so it remains a long-term must-have.
Oh, we'll always use something Trac-like. Whether it's github, continuing with trac, or something else entirely.
Bugs and enhancements are the *first* things that people will be tackling after conversion to GIT (not new libraries at first), so it would be really good if we still had a way of handling the recording of info about the work on them.
So (to start with) do we just carry on using Trac as before?
Sure, I was prematurely writing about stopping using Trac in my last mail. I should have been more careful, as I don't know if that's actually the case. Sorry about that.