On Jun 4, 2013, at 3:18 PM, Răzvan Crainea <[email protected]> wrote:
> Hello all! > > After migrating all the OpenSIPS repositories from SourceForge to GitHub[1], > the next step is to proceed with the tracker migration. We wrote down two > options here: > > 1. Move all tickets (patches, feature requests, bugs) to the GitHub tracker. > There are several problems with this approach: first is that we won't be able > to preserve the submitter information, therefore it will no longer be updated > about further updates (comments, fixes, etc). Moreover this has to be done > manually, so it requires a lot of time and effort. > > 2. Keep all the tickets already opened on SourceForge, but open new tickets > on GitHub. In this case you will no longer be able to open tickets (this will > be blocked from SourceForge), but only to update the new ones (comment, > close, etc). All new tickets will have to be opened on the GitHub tracker. > > We prefer the second option because it overcomes all the issues of the first > one. The downside is that for a certain period of time we will have to follow > two different tracks (both SourceForge and GitHub). However, we believe that > this is an acceptable compromise. > I think it's a good thing to do, this will probably also help in removing old tickets that have been lingering around for too long ;-) Regards, -- Saúl Ibarra Corretgé AG Projects _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
