JIRA's with no commits

[Ted Dunning <te...@gmail.com>]

A lot of JIRA's are being opened and then closed with no apparent commits
associated with them.

For example MAHOUT-1725 adds an element-wise power operation but it was
closed as fixed with no apparent discussion and with no commits attached to
the JIRA.

What is happening?

Re: JIRA's with no commits

[Andrew Musselman <an...@gmail.com>]

For reference https://github.com/apache/mahout/pull/135

On Wednesday, June 17, 2015, Andrew Musselman <an...@gmail.com>
wrote:

> We talked about it a lot, some on Slack; was work finally approved for
> donation.  I reviewed it, looked great.
>
> On Wednesday, June 17, 2015, Ted Dunning <ted.dunning@gmail.com
> <javascript:_e(%7B%7D,'cvml','ted.dunning@gmail.com');>> wrote:
>
>> 5k lines in a single commit?
>>
>> No discussion on the list?
>>
>>
>>
>> On Wed, Jun 17, 2015 at 11:26 PM, Andrew Musselman <
>> andrew.musselman@gmail.com> wrote:
>>
>> > Sounds like part of PR 135 which is Dmitriy's 5k-line-diff drop from the
>> > other week.
>> >
>> > On Wednesday, June 17, 2015, Ted Dunning <te...@gmail.com> wrote:
>> >
>> > > A lot of JIRA's are being opened and then closed with no apparent
>> commits
>> > > associated with them.
>> > >
>> > > For example MAHOUT-1725 adds an element-wise power operation but it
>> was
>> > > closed as fixed with no apparent discussion and with no commits
>> attached
>> > to
>> > > the JIRA.
>> > >
>> > > What is happening?
>> > >
>> >
>>
>

Re: JIRA's with no commits

[Ted Dunning <te...@gmail.com>]

On Thu, Jun 18, 2015 at 7:08 AM, Suneel Marthi <sm...@apache.org> wrote:

> Agreed. We have been keeping all project and design discussions to dev@
> mailing lists and that's still is the case.
>

I just took a look at Slack and there is a long conversation on general
about the trade-offs of matrix algorithms.  Then another about the benefits
or costs of multi-backend architecture.

These are not discussions about release coordination.  They are design
discussions.

Re: JIRA's with no commits

[Suneel Marthi <sm...@apache.org>]

Agreed. We have been keeping all project and design discussions to dev@
mailing lists and that's still is the case.
If something about the recent PR needs to be discussed, please feel free to
start the convo on dev@.

Hope that clarifies everything now and I would like to conclude this thread.

On Thu, Jun 18, 2015 at 10:04 AM, Dmitriy Lyubimov <dl...@gmail.com>
wrote:

