From: Loren C. <lor...@gm...> - 2013-09-14 20:29:01
|
We should ask each owner to resubmit under github. Can we lockout sourceforge do that no one submits a new issue through them? Sent from my iPhone On Sep 14, 2013, at 4:14 PM, Dmitriy Shabanov <sha...@gm...> wrote: I think yeap ... review and migrate one by one ... or ask owner ... On Sat, Sep 14, 2013 at 11:36 PM, Joe Wicentowski <jo...@gm...> wrote: > Makes sense to me too, but do old filings need to be migrated to github? > > Sent from my iPhone > > On Saturday, September 14, 2013 at 1:42 PM, Dmitriy Shabanov wrote: > >> on github issues better integrated with git commits and by so with code >> >> +1 issues on github >> >> On Sat, Sep 14, 2013 at 3:38 PM, Dannes Wessels <di...@ex...> wrote: >> we did not formally decide this, nor is this updated in our documentation.... >> until then, it is sf.net IMO..... >> >> >> On 14 Sep 2013, at 13:25 , Adam Retter <del...@us...> wrote: >>> All new issues should be logged on GitHub not SF. https://github.com/eXist-db/exist >>> -- Dmitriy Shabanov ------------------------------------------------------------------------------ LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/22/13. http://pubads.g.doubleclick.net/gampad/clk?id=64545871&iu=/4140/ostg.clktrk _______________________________________________ Exist-development mailing list Exi...@li... https://lists.sourceforge.net/lists/listinfo/exist-development |