Re: [VOTE] Git Guidelines (2)

On 05/31/2017 12:34 AM, Gary Gregory wrote: On Tue, May 30, 2017 at 11:55 AM, Oleg Kalnichevski wrote: On Tue, 2017-05-30 at 11:34 -0700, Gary Gregory wrote: On Tue, May 30, 2017 at 9:13 AM, Michael Osipov wrote: Am 2017-05-29 um 22:54 schrieb Gary

Re: [VOTE] Git Guidelines (2)

On Tue, May 30, 2017 at 8:55 PM, Oleg Kalnichevski wrote: > On Tue, 2017-05-30 at 11:34 -0700, Gary Gregory wrote: > > On Tue, May 30, 2017 at 9:13 AM, Michael Osipov > > wrote: > > > > > Am 2017-05-29 um 22:54 schrieb Gary Gregory: > > > > > > > On Mon,

Re: [VOTE] Git Guidelines (2)

On Tue, May 30, 2017 at 11:55 AM, Oleg Kalnichevski wrote: > On Tue, 2017-05-30 at 11:34 -0700, Gary Gregory wrote: > > On Tue, May 30, 2017 at 9:13 AM, Michael Osipov > > wrote: > > > > > Am 2017-05-29 um 22:54 schrieb Gary Gregory: > > > > > > > On Mon,

Re: [VOTE] Git Guidelines (2)

On Tue, 2017-05-30 at 11:34 -0700, Gary Gregory wrote: > On Tue, May 30, 2017 at 9:13 AM, Michael Osipov > wrote: > > > Am 2017-05-29 um 22:54 schrieb Gary Gregory: > > > > > On Mon, May 29, 2017 at 12:54 PM, Philippe Mouawad < > > > philippe.moua...@gmail.com> wrote: > > >

Re: [VOTE] Git Guidelines (2)

On Tue, May 30, 2017 at 9:13 AM, Michael Osipov wrote: > Am 2017-05-29 um 22:54 schrieb Gary Gregory: > >> On Mon, May 29, 2017 at 12:54 PM, Philippe Mouawad < >> philippe.moua...@gmail.com> wrote: >> >> Hello, >>> I'm not committer still, my 2 cents: >>> >>> [x] +1

Re: [VOTE] Git Guidelines (2)

Am 2017-05-29 um 22:54 schrieb Gary Gregory: On Mon, May 29, 2017 at 12:54 PM, Philippe Mouawad < philippe.moua...@gmail.com> wrote: Hello, I'm not committer still, my 2 cents: [x] +1 Committers must abide to these Git guidelines while working on the code Except for this one: => 1. Request

Re: [VOTE] Git Guidelines (2)

Am 2017-05-29 um 21:54 schrieb Philippe Mouawad: Hello, I'm not committer still, my 2 cents: [x] +1 Committers must abide to these Git guidelines while working on the code Except for this one: => 1. Request the release manager to merge your banch back to the release branch and make sure that

Re: [VOTE] Git Guidelines (2)

On Mon, May 29, 2017 at 12:54 PM, Philippe Mouawad < philippe.moua...@gmail.com> wrote: > Hello, > I'm not committer still, my 2 cents: > > [x] +1 Committers must abide to these Git guidelines while working on the > code > > Except for this one: > => 1. Request the release manager to merge your

Re: [VOTE] Git Guidelines (2)

Hello, I'm not committer still, my 2 cents: [x] +1 Committers must abide to these Git guidelines while working on the code Except for this one: => 1. Request the release manager to merge your banch back to the release branch and make sure that this merge won't incur a merge commit IMO, this

Re: [VOTE] Git Guidelines (2)

Am 2017-05-24 um 19:11 schrieb Michael Osipov: Hi folks, I am re-casting this vote for the previously discussed Git guidelines for all committers to make life easier for everyone. If the vote passes, every committer must abide to this. The guidelines: = Typical Issue Workflow = 1. Branch off

Re: [VOTE] Git Guidelines (2)

[x] +1 Committers must abide to these Git guidelines while working on the code On May 24, 2017 7:11:27 PM GMT+02:00, Michael Osipov wrote: >Hi folks, > >I am re-casting this vote for the previously discussed Git guidelines >for all committers to make life easier for

Re: [VOTE] Git Guidelines (2)

Am 2017-05-24 um 19:11 schrieb Michael Osipov: Hi folks, I am re-casting this vote for the previously discussed Git guidelines for all committers to make life easier for everyone. If the vote passes, every committer must abide to this. The guidelines: = Typical Issue Workflow = 1. Branch off

[VOTE] Git Guidelines (2)

Hi folks, I am re-casting this vote for the previously discussed Git guidelines for all committers to make life easier for everyone. If the vote passes, every committer must abide to this. The guidelines: = Typical Issue Workflow = 1. Branch off a release branch (e.g., 4.4.x, 5.0.x)

Re: [VOTE] Git Guidelines

Am 2017-05-21 um 11:00 schrieb Michael Osipov: Hi folks, I am casting this vote for the previously discussed Git guidelines for all committers to make life easier for everyone. If the vote passes, every committer must abide to this. The guidelines: = Typical Issue Workflow = 1. Branch off a

Re: [VOTE] Git Guidelines

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

Re: [VOTE] Git Guidelines

On Mon, 2017-05-22 at 11:29 -0700, Gary Gregory wrote: > On Mon, May 22, 2017 at 11:16 AM, Michael Osipov > > 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

Re: [VOTE] Git Guidelines

Am 2017-05-22 um 20:29 schrieb Gary Gregory: On Mon, May 22, 2017 at 11:16 AM, Michael Osipov 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

Re: [VOTE] Git Guidelines

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

Re: [VOTE] Git Guidelines

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. Gary On May 21,

[VOTE] Git Guidelines

Hi folks, I am casting this vote for the previously discussed Git guidelines for all committers to make life easier for everyone. If the vote passes, every committer must abide to this. The guidelines: = Typical Issue Workflow = 1. Branch off a release branch (e.g., 4.4.x, 5.0.x) ({{{git