> Asf git mirrors github comments to jira and to dev list. There have been no
> discussions on the slack about the code other than announce of the PR
> itself (which jira and dev do as well). Discussion time was allowed the
> usual time, 5 business says or so. The bulking up of contributions is
> unfortunate artifact of bureacracy at big corporations, process no one can
> affect. Contributions under corporate cla go thru internal review for
> months, after which they cannot be changed.
> On Jun 18, 2015 6:54 AM, "Suneel Marthi" <sm...@apache.org> wrote:
>
> > While I agree that most of the project and design discussions need to be
> > confined to dev@ mailing lists and we have been abiding by that norm and
> > not resorting to private slack channels.
> > The PR that's in question has been in Skunkworks for a while and has only
> > recently been pushed to the public codebase. This PR has been open for a
> > while now and there's been enuf comments and feedback on the PR.
> >
> > The JIRAs corresponding to the PR could have done with a comment
> something
> > like "Fixed by PR#XX", something we have been doing always and should be
> > cognizant of going forward.  Given that we r now officially using Github,
> > most of the comments and discussions happen on the PR itself and would be
> > reflected on the JIRA, there is no need to repeat the conversation on the
> > mailing lists again.
> >
> > I guess this discussion stems from the fact that the recent 5K lines PR
> is
> > tied to some 20+ JIRAs that were created for it and yet the comments on
> the
> > PR are not reflected in any of the JIRAs. I agree that this shouldn't be
> > happening, but this specific PR is from Skunkworks that's been pending
> > clearance from the contributor's corporate legal for over 6 months now
> and
> > has only been growing in size while pending clearance from corporate
> > legals. This is a one off exception and shouldn't happen going forward as
> > most committers are now past their respective corporate legal hurdles and
> > have clearances.
> >
> > About Slack: We have been using slack to coordinate release process when
> > its easier to have the team together and schedule hangouts. Most of the
> > design and project discussions still happen on dev@, an example being
> the
> > recent Cholesky Decomposition and Spark Shell enhancements. Slack is only
> > being used to bring the team together to better coordinate release
> process
> > and nothing more. Yes, there are exceptions when we do discuss things on
> > slack but that's usually stuff that's of little or no interest to the
> > general public and is not project specific. The intent here is definitely
> > not to become an 'Openly Closed' project.
> >
> > If there's a question about the PR itself, please feel free to start the
> > discussion on dev@.
> >
> >
> >
> > On Thu, Jun 18, 2015 at 4:52 AM, Andrew Musselman <
> > andrew.musselman@gmail.com> wrote:
> >
> > > Do you think PR comments are relevant discussions?  Again, what is the
> > > allowance/guidance from the ASF for them, now that Github is officially
> > > approved/advised.
> > >
> > > I suggest it's worth raising to the larger ASF community for comment
> and
> > > adaptation.
> > >
> > > On Thu, Jun 18, 2015 at 1:45 AM, Sebastian <ss...@apache.org> wrote:
> > >
> > > > The ASF mandates that all relevant discussions happen on the
> > mailinglist.
> > > >
> > > > Best,
> > > > Sebastian
> > > >
> > > >
> > > > On 18.06.2015 10:44, Andrew Musselman wrote:
> > > >
> > > >> What do you mean no-go, that there's no reasonable way to
> incorporate
> > > >> discussion from other channels to the list?
> > > >>
> > > >> On Thu, Jun 18, 2015 at 1:21 AM, Sebastian <ss...@apache.org> wrote:
> > > >>
> > > >>  Having these discussions in a non-public environment prevents all
> > > >>> non-invited people (e.g. all non-committers) from participating in
> > the
> > > >>> development. I think this is a huge no-go.
> > > >>>
> > > >>> Best,
> > > >>> Sebastian
> > > >>>
> > > >>>
> > > >>> On 18.06.2015 09:43, Ted Dunning wrote:
> > > >>>
> > > >>>  On Thu, Jun 18, 2015 at 12:36 AM, Andrew Musselman <
> > > >>>> andrew.musselman@gmail.com> wrote:
> > > >>>>
> > > >>>>   Capturing discussion in a public format and archiving the
> > discussion
> > > >>>>
> > > >>>>> would
> > > >>>>> be preferable to fragmenting across lists, PR comments, and
> Slack,
> > > but
> > > >>>>> the
> > > >>>>> tools are all valuable, and until we find a way to build a digest
> > for
> > > >>>>> the
> > > >>>>> archives I support using them all.
> > > >>>>>
> > > >>>>>
> > > >>>>>  Actually, capturing the design discussion on the list is not
> just
> > > >>>> preferable.
> > > >>>>
> > > >>>> It is required.
> > > >>>>
> > > >>>> Using alternative tools is fine and all, but not if it compromises
> > > that
> > > >>>> core requirement.
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>
> > >
> >
>

Re: JIRA's with no commits

[Dmitriy Lyubimov <dl...@gmail.com>]

Asf git mirrors github comments to jira and to dev list. There have been no
discussions on the slack about the code other than announce of the PR
itself (which jira and dev do as well). Discussion time was allowed the
usual time, 5 business says or so. The bulking up of contributions is
unfortunate artifact of bureacracy at big corporations, process no one can
affect. Contributions under corporate cla go thru internal review for
months, after which they cannot be changed.
On Jun 18, 2015 6:54 AM, "Suneel Marthi" <sm...@apache.org> wrote:

