<div dir="ltr">FYI, that link did not bring me to your issues page, but this one does:<div><br></div><div><a href="https://github.com/OpenSIPS/opensips/issues?state=open">https://github.com/OpenSIPS/opensips/issues?state=open</a><br>
</div><div><br></div><div style>I'm not sure if you were trying to direct to something else though, just thought I would let you know what happened when I clicked it.</div></div><div class="gmail_extra"><br clear="all">
<div><br>-dg</div>
<br><br><div class="gmail_quote">On Fri, Jun 7, 2013 at 5:31 AM, Răzvan Crainea <span dir="ltr"><<a href="mailto:razvan@opensips.org" target="_blank">razvan@opensips.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello, all!<br>
<br>
It's settled then, we'll proceed with the second option.<br>
Starting from now, any new ticket should be opened on the new GitHub tracker:<br>
<br>
<a href="https://github.com/organizations/OpenSIPS/dashboard/issues" target="_blank">https://github.com/<u></u>organizations/OpenSIPS/<u></u>dashboard/issues</a><br>
<br>
However, until all the resources are updated, the SourceForge tracker will still be available for the community. It will be closed only when the entire process is completed.<br>
I will get back with updates during the next week.<br>
<br>
Cheers,<br>
<br>
Razvan Crainea<br>
OpenSIPS Core Developer<br>
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.<u></u>com</a><br>
<br>
On 06/04/2013 05:05 PM, Ali Pey wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I would vote for the second option. It would take a bit to clean up but<br>
it would be cleaner and much less work. Usually when you move things,<br>
there are errors, mistakes, etc. It would be cleaner and less work with<br>
option 2.<br>
<br>
Regards,<br>
Ali<br>
<br>
<br>
<br>
On Tue, Jun 4, 2013 at 9:18 AM, Răzvan Crainea <<a href="mailto:razvan@opensips.org" target="_blank">razvan@opensips.org</a><br>
<mailto:<a href="mailto:razvan@opensips.org" target="_blank">razvan@opensips.org</a>>> wrote:<br>
<br>
Hello all!<br>
<br>
After migrating all the OpenSIPS repositories from SourceForge to<br>
GitHub[1], the next step is to proceed with the tracker migration.<br>
We wrote down two options here:<br>
<br>
1. Move all tickets (patches, feature requests, bugs) to the GitHub<br>
tracker. There are several problems with this approach: first is<br>
that we won't be able to preserve the submitter information,<br>
therefore it will no longer be updated about further updates<br>
(comments, fixes, etc). Moreover this has to be done manually, so it<br>
requires a lot of time and effort.<br>
<br>
2. Keep all the tickets already opened on SourceForge, but open new<br>
tickets on GitHub. In this case you will no longer be able to open<br>
tickets (this will be blocked from SourceForge), but only to update<br>
the new ones (comment, close, etc). All new tickets will have to be<br>
opened on the GitHub tracker.<br>
<br>
We prefer the second option because it overcomes all the issues of<br>
the first one. The downside is that for a certain period of time we<br>
will have to follow two different tracks (both SourceForge and<br>
GitHub). However, we believe that this is an acceptable compromise.<br>
<br>
Let us know what you think about this plan. Our intention is to do<br>
the migration process as smoothly as possible. So if you have a<br>
different idea, don't hesitate to share it with us!<br>
<br>
[1] <a href="http://www.opensips.org/About/__GitHub-Migration" target="_blank">http://www.opensips.org/About/<u></u>__GitHub-Migration</a><br>
<<a href="http://www.opensips.org/About/GitHub-Migration" target="_blank">http://www.opensips.org/<u></u>About/GitHub-Migration</a>><br>
<br>
Best regards,<br>
--<br>
Razvan Crainea<br>
OpenSIPS Core Developer<br>
<a href="http://www.opensips-solutions." target="_blank">http://www.opensips-solutions.</a><u></u>__com <<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-<u></u>solutions.com</a>><br>
<br>
______________________________<u></u>___________________<br>
Devel mailing list<br>
<a href="mailto:Devel@lists.opensips.org" target="_blank">Devel@lists.opensips.org</a> <mailto:<a href="mailto:Devel@lists.opensips.org" target="_blank">Devel@lists.opensips.<u></u>org</a>><br>
<a href="http://lists.opensips.org/cgi-__bin/mailman/listinfo/devel" target="_blank">http://lists.opensips.org/cgi-<u></u>__bin/mailman/listinfo/devel</a><br>
<<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/devel" target="_blank">http://lists.opensips.org/<u></u>cgi-bin/mailman/listinfo/devel</a><u></u>><br>
<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-<u></u>bin/mailman/listinfo/users</a><br>
<br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-<u></u>bin/mailman/listinfo/users</a><br>
</blockquote></div><br></div>