 |
 |
done
From: CCP-PETMR Developers list [mailto:[log in to unmask]]
On Behalf Of Thielemans, Kris
Sent: 21 July 2017 16:11
To: [log in to unmask]
Subject: Re: CCP: aggregating GitHub issues
Evgueni/Edo
I suggest that we add a link to all open issues on the Software Framework page. Something like
------
A development version of the software is available at
https://github.com/CCPPETMR/. A list of all
open CCPPETMR issues is [here](https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3ACCPPETMR).
The plan and timeline for the next release can be found
here. See also our
initial plan for the longer term.
--------
From: CCP-PETMR Developers list [mailto:[log in to unmask]]
On Behalf Of Thielemans, Kris
Sent: 21 July 2017 16:49
To: [log in to unmask]
Subject: Re: CCP: aggregating GitHub issues
Great.
I cannot find a way to list all CCPPETMR issues at milestone v1.0.0, but that’s not really necessary.
So, Evgueni, can you move a few of the new SIRF issues to CCPETMR_VM or the SuperBuild?
Thanks all
Kris
From: Casper da Costa-Luis [mailto:[log in to unmask]]
Sent: 21 July 2017 15:19
To: Thomas, Ben <[log in to unmask]>
Cc: Thielemans, Kris <[log in to unmask]>;
[log in to unmask]
Subject: Re: CCP: aggregating GitHub issues
Hi Ben,
I know other large multi-repository projects have opted to have an empty "issues-only" repository to tackle this.
You can aggregate reasonably easily as-is, though. Some examples:
open CCPPETMR issues:
https://github.com/issues?q=is%3Aopen+is%3Aissue+user%3ACCPPETMR
open CCPPETMR PRs:
https://github.com/issues?q=is%3Aopen+is%3Apr+user%3ACCPPETMR
open CCPPETMR anything:
https://github.com/issues?q=is%3Aopen+user%3ACCPPETMR
all CCPPETMR anything:
https://github.com/issues?q=user%3ACCPPETMR
Regards,
Casper
On 21 July 2017 at 12:49, Thomas, Ben <[log in to unmask]> wrote:
Hi Casper,
The topic of GitHub issues came up during the t-con this morning and Kris asked that I send you a message. Currently, CCPPETMR GitHub issues/milestones are spread across 3 repositories. Do you know if it is feasible to aggregate the issues somehow, rather than having to visit each independently? And if so, how?
Kind regards,
Ben