> While I agree that most of the project and design discussions need to be
> confined to dev@ mailing lists and we have been abiding by that norm and
> not resorting to private slack channels.
> The PR that's in question has been in Skunkworks for a while and has only
> recently been pushed to the public codebase. This PR has been open for a
> while now and there's been enuf comments and feedback on the PR.
>
> The JIRAs corresponding to the PR could have done with a comment something
> like "Fixed by PR#XX", something we have been doing always and should be
> cognizant of going forward.  Given that we r now officially using Github,
> most of the comments and discussions happen on the PR itself and would be
> reflected on the JIRA, there is no need to repeat the conversation on the
> mailing lists again.
>
> I guess this discussion stems from the fact that the recent 5K lines PR is
> tied to some 20+ JIRAs that were created for it and yet the comments on the
> PR are not reflected in any of the JIRAs. I agree that this shouldn't be
> happening, but this specific PR is from Skunkworks that's been pending
> clearance from the contributor's corporate legal for over 6 months now and
> has only been growing in size while pending clearance from corporate
> legals. This is a one off exception and shouldn't happen going forward as
> most committers are now past their respective corporate legal hurdles and
> have clearances.
>
> About Slack: We have been using slack to coordinate release process when
> its easier to have the team together and schedule hangouts. Most of the
> design and project discussions still happen on dev@, an example being the
> recent Cholesky Decomposition and Spark Shell enhancements. Slack is only
> being used to bring the team together to better coordinate release process
> and nothing more. Yes, there are exceptions when we do discuss things on
> slack but that's usually stuff that's of little or no interest to the
> general public and is not project specific. The intent here is definitely
> not to become an 'Openly Closed' project.
>
> If there's a question about the PR itself, please feel free to start the
> discussion on dev@.
>
>
>
> On Thu, Jun 18, 2015 at 4:52 AM, Andrew Musselman <
> andrew.musselman@gmail.com> wrote:
>
> > Do you think PR comments are relevant discussions?  Again, what is the
> > allowance/guidance from the ASF for them, now that Github is officially
> > approved/advised.
> >
> > I suggest it's worth raising to the larger ASF community for comment and
> > adaptation.
> >
> > On Thu, Jun 18, 2015 at 1:45 AM, Sebastian <ss...@apache.org> wrote:
> >
> > > The ASF mandates that all relevant discussions happen on the
> mailinglist.
> > >
> > > Best,
> > > Sebastian
> > >
> > >
> > > On 18.06.2015 10:44, Andrew Musselman wrote:
> > >
> > >> What do you mean no-go, that there's no reasonable way to incorporate
> > >> discussion from other channels to the list?
> > >>
> > >> On Thu, Jun 18, 2015 at 1:21 AM, Sebastian <ss...@apache.org> wrote:
> > >>
> > >>  Having these discussions in a non-public environment prevents all
> > >>> non-invited people (e.g. all non-committers) from participating in
> the
> > >>> development. I think this is a huge no-go.
> > >>>
> > >>> Best,
> > >>> Sebastian
> > >>>
> > >>>
> > >>> On 18.06.2015 09:43, Ted Dunning wrote:
> > >>>
> > >>>  On Thu, Jun 18, 2015 at 12:36 AM, Andrew Musselman <
> > >>>> andrew.musselman@gmail.com> wrote:
> > >>>>
> > >>>>   Capturing discussion in a public format and archiving the
> discussion
> > >>>>
> > >>>>> would
> > >>>>> be preferable to fragmenting across lists, PR comments, and Slack,
> > but
> > >>>>> the
> > >>>>> tools are all valuable, and until we find a way to build a digest
> for
> > >>>>> the
> > >>>>> archives I support using them all.
> > >>>>>
> > >>>>>
> > >>>>>  Actually, capturing the design discussion on the list is not just
> > >>>> preferable.
> > >>>>
> > >>>> It is required.
> > >>>>
> > >>>> Using alternative tools is fine and all, but not if it compromises
> > that
> > >>>> core requirement.
> > >>>>
> > >>>>
> > >>>>
> > >>
> >
>

Re: JIRA's with no commits

[Suneel Marthi <sm...@apache.org>]

