On Mon, 2017-05-22 at 11:29 -0700, Gary Gregory wrote: > On Mon, May 22, 2017 at 11:16 AM, Michael Osipov <[email protected] > > > wrote: > > > Am 2017-05-22 um 06:46 schrieb Gary Gregory: > > > > > I will follow whatever the community decides; my only request is > > > that > > > precise git instructions be provided for contributors and RMs. > > > I'm sure > > > Oleg does not need them, but I'd like to get releases sooner > > > perhaps so I > > > might give RMing a go if there a bug fix I just must have ASAP. > > > > > > > On what do you exact Git steps? How to squash/rewrite? On a > > release? Maven > > Release Plugin does that for you > > > I would expect to see Git instructions so that contributors using > Apache > Git or GitHub can provide a branch or PR that meets the cleanliness > standard you all expect. >
Hi Gary You do not need to worry. It will be RM's (mostly mine for the time being) trouble. Only if you volunteer to be an RM you will have to deal with merging dev branches and keeping track of changes in the release branch. If one prefers to keep track of changes in JIRA instead of git log I guess it should also be fine. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
