If we are commiting to github, then we should use the github tracker because it offers a tight integration. If possible, we should move existing issues from flyspray to github or just leave them there until closed, but new issues should be tracked in the github tracker.
Regards, Ovidiu Sas On Tue, Dec 9, 2014 at 4:57 PM, Daniel-Constantin Mierla <[email protected]> wrote: > I am for using github -- besides it will integrate better with git > repository, flyspray is slow developing (if still does it). > > We need to review and see what items there need to be migrated ... > > Can be done later, but if anyone wants to start, he/she is welcome. > > Cheers, > Daniel > > > On 09/12/14 21:01, Victor Seva wrote: > > On 12/08/2014 09:44 AM, Daniel-Constantin Mierla wrote: > > Considering all above, I propose to stop committing togit.sip-router.org and > pushing to github starting either next Monday > (Dec 15) (or Wednesday (Dec 17) if not ready by Monday). Existing > developers have to send me the github username to add it to kamailio > project. > > Are we going to use the github issues instead of our flyspray? > Do we need to migrate open issues to github then? > > Cheers, > Victor > > > > > _______________________________________________ > sr-dev mailing > [email protected]http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev > > > -- > Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - > http://www.linkedin.com/in/miconda > > > _______________________________________________ > sr-dev mailing list > [email protected] > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev > > -- VoIP Embedded, Inc. http://www.voipembedded.com
_______________________________________________ sr-dev mailing list [email protected] http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