While I agree that most of the project and design discussions need to be
confined to dev@ mailing lists and we have been abiding by that norm and
not resorting to private slack channels.
The PR that's in question has been in Skunkworks for a while and has only
recently been pushed to the public codebase. This PR has been open for a
while now and there's been enuf comments and feedback on the PR.

The JIRAs corresponding to the PR could have done with a comment something
like "Fixed by PR#XX", something we have been doing always and should be
cognizant of going forward.  Given that we r now officially using Github,
most of the comments and discussions happen on the PR itself and would be
reflected on the JIRA, there is no need to repeat the conversation on the
mailing lists again.

I guess this discussion stems from the fact that the recent 5K lines PR is
tied to some 20+ JIRAs that were created for it and yet the comments on the
PR are not reflected in any of the JIRAs. I agree that this shouldn't be
happening, but this specific PR is from Skunkworks that's been pending
clearance from the contributor's corporate legal for over 6 months now and
has only been growing in size while pending clearance from corporate
legals. This is a one off exception and shouldn't happen going forward as
most committers are now past their respective corporate legal hurdles and
have clearances.

About Slack: We have been using slack to coordinate release process when
its easier to have the team together and schedule hangouts. Most of the
design and project discussions still happen on dev@, an example being the
recent Cholesky Decomposition and Spark Shell enhancements. Slack is only
being used to bring the team together to better coordinate release process
and nothing more. Yes, there are exceptions when we do discuss things on
slack but that's usually stuff that's of little or no interest to the
general public and is not project specific. The intent here is definitely
not to become an 'Openly Closed' project.

If there's a question about the PR itself, please feel free to start the
discussion on dev@.



On Thu, Jun 18, 2015 at 4:52 AM, Andrew Musselman <
andrew.musselman@gmail.com> wrote:

> Do you think PR comments are relevant discussions?  Again, what is the
> allowance/guidance from the ASF for them, now that Github is officially
> approved/advised.
>
> I suggest it's worth raising to the larger ASF community for comment and
> adaptation.
>
> On Thu, Jun 18, 2015 at 1:45 AM, Sebastian <ss...@apache.org> wrote:
>
> > The ASF mandates that all relevant discussions happen on the mailinglist.
> >
> > Best,
> > Sebastian
> >
> >
> > On 18.06.2015 10:44, Andrew Musselman wrote:
> >
> >> What do you mean no-go, that there's no reasonable way to incorporate
> >> discussion from other channels to the list?
> >>
> >> On Thu, Jun 18, 2015 at 1:21 AM, Sebastian <ss...@apache.org> wrote:
> >>
> >>  Having these discussions in a non-public environment prevents all
> >>> non-invited people (e.g. all non-committers) from participating in the
> >>> development. I think this is a huge no-go.
> >>>
> >>> Best,
> >>> Sebastian
> >>>
> >>>
> >>> On 18.06.2015 09:43, Ted Dunning wrote:
> >>>
> >>>  On Thu, Jun 18, 2015 at 12:36 AM, Andrew Musselman <
> >>>> andrew.musselman@gmail.com> wrote:
> >>>>
> >>>>   Capturing discussion in a public format and archiving the discussion
> >>>>
> >>>>> would
> >>>>> be preferable to fragmenting across lists, PR comments, and Slack,
> but
> >>>>> the
> >>>>> tools are all valuable, and until we find a way to build a digest for
> >>>>> the
> >>>>> archives I support using them all.
> >>>>>
> >>>>>
> >>>>>  Actually, capturing the design discussion on the list is not just
> >>>> preferable.
> >>>>
> >>>> It is required.
> >>>>
> >>>> Using alternative tools is fine and all, but not if it compromises
> that
> >>>> core requirement.
> >>>>
> >>>>
> >>>>
> >>
>

Re: JIRA's with no commits

[Andrew Musselman <an...@gmail.com>]

Do you think PR comments are relevant discussions?  Again, what is the
allowance/guidance from the ASF for them, now that Github is officially
approved/advised.

I suggest it's worth raising to the larger ASF community for comment and
adaptation.

