Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [che-dev] How we track issues/PR that are part of a release 
On Tue, Jul 21, 2020 at 4:27 AM Gorkem Ercan <gorkem.ercan@xxxxxxxxx> wrote:
>
> You can automate reports if you have structured metadata , if your metadata is trapped inside an issue's markdown it is almost impossible to do anything meaningful with it.
> Option 1 is a  manual process that will be likely to be neglected and even if it is not neglected the data is not usable for anything else.
>
> I like option 2 because as long as data is there and structured I can create reports that span multiple repos.
> Here is a demo [1] of how I follow up with the Eclipse Che project today. Notice that I aggregate PRs from 3 repos on the Open Pull
> Requests section of my notebook (there are 53 by the way). You can also see that the report can
> be easily used for generating new&noteworthy by combining the milestones with n&n label.
> And it is possible to do more as long as data exists. I have for instance another notebook that helps me to follow devfile progress
> on odo, che and devfile repos in one place.
>
> I am using this gh notebook vscode extension [2] for this. Once the notebook APIs are available, we will be able to run it with Che as well.
> I can send a PR to share the notebook I am using with the repository as well.
>
> [1] https://youtu.be/COz_dS2CSUk
> [2] https://marketplace.visualstudio.com/items?itemName=ms-vscode.vscode-github-issue-notebooks

This may sound like a radical proposal, but have we considered using
something else for issue tracking? For example in bugzilla these sort
of reports/views are trivial to create, all you need to do is create a
saved search. Bugzilla also has vastly superior notification
preferences and historical report functionalities compared to GitHub
-- you can use it to extract all sorts of metrics and data. There is
also already a fully maintained bugzilla instance we could use at
Eclipse.org.

We can keep everything else on GitHub, just move issue tracking to
bugzilla -- food for thought.

Eric

Back to the top