I really appreciate this move and I would vote for variant 3, too!
I think duplicate or placeholder issues would be strange, as I've never
seen them in Github projects before. ;)
Am 10.09.2012 15:56, schrieb Michael Pedersen:
> Okay, a couple weeks back, right after we released TG 2.2.0, we--
> discovered a few things about the sourceforge system that makes it no
> longer desirable for using as our tracker. We had been thinking of
> using Github back when we switched last year, but (at the time) we
> chose SF.
> Now, we're going to make the switch to Github. I'm in the process of
> 1. Copy every ticket into every repository's issue tracker. Good:
> 2. Copy only relevant tickets, but use placeholders for non-relevant
> 3. Copy only relevant tickets. Good: Each repository's issues are kept
> I'm leaning towards number three, personally. However, I know that
> What do you think? Which one would you prefer?
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.