[Building Sakai] Github and JIra

classic Classic list List threaded Threaded
4 messages Options
Adrian Fish-2 Adrian Fish-2
Reply | Threaded
Open this post in threaded view
|

[Building Sakai] Github and JIra

What's the current thinking on how we'll be doing issue tracking after moving to github (or Stash or whatever) ? Will we stay with Jira for issue tracking, whatever?

I'm asking because I've been tentatively playing with using Github for issues and it's already leading to a slightly confusing situation; some in Jira and some in Github. Jira's issue tracking is obviously way more advanced.

If we're definitely sticking with Jira, I'll shut down issue tracking in my github projects, if that's possible.

Cheers,
Adrian.

_______________________________________________
sakai-dev mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"
Steve Swinsburg-3 Steve Swinsburg-3
Reply | Threaded
Open this post in threaded view
|

Re: [Building Sakai] Github and JIra

What has been discussed before is keeping issue tracking in Jira - lots invested in there already and Github's is pretty basic. So long as we can still see the commits in Jira (via the git plugin) and merge PR's via the UI (important for taking contributions) then that combo would be fine.

cheers,
Steve


On Wed, Jul 16, 2014 at 7:16 PM, Adrian Fish <[hidden email]> wrote:
What's the current thinking on how we'll be doing issue tracking after moving to github (or Stash or whatever) ? Will we stay with Jira for issue tracking, whatever?

I'm asking because I've been tentatively playing with using Github for issues and it's already leading to a slightly confusing situation; some in Jira and some in Github. Jira's issue tracking is obviously way more advanced.

If we're definitely sticking with Jira, I'll shut down issue tracking in my github projects, if that's possible.

Cheers,
Adrian.

_______________________________________________
sakai-dev mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"


_______________________________________________
sakai-dev mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"
Aaron Zeckoski-3 Aaron Zeckoski-3
Reply | Threaded
Open this post in threaded view
|

Re: [Building Sakai] Github and JIra

In reply to this post by Adrian Fish-2
The plan is to use JIRA for issue tracking (for now anyway). It is
trivial to shutdown the issue tracking in a project. Just go to
project settings in github and disable the issues.
-AZ

On Wed, Jul 16, 2014 at 5:16 AM, Adrian Fish <[hidden email]> wrote:

> What's the current thinking on how we'll be doing issue tracking after
> moving to github (or Stash or whatever) ? Will we stay with Jira for issue
> tracking, whatever?
>
> I'm asking because I've been tentatively playing with using Github for
> issues and it's already leading to a slightly confusing situation; some in
> Jira and some in Github. Jira's issue tracking is obviously way more
> advanced.
>
> If we're definitely sticking with Jira, I'll shut down issue tracking in my
> github projects, if that's possible.
>
> Cheers,
> Adrian.
>
> _______________________________________________
> sakai-dev mailing list
> [hidden email]
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to [hidden email]
> with a subject of "unsubscribe"



--
Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
_______________________________________________
sakai-dev mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"
Adrian Fish-2 Adrian Fish-2
Reply | Threaded
Open this post in threaded view
|

Re: [Building Sakai] Github and JIra

Thanks for the responses. I'll do just that.

Cheers,
Adrian.


On 16 July 2014 11:18, Aaron Zeckoski <[hidden email]> wrote:
The plan is to use JIRA for issue tracking (for now anyway). It is
trivial to shutdown the issue tracking in a project. Just go to
project settings in github and disable the issues.
-AZ

On Wed, Jul 16, 2014 at 5:16 AM, Adrian Fish <[hidden email]> wrote:
> What's the current thinking on how we'll be doing issue tracking after
> moving to github (or Stash or whatever) ? Will we stay with Jira for issue
> tracking, whatever?
>
> I'm asking because I've been tentatively playing with using Github for
> issues and it's already leading to a slightly confusing situation; some in
> Jira and some in Github. Jira's issue tracking is obviously way more
> advanced.
>
> If we're definitely sticking with Jira, I'll shut down issue tracking in my
> github projects, if that's possible.
>
> Cheers,
> Adrian.
>
> _______________________________________________
> sakai-dev mailing list
> [hidden email]
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to [hidden email]
> with a subject of "unsubscribe"



--
Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile


_______________________________________________
sakai-dev mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"