Proposal: GitHub Issue Tracker (versus current Jira)


#1

@nithinj suggested switching from Jira to Github in another topic (thread). I am moving the discussion here for better visibility. The previous comments from http://community.pbspro.org/t/proposal-for-simplification-of-the-code-contribution-process are:


Proposal for simplification of the code contribution process
#2

When are we opening a Github issue tracker for PBSPro? The sooner the better as we are not planning to migrate existing Jira issues. (I know everyone is busy with 18.1 release, so just treat it as a gentle reminder :slight_smile: )


#3

Hi,

Thanks @nithinj – reviewing this thread, I see only positive comments on moving from Jira to Github.

Last call for any more comments or dissent…

If there is still general consensus when PBS Pro v18.1 GA is released (see 18.1 Release Plan), then we will move to Github issue trackers at that time (or there about, depending on how long it takes).


#4

Hi @billnitzberg @subhasisb
Since 18.1 is already released and there isn’t any comment that vote against this, shall we proceed and enable Github issue on our open source repo?

Thanks,


#5

Hi @minghui & all – looks like consensus has been reached!

I feel it would be “bad” to have two systems in operation, so I would like to discuss the best way to transition. That should include updating our process documentation, pull request template, etc., but also if there is some way to label Jira (or make it read-only). (I do not believe we need to transfer open JIRA tickets, but am open to that idea as well.)

Let’s discuss offline, and we can post the plans here, then execute.