[OpenSIPS-Users] [OpenSIPS-Devel] OpenSIPS Tracker Migration on GitHub

[Daniel Goepp]

FYI, that link did not bring me to your issues page, but this one does:

https://github.com/OpenSIPS/opensips/issues?state=open

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.


-dg


On Fri, Jun 7, 2013 at 5:31 AM, Răzvan Crainea <razvan at opensips.org> wrote:

> Hello, all!
>
> It's settled then, we'll proceed with the second option.
> Starting from now, any new ticket should be opened on the new GitHub
> tracker:
>
>  https://github.com/**organizations/OpenSIPS/**dashboard/issues<https://github.com/organizations/OpenSIPS/dashboard/issues>
>
> 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.
> I will get back with updates during the next week.
>
> Cheers,
>
> Razvan Crainea
> OpenSIPS Core Developer
> http://www.opensips-solutions.**com <http://www.opensips-solutions.com>
>
> On 06/04/2013 05:05 PM, Ali Pey wrote:
>
>> I would vote for the second option. It would take a bit to clean up but
>> it would be cleaner and much less work. Usually when you move things,
>> there are errors, mistakes, etc. It would be cleaner and less work with
>> option 2.
>>
>> Regards,
>> Ali
>>
>>
>>
>> On Tue, Jun 4, 2013 at 9:18 AM, Răzvan Crainea <razvan at opensips.org
>> <mailto:razvan at opensips.org>> 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.
>>
>>     Let us know what you think about this plan. Our intention is to do
>>     the migration process as smoothly as possible. So if you have a
>>     different idea, don't hesitate to share it with us!
>>
>>     [1] http://www.opensips.org/About/**__GitHub-Migration<http://www.opensips.org/About/__GitHub-Migration>
>>     <http://www.opensips.org/**About/GitHub-Migration<http://www.opensips.org/About/GitHub-Migration>
>> >
>>
>>     Best regards,
>>     --
>>     Razvan Crainea
>>     OpenSIPS Core Developer
>>     http://www.opensips-solutions.**__com <http://www.opensips-**
>> solutions.com <http://www.opensips-solutions.com>>
>>
>>     ______________________________**___________________
>>     Devel mailing list
>>     Devel at lists.opensips.org <mailto:Devel at lists.opensips.**org<Devel at lists.opensips.org>
>> >
>>     http://lists.opensips.org/cgi-**__bin/mailman/listinfo/devel<http://lists.opensips.org/cgi-__bin/mailman/listinfo/devel>
>>     <http://lists.opensips.org/**cgi-bin/mailman/listinfo/devel<http://lists.opensips.org/cgi-bin/mailman/listinfo/devel>
>> **>
>>
>>
>>
>>
>> ______________________________**_________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-**bin/mailman/listinfo/users<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
>>
>>
> ______________________________**_________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-**bin/mailman/listinfo/users<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20130607/1d52c630/attachment-0001.htm>