I have not done a ton of research on GH issues, but from what I have seen, their biggest shortcoming is project management. It doesn’t appear there are nearly as many options for boards, workflows, ticket config, and reporting as JIRA. That being said, I don’t know that we have a strong need of any of these features in Codice. Given that, I’m in agreement to give GH issues a try. Aligning the switchover with the next DDF release seems reasonable to me.
--
You received this message because you are subscribed to the Google Groups "ddf-developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
ddf-developer...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Github added project boards to help organize and prioritize work.
https://help.github.com/articles/about-project-boards/
--Keith
From: ddf-dev...@googlegroups.com <ddf-dev...@googlegroups.com>
On Behalf Of R.A. Porter
Sent: Friday, January 18, 2019 8:36 AM
To: ddf-developers <ddf-dev...@googlegroups.com>
Subject: Re: Migrating from Jira to GH Issues
That's a very reasonable point and not one for which I have a definitive answer. All the pros of coupling issues and project tracking to source control definitely become cons if you decide to migrate source.
--
So, assuming that people have installed the githooks as they should), they would be forced to put a dummy PR number first or XXXX and then later not forget to update that commit with the actual PR number.
This seems to me like something that will be often forgotten.
I would prefer always have an issue first created even if that is a simple one.
Patrick
From: <ddf-dev...@googlegroups.com> on behalf of "R.A. Porter" <richard...@connexta.com>
Date: Wednesday, January 23, 2019 at 10:22 AM
To: ddf-developers <ddf-dev...@googlegroups.com>
Subject: Re: Migrating from Jira to GH Issues
Good point, Patrick. I think a solution to that (that is only mildly annoying) is to use the PR number as the commit prefix. It's mildly annoying because it would require the submitter to rename their commit after creating the PR in order to update it with the generated id.