On Thu, Jun 18, 2015 at 1:45 AM, Sebastian <ss...@apache.org> wrote:

> The ASF mandates that all relevant discussions happen on the mailinglist.
>
> Best,
> Sebastian
>
>
> On 18.06.2015 10:44, Andrew Musselman wrote:
>
>> What do you mean no-go, that there's no reasonable way to incorporate
>> discussion from other channels to the list?
>>
>> On Thu, Jun 18, 2015 at 1:21 AM, Sebastian <ss...@apache.org> wrote:
>>
>>  Having these discussions in a non-public environment prevents all
>>> non-invited people (e.g. all non-committers) from participating in the
>>> development. I think this is a huge no-go.
>>>
>>> Best,
>>> Sebastian
>>>
>>>
>>> On 18.06.2015 09:43, Ted Dunning wrote:
>>>
>>>  On Thu, Jun 18, 2015 at 12:36 AM, Andrew Musselman <
>>>> andrew.musselman@gmail.com> wrote:
>>>>
>>>>   Capturing discussion in a public format and archiving the discussion
>>>>
>>>>> would
>>>>> be preferable to fragmenting across lists, PR comments, and Slack, but
>>>>> the
>>>>> tools are all valuable, and until we find a way to build a digest for
>>>>> the
>>>>> archives I support using them all.
>>>>>
>>>>>
>>>>>  Actually, capturing the design discussion on the list is not just
>>>> preferable.
>>>>
>>>> It is required.
>>>>
>>>> Using alternative tools is fine and all, but not if it compromises that
>>>> core requirement.
>>>>
>>>>
>>>>
>>

Re: JIRA's with no commits

[Sebastian <ss...@apache.org>]

The ASF mandates that all relevant discussions happen on the mailinglist.

Best,
Sebastian

On 18.06.2015 10:44, Andrew Musselman wrote:
> What do you mean no-go, that there's no reasonable way to incorporate
> discussion from other channels to the list?
>
> On Thu, Jun 18, 2015 at 1:21 AM, Sebastian <ss...@apache.org> wrote:
>
>> Having these discussions in a non-public environment prevents all
>> non-invited people (e.g. all non-committers) from participating in the
>> development. I think this is a huge no-go.
>>
>> Best,
>> Sebastian
>>
>>
>> On 18.06.2015 09:43, Ted Dunning wrote:
>>
>>> On Thu, Jun 18, 2015 at 12:36 AM, Andrew Musselman <
>>> andrew.musselman@gmail.com> wrote:
>>>
>>>   Capturing discussion in a public format and archiving the discussion
>>>> would
>>>> be preferable to fragmenting across lists, PR comments, and Slack, but
>>>> the
>>>> tools are all valuable, and until we find a way to build a digest for the
>>>> archives I support using them all.
>>>>
>>>>
>>> Actually, capturing the design discussion on the list is not just
>>> preferable.
>>>
>>> It is required.
>>>
>>> Using alternative tools is fine and all, but not if it compromises that
>>> core requirement.
>>>
>>>
>

Re: JIRA's with no commits

[Andrew Musselman <an...@gmail.com>]

What do you mean no-go, that there's no reasonable way to incorporate
discussion from other channels to the list?

On Thu, Jun 18, 2015 at 1:21 AM, Sebastian <ss...@apache.org> wrote:

> Having these discussions in a non-public environment prevents all
> non-invited people (e.g. all non-committers) from participating in the
> development. I think this is a huge no-go.
>
> Best,
> Sebastian
>
>
> On 18.06.2015 09:43, Ted Dunning wrote:
>
>> On Thu, Jun 18, 2015 at 12:36 AM, Andrew Musselman <
>> andrew.musselman@gmail.com> wrote:
>>
>>  Capturing discussion in a public format and archiving the discussion
>>> would
>>> be preferable to fragmenting across lists, PR comments, and Slack, but
>>> the
>>> tools are all valuable, and until we find a way to build a digest for the
>>> archives I support using them all.
>>>
>>>
>> Actually, capturing the design discussion on the list is not just
>> preferable.
>>
>> It is required.
>>
>> Using alternative tools is fine and all, but not if it compromises that
>> core requirement.
>>
>>

