I found hints at http://tomee.apache.org/dev/contribution-tips.html but the
important point "how to assign" a task to a person is not completely clear
there.
So the workflow for a task one is interested in could be like this?:
[1] Check JIRA
- create ticket, if not exists
- (request to) assign ticket
=> the assignment of the ticket could raise an automated post in the mailing
list
[2] Process Task
- fork repo
- create branch in fork
- discuss on mailing list / in JIRA ticket (prefered?)
- work on code
[3] Submit Change
- create PR
- ask for review on mailing list
[4] Merge Change (by a committer)
- review changes
- merge code
- change JIRA ticket status / close ticket => would help to inform
contributor that merge is done ...
[5] Clean up
- wait until PR is merged (ticket status change)
- remove branch in fork
I think it would be important not only to have this defined (and documented)
but that it matches the way we act in working on tasks so one can rely on
it.
Frankie
--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
