Apache Veterans,

What is typical in a project trying to follow an RTC workflow?

Benson's submission of a PR seems like an ideal way to do RTC.  What
matt/mark/and I have largely done is put stuff in a branch which is often
overkill or generated a patch and appended that to a ticket.  The Github PR
approach though seems like it might actually make more sense.

Is there a 'common approach here'?

Also, I personally have found RTC to be overkill for a non-trivial range of
changes:
- documentation updates
- license/header adjustments
- fixing maven configuration / build items

I can see a bit of a slippery slope in the reasoning but is there merit to
defining things which are RTC vs those which are reasonable as CTR?

Thanks
Joe

Reply via email to