Re: JIRA's with no commits

[Sebastian <ss...@apache.org>]

Having these discussions in a non-public environment prevents all 
non-invited people (e.g. all non-committers) from participating in the 
development. I think this is a huge no-go.

Best,
Sebastian

On 18.06.2015 09:43, Ted Dunning wrote:
> On Thu, Jun 18, 2015 at 12:36 AM, Andrew Musselman <
> andrew.musselman@gmail.com> wrote:
>
>> Capturing discussion in a public format and archiving the discussion would
>> be preferable to fragmenting across lists, PR comments, and Slack, but the
>> tools are all valuable, and until we find a way to build a digest for the
>> archives I support using them all.
>>
>
> Actually, capturing the design discussion on the list is not just
> preferable.
>
> It is required.
>
> Using alternative tools is fine and all, but not if it compromises that
> core requirement.
>

Re: JIRA's with no commits

[Andrew Musselman <an...@gmail.com>]

Leaving Slack aside, what's the guidance from ASF on capturing PR comments
now that Github's an approved platform?

On Thu, Jun 18, 2015 at 12:43 AM, Ted Dunning <te...@gmail.com> wrote:

> On Thu, Jun 18, 2015 at 12:36 AM, Andrew Musselman <
> andrew.musselman@gmail.com> wrote:
>
> > Capturing discussion in a public format and archiving the discussion
> would
> > be preferable to fragmenting across lists, PR comments, and Slack, but
> the
> > tools are all valuable, and until we find a way to build a digest for the
> > archives I support using them all.
> >
>
> Actually, capturing the design discussion on the list is not just
> preferable.
>
> It is required.
>
> Using alternative tools is fine and all, but not if it compromises that
> core requirement.
>

Re: JIRA's with no commits

[Ted Dunning <te...@gmail.com>]

On Thu, Jun 18, 2015 at 12:36 AM, Andrew Musselman <
andrew.musselman@gmail.com> wrote:

> Capturing discussion in a public format and archiving the discussion would
> be preferable to fragmenting across lists, PR comments, and Slack, but the
> tools are all valuable, and until we find a way to build a digest for the
> archives I support using them all.
>

Actually, capturing the design discussion on the list is not just
preferable.

It is required.

Using alternative tools is fine and all, but not if it compromises that
core requirement.

Re: JIRA's with no commits

[Andrew Musselman <an...@gmail.com>]

Chalk it up to using expedient tools to pull the team together to ship a
major release and to pull in a big contribution after a long wait.

Capturing discussion in a public format and archiving the discussion would
be preferable to fragmenting across lists, PR comments, and Slack, but the
tools are all valuable, and until we find a way to build a digest for the
archives I support using them all.

Anyone know what other projects are doing to bring many-threaded
conversations into their dev list, if any?

On Wed, Jun 17, 2015 at 11:56 PM, Ted Dunning <te...@gmail.com> wrote:

> Slack isn't the mailing list.
>
>
>
> On Wed, Jun 17, 2015 at 11:43 PM, Andrew Musselman <
> andrew.musselman@gmail.com> wrote:
>
> > We talked about it a lot, some on Slack; was work finally approved for
> > donation.  I reviewed it, looked great.
> >
> > On Wednesday, June 17, 2015, Ted Dunning <te...@gmail.com> wrote:
> >
> > > 5k lines in a single commit?
> > >
> > > No discussion on the list?
> > >
> > >
> > >
> > > On Wed, Jun 17, 2015 at 11:26 PM, Andrew Musselman <
> > > andrew.musselman@gmail.com <javascript:;>> wrote:
> > >
> > > > Sounds like part of PR 135 which is Dmitriy's 5k-line-diff drop from
> > the
> > > > other week.
> > > >
> > > > On Wednesday, June 17, 2015, Ted Dunning <ted.dunning@gmail.com
> > > <javascript:;>> wrote:
> > > >
> > > > > A lot of JIRA's are being opened and then closed with no apparent
> > > commits
> > > > > associated with them.
> > > > >
> > > > > For example MAHOUT-1725 adds an element-wise power operation but it
> > was
> > > > > closed as fixed with no apparent discussion and with no commits
> > > attached
> > > > to
> > > > > the JIRA.
> > > > >
> > > > > What is happening?
> > > > >
> > > >
> > >
> >
>

