OpenSIPS Tracker Migration on GitHub

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

OpenSIPS Tracker Migration on GitHub

Răzvan Crainea-2
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

Best regards,
--
Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: [OpenSIPS-Devel] OpenSIPS Tracker Migration on GitHub

Saúl Ibarra Corretgé

On Jun 4, 2013, at 3:18 PM, Răzvan Crainea <[hidden email]> 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
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: [OpenSIPS-Devel] OpenSIPS Tracker Migration on GitHub

Ali Pey
In reply to this post by Răzvan Crainea-2
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 <[hidden email]> 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

Best regards,
--
Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com

_______________________________________________
Devel mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: [OpenSIPS-Devel] OpenSIPS Tracker Migration on GitHub

Răzvan Crainea-2
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

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

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 <[hidden email]
> <mailto:[hidden email]>> 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>
>
>     Best regards,
>     --
>     Razvan Crainea
>     OpenSIPS Core Developer
>     http://www.opensips-solutions.__com <http://www.opensips-solutions.com>
>
>     _________________________________________________
>     Devel mailing list
>     [hidden email] <mailto:[hidden email]>
>     http://lists.opensips.org/cgi-__bin/mailman/listinfo/devel
>     <http://lists.opensips.org/cgi-bin/mailman/listinfo/devel>
>
>
>
>
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: [OpenSIPS-Devel] OpenSIPS Tracker Migration on GitHub

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


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 <[hidden email]> 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

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

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 <[hidden email]
<mailto:[hidden email]>> 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>

    Best regards,
    --
    Razvan Crainea
    OpenSIPS Core Developer
    http://www.opensips-solutions.__com <http://www.opensips-solutions.com>

    _________________________________________________
    Devel mailing list
    [hidden email] <mailto:[hidden email]>
    http://lists.opensips.org/cgi-__bin/mailman/listinfo/devel
    <http://lists.opensips.org/cgi-bin/mailman/listinfo/devel>




_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: [OpenSIPS-Devel] OpenSIPS Tracker Migration on GitHub

Răzvan Crainea-2
In reply to this post by Răzvan Crainea-2
Hi again!

I am very pleased to announce you that the tracker migration is done.
 From now on, you will only be able to open new tickets/issues through
the GitHub Portal[1].
SourceForge tracker will only be used to follow old tickets. You will no
longer be able to open new ones. More details can be found here[2].
I hope you'll enjoy the new interface!

[1] https://github.com/OpenSIPS/opensips/issues
[2] http://www.opensips.org/Development/Tracker

Cheers,
Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com

On 06/07/2013 02:31 PM, Răzvan Crainea 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
>
> 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
>
> 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 <[hidden email]
>> <mailto:[hidden email]>> 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>
>>
>>     Best regards,
>>     --
>>     Razvan Crainea
>>     OpenSIPS Core Developer
>>     http://www.opensips-solutions.__com
>> <http://www.opensips-solutions.com>
>>
>>     _________________________________________________
>>     Devel mailing list
>>     [hidden email] <mailto:[hidden email]>
>>     http://lists.opensips.org/cgi-__bin/mailman/listinfo/devel
>>     <http://lists.opensips.org/cgi-bin/mailman/listinfo/devel>
>>
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> [hidden email]
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: [OpenSIPS-Devel] OpenSIPS Tracker Migration on GitHub

Bogdan-Andrei Iancu-2
Hi Razvan,

I'm really glad this migration to GitHub is completed ! thank a lot for
all your effort in doing that !

Now let's enjoy GitHub ;)

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com


On 06/11/2013 04:15 PM, Răzvan Crainea wrote:

> Hi again!
>
> I am very pleased to announce you that the tracker migration is done.
> From now on, you will only be able to open new tickets/issues through
> the GitHub Portal[1].
> SourceForge tracker will only be used to follow old tickets. You will
> no longer be able to open new ones. More details can be found here[2].
> I hope you'll enjoy the new interface!
>
> [1] https://github.com/OpenSIPS/opensips/issues
> [2] http://www.opensips.org/Development/Tracker
>
> Cheers,
> Razvan Crainea
> OpenSIPS Core Developer
> http://www.opensips-solutions.com
>
> On 06/07/2013 02:31 PM, Răzvan Crainea 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
>>
>> 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
>>
>> 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 <[hidden email]
>>> <mailto:[hidden email]>> 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>
>>>
>>>     Best regards,
>>>     --
>>>     Razvan Crainea
>>>     OpenSIPS Core Developer
>>>     http://www.opensips-solutions.__com
>>> <http://www.opensips-solutions.com>
>>>
>>>     _________________________________________________
>>>     Devel mailing list
>>>     [hidden email] <mailto:[hidden email]>
>>>     http://lists.opensips.org/cgi-__bin/mailman/listinfo/devel
>>>     <http://lists.opensips.org/cgi-bin/mailman/listinfo/devel>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> [hidden email]
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>
>> _______________________________________________
>> Users mailing list
>> [hidden email]
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users