Hi Frankie This is awesome, and thank you for posting it. JIRAs actually do post to a mailing list - but it is [email protected] as opposed to dev@. You should be able to to subscribe by sending an email to [email protected].
Commenting on JIRA themselves and tracking tasks there is good, but I would encourage posting on dev@ as well, so your audience is a wide as possible. The link you posted is on the old version of the site - do you know if we have a copy on the new site? If not, it would be great to shift this over, include your list, and update it (I notice this page references svn, for example). Thanks Jon On Wed, Dec 5, 2018 at 6:46 AM Frankie <[email protected]> wrote: > Extended considering > > http://tomee-openejb.979440.n4.nabble.com/Stabilize-TomEE-Build-td4685909.html > > [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] Monitor build - on build errors caused by my changes: > - reopen JIRA ticket > - comment ticket > - fix build issues > - goto [3] > > [6] Clean up > - wait until PR is merged (ticket status change) > - remove branch in fork > > Frankie > > > > -- > Sent from: > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html >