Re: JIRA's with no commits

[Ted Dunning <te...@gmail.com>]

Slack isn't the mailing list.



On Wed, Jun 17, 2015 at 11:43 PM, Andrew Musselman <
andrew.musselman@gmail.com> wrote:

> We talked about it a lot, some on Slack; was work finally approved for
> donation.  I reviewed it, looked great.
>
> On Wednesday, June 17, 2015, Ted Dunning <te...@gmail.com> wrote:
>
> > 5k lines in a single commit?
> >
> > No discussion on the list?
> >
> >
> >
> > On Wed, Jun 17, 2015 at 11:26 PM, Andrew Musselman <
> > andrew.musselman@gmail.com <javascript:;>> wrote:
> >
> > > Sounds like part of PR 135 which is Dmitriy's 5k-line-diff drop from
> the
> > > other week.
> > >
> > > On Wednesday, June 17, 2015, Ted Dunning <ted.dunning@gmail.com
> > <javascript:;>> wrote:
> > >
> > > > A lot of JIRA's are being opened and then closed with no apparent
> > commits
> > > > associated with them.
> > > >
> > > > For example MAHOUT-1725 adds an element-wise power operation but it
> was
> > > > closed as fixed with no apparent discussion and with no commits
> > attached
> > > to
> > > > the JIRA.
> > > >
> > > > What is happening?
> > > >
> > >
> >
>

Re: JIRA's with no commits

[Andrew Musselman <an...@gmail.com>]

We talked about it a lot, some on Slack; was work finally approved for
donation.  I reviewed it, looked great.

On Wednesday, June 17, 2015, Ted Dunning <te...@gmail.com> wrote:

> 5k lines in a single commit?
>
> No discussion on the list?
>
>
>
> On Wed, Jun 17, 2015 at 11:26 PM, Andrew Musselman <
> andrew.musselman@gmail.com <javascript:;>> wrote:
>
> > Sounds like part of PR 135 which is Dmitriy's 5k-line-diff drop from the
> > other week.
> >
> > On Wednesday, June 17, 2015, Ted Dunning <ted.dunning@gmail.com
> <javascript:;>> wrote:
> >
> > > A lot of JIRA's are being opened and then closed with no apparent
> commits
> > > associated with them.
> > >
> > > For example MAHOUT-1725 adds an element-wise power operation but it was
> > > closed as fixed with no apparent discussion and with no commits
> attached
> > to
> > > the JIRA.
> > >
> > > What is happening?
> > >
> >
>

Re: JIRA's with no commits

[Ted Dunning <te...@gmail.com>]

5k lines in a single commit?

No discussion on the list?



On Wed, Jun 17, 2015 at 11:26 PM, Andrew Musselman <
andrew.musselman@gmail.com> wrote:

> Sounds like part of PR 135 which is Dmitriy's 5k-line-diff drop from the
> other week.
>
> On Wednesday, June 17, 2015, Ted Dunning <te...@gmail.com> wrote:
>
> > A lot of JIRA's are being opened and then closed with no apparent commits
> > associated with them.
> >
> > For example MAHOUT-1725 adds an element-wise power operation but it was
> > closed as fixed with no apparent discussion and with no commits attached
> to
> > the JIRA.
> >
> > What is happening?
> >
>

Re: JIRA's with no commits

[Andrew Musselman <an...@gmail.com>]

Sounds like part of PR 135 which is Dmitriy's 5k-line-diff drop from the
other week.

On Wednesday, June 17, 2015, Ted Dunning <te...@gmail.com> wrote:

> A lot of JIRA's are being opened and then closed with no apparent commits
> associated with them.
>
> For example MAHOUT-1725 adds an element-wise power operation but it was
> closed as fixed with no apparent discussion and with no commits attached to
> the JIRA.
>
> What is happening?
>