the RM
> > who
> > > >>> happens to be looking at history has to take on the task of
> > backporting
> > > >> the
> > > >>> change if it turns out to be a bug fix germane to release branches.
> > The
>
gt;> change if it turns out to be a bug fix germane to release branches.
> The
> > >>> worst thing you can do as a committer is take a bug fix change, only
> > >> commit
> > >>> it to trunk, resolve the JIRA, and walk away. The second worst thing
&g
There is currently one
> one
> >>> committer doing these things on a frequent basis. I ask that this
> >> practice
> >>> stop. Please view this behavior as poor maintenance practice that
> should
> >> be
> >>> avoided. Frankly, better you not commit the
the change at all. You are not
helping the project. It is a net negative.
On Mon, Jul 23, 2018 at 12:18 PM Andrew Purtell
wrote:
There is a recent trend in JIRA management where a change being tracked
by
one JIRA is committed only to master, or maybe master and branch-2, and
then the JIRA is
t; commit only to trunk and leave the JIRA open. There is currently one one
>>>> committer doing these things on a frequent basis. I ask that this
>>> practice
>>>> stop. Please view this behavior as poor maintenance practice that should
>>> be
>>
iew this behavior as poor maintenance practice that should
>> be
>>> avoided. Frankly, better you not commit the change at all. You are not
>>> helping the project. It is a net negative.
>>>
>>> On Mon, Jul 23, 2018 at 12:18 PM Andrew Purtell
ing these things on a frequent basis. I ask that this
> practice
> > stop. Please view this behavior as poor maintenance practice that should
> be
> > avoided. Frankly, better you not commit the change at all. You are not
> > helping the project. It is a net negative.
&
nge at all. You are not
> helping the project. It is a net negative.
>
> On Mon, Jul 23, 2018 at 12:18 PM Andrew Purtell wrote:
>
>> There is a recent trend in JIRA management where a change being tracked by
>> one JIRA is committed only to master, or maybe master and bran
be
avoided. Frankly, better you not commit the change at all. You are not
helping the project. It is a net negative.
On Mon, Jul 23, 2018 at 12:18 PM Andrew Purtell wrote:
> There is a recent trend in JIRA management where a change being tracked by
> one JIRA is committed only to master, or
There is a recent trend in JIRA management where a change being tracked by
one JIRA is committed only to master, or maybe master and branch-2, and
then the JIRA is left open. The fix versions may or may not be updated. The
biggest offender is Ted Yu but newer committers are also occasionally doing
10 matches
Mail list logo
