I think what you are hitting is the lack of a light-weight project management tool and hitting the limitation of GitHub projects.
I don’t see the problem of creating issues on the actual responsible project for substantive milestones i.e. Create release plan, Make RC available etc. however as we now have an issue with checkboxes
it would probably cause confusion if we turned each bullet into its own issue in the project repo.
Therefore, short of using a different tool, a new repo maybe the way to go just to hang issues off which we have total control over.
Steve
From: jakartaee-platform-dev-bounces@xxxxxxxxxxx <jakartaee-platform-dev-bounces@xxxxxxxxxxx>
On Behalf Of Kevin Sutter
Sent: 28 January 2020 22:38
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: [jakartaee-platform-dev] Tracking progress of Jakarta EE 9
This is more of a release management question (vs a technical question), so if you are not interested in planning, you can skip this message...
The github project boardwe
have in place is working nice, but I'm hitting a couple of gotchas...
-
The notecards I am using in the
RC column are not very usable or flexible.
I can't add tags, labels, relationships, assignments, etc.
-
For example, if Ifilter on "wave:1",
I can see all of the Issues assigned to Wave:1, except I can't see whether we have any RCs available for Wave:1 yet. Unless I open each individual Issue and review it's checklist.
-
I was thinking of converting these Notecards in the RC column to Issues. I could add the necessary tags/labels to these Issues and the project board would be more useful. But, these Issues would
only be used for tracking purposes, so it seems silly to clutter up "real code" repositories.
-
So, I was thinking of creating a new repo called jakartaee-release, or jakartaee-mgmt, or jakartaee-project (I'm not picky). I used the jakartaee- prefix since the Platform project was responsible
for developing the Release Plan and we already own the jakartaee-platform, jakartaee-api, and jakartaee-schemas repos. I just didn't want to clutter up the jakartaee-platform repo with these release mgmt Issues. I also want to use a repo that we have write
access to so that it's easier to maintain.
-
-
You'll notice that the PR column for the Specifications and Apidocs can already utilize these tags/labels since we have write access to that repo. So,
a query for "wave:0"shows
all of the Issues and the PRs associated with "wave:0".
-
Maybe I'm over-complicating things here... I'm open to other suggestions. Thanks!
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter