Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-tck-dev] Slack room for informal discussion of Platform TCK tasks/planning...
As a follow up on the label for task planning/status presented by Scott at the beginning of this email thread, there is one more possible label that can help to identify the execution issues pointed by Kevin.
I come up with "build-exec-bug" name, which may not be the best to describe the category, as a starting point to have this added to the proposed set of labels.

9.0.0 - for issues that target the 9.0.0 platform TCK release.
blocking - for issues that are blocking the current platform TCK release
nice to have - for nice to have changes that don't block the current platform TCK release.
build-exec-bug - issues for building and executing tasks associated with the TCK.

Also, since we are already using GitHub issues and Project board for status transitions.
We are just one click away from GitHub milestones https://help.github.com/en/github/managing-your-work-on-github/about-milestones as a way to provide an automated status of the many project milestones.

What do you think?
--
Regards
Cesar Hernandez


On Mon, May 11, 2020 at 12:11 PM Cesar Hernandez <chernandez@xxxxxxxxxxxxx> wrote:
Hi Oliver.

Slack and the rest of the communication channels are here:

On Fri, May 8, 2020 at 5:41 PM Olivier Lamy <olamy@xxxxxxxxxxx> wrote:
Hi 
How do we get access to the slack channel?

On Fri, May 8, 2020 at 3:42 AM Scott Marlow <smarlow@xxxxxxxxxx> wrote:
Hi,

I created a #jakartaee-tck [1] room for discussing the EE 9 Platform TCK tasks/planning, that is open for all in the community that would like to join.

IMO, we should still default to discussing things on this mailing list, as well as via tracking issues.  The slack room is for trying to have a place for informal discussions that last a little while (e.g. as long as our slack instance allows for).

One question that I am looking to answer, that I thought having the public slack room, might help with, is how to best collect our TCK status, for reporting into the Eclipse Jakarta steering committee.  

Speaking of status, as I understand it, we are still working on our first milestone (covering the javax => jakarta package rename + removing pruned tests).  I think that our first milestone is reached when the TCK compiles without error.  

Please do continue to assign tracking issues (https://github.com/eclipse-ee4j/jakartaee-tck/issues) to yourself, when working on them.  If there isn't one, please do create a new one, so we can understand what is left to do.

Speaking of tracking issues, any suggestions for categorizing issues for the Platform TCK 9.0.0 release?  How about labels for categorizing issues that block the 9.0.0 release?  How about the following:

9.0.0 - for issues that target the 9.0.0 platform TCK release.

blocking - for issues that are blocking the current platform TCK release

nice to have - for nice to have changes that don't block the current platform TCK release.

Scott

_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev


--
Olivier
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev

Back to the top