For me this probably comes down to whether and how we can migrate the existing content from JIRA to GitHub without any loss of fidelity...there's a LOT of important history in there re: decisions reached, etc. that would be difficult to live without (and it's obviously important to maintain some sort of consistency for items that are ongoing/active/open at the time of the migration).
Can anyone speak to the migration story for the existing data in re: what aspects of the JIRA content can make the jump to GitHub and what will be lost? -Steve B. -----Original Message----- From: "Ricardo Peres" <[email protected]> Sent: 12/19/2015 11:13 AM To: "nhibernate-development" <[email protected]> Subject: [nhibernate-development] Re: Migrate from JIRA to GitHub issues? +1 On Tuesday, December 15, 2015 at 11:02:29 PM UTC, Alexander Zaytsev wrote: Hi I have an idea to abandon JIRA in favor of github issues. Since development is fully on github and github has almost all features we are using in JIRA, so, in my opinion, keeping up JIRA running is kind of overhead. Also switching to github issues will make entry barrier lower, as users will not be required to register in an additional system. Any comments or objections? Best Regards, Alexander -- --- You received this message because you are subscribed to the Google Groups "nhibernate-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- --- You received this message because you are subscribed to the Google Groups "nhibernate-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
