Re: Assign JIRA issue

Done. On Thu, Mar 8, 2018 at 9:10 PM Zhao, Patric wrote: > @Chris please add into group too. > > > -Original Message- > > From: YiZhi Liu [mailto:liuyi...@apache.org] > > Sent: Friday, March 9, 2018 8:40 AM > > To: dev@mxnet.incubator.apache.org > > Subject: Re:

RE: Assign JIRA issue

@Chris please add into group too. > -Original Message- > From: YiZhi Liu [mailto:liuyi...@apache.org] > Sent: Friday, March 9, 2018 8:40 AM > To: dev@mxnet.incubator.apache.org > Subject: Re: Assign JIRA issue > > Yes it is. Thanks! > > 2018-03-08 16:04 GMT-08:00 Chris Olivier

Re: Assign JIRA issue

Yes it is. Thanks! 2018-03-08 16:04 GMT-08:00 Chris Olivier : > Done. Assume you meant your apache.org onew (there there two) > > On Thu, Mar 8, 2018 at 3:47 PM, YiZhi Liu wrote: > >> Hi Chris, >> >> could you help to add me to the permission group

Re: Assign JIRA issue

Done. Assume you meant your apache.org onew (there there two) On Thu, Mar 8, 2018 at 3:47 PM, YiZhi Liu wrote: > Hi Chris, > > could you help to add me to the permission group (committer)? > > Thanks, > Yizhi > > 2018-03-07 11:11 GMT-08:00 Chris Olivier

Re: Assign JIRA issue

Hi Chris, could you help to add me to the permission group (committer)? Thanks, Yizhi 2018-03-07 11:11 GMT-08:00 Chris Olivier : > yeah I fixed that > > On Wed, Mar 7, 2018 at 11:09 AM, Marco de Abreu < > marco.g.ab...@googlemail.com> wrote: > >> Would it be possible to

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

Workflow should be: 1. Create JIRA or select JIRA from backlog 2. Mark JIRA as "In Progress" 3. Work on code and submit PR the PR needs to start with [MXNET-XXX] that way the JIRA has the latest updates from github 4. Once PR has been approved., commit the PR 5. Mark the Jira as Resolved and then

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

How should we use Github issues if we do that? Currently it's supposed that issues are created before the PR. Xingjian From: Chris Olivier Sent: Friday, March 9, 2018 3:44 AM To: dev@mxnet.incubator.apache.org Subject: Re: [RESULT][VOTE]

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

You should create the JIRA before you start work (long before the PR) so that people know what's being worked on and don't overlap. Ideally, anything people work on should have been in JIRA for some time before work starts so that there is some sort of holistic view of the direction of the

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

What's the expected workflow if we use JIRA? I'm not clear about that. Currently I'll 1) submit the PR, 2) describe what's done in the PR in detail and refer to the related Github issues, 3) create the JIRA item by copying the PR description, 4) change the title of the PR to

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

Whether to use Jira or not is a moot point now, I suggest lets discuss how to use Github/Jira effectively, to make it easy for contributors(new and veterans). Let us use it for 6 months or so and collect feedback, people who don't find it useful can start another VOTE. On Thu, Mar 8, 2018 at

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

There are a lot of issues out there which can be translated to work items(for e.g. labels such as "Call For Contribution", "Feature" and "Bugs") There should be an easy way to translate these to work items in JIRA. On Thu, Mar 8, 2018 at 11:17 AM, Chris Olivier wrote: >

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

We can also consider to give a special label for all the issues that are "working items". There are lots of efforts spent on assigning the correct label to Github issues. We can then easily select the issues we are interested in, e.g,

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

Oh my God, no... On Thu, Mar 8, 2018 at 10:58 AM, Anirudh wrote: > There should be an easy way to translate all the existing github issues > into work items in JIRA(Considering the work on labelling that is done for > github issues). > Does the JIRA bot handle this ? > >

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

To summarize: - JIRA might be more maintainer friendly(have more features for tracking progress etc.) - Github issues are more community friendly (it has been the way most people contribute, and have lower bar of entry). Tianqi On Thu, Mar 8, 2018 at 11:05 AM, Xingjian SHI

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

I don't think we should transfer all Github issues to Jira that will make Jira issues unmanageable and pretty useless, also not all issues are being worked on or will be worked on. I like the idea of using Jira as a backlog, so contributors/committers create Jira tasks/projects based on what they

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

There is no issue page in Spark (https://github.com/apache/spark) and they rely solely on JIRA to track the working items. This is different from what we are doing now. MXNet associate PRs to working items by linking them to the Github issues, e.g,

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

There should be an easy way to translate all the existing github issues into work items in JIRA(Considering the work on labelling that is done for github issues). Does the JIRA bot handle this ? On Thu, Mar 8, 2018 at 10:40 AM, Chris Olivier wrote: > Anyone can create a

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

Anyone can create a backlog item/JIRA ticket. Obvious cases might include: * Someone thinks of a task and (optionally) wants to develop it themselves, so they create a backlog item and assign it to themself, putting it into "in progress" mode. * Someone dreams up a large feature and wants to

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

just giving an example about Chris's opinion (how JIRA would help for more new users) I can see Spark 2.4 is highly possible to include the nested column pruning in parquet file from its JIRA ( https://issues.apache.org/jira/browse/SPARK-4502) it's hard for me to have any source to get the

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

Almost all Apache projects use JIRA. It's been proven to work in open-source. Having backlog/development process public hopefully will help adoption. Right now, what new users? Adoption is very slow, so I think it's hard to argue that the current way of doing things is effective. On Thu, Mar 8,

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

Cool. Feel free to propose a change to the PR template. How would JIRA be less daunting to new users? -sz > On Mar 8, 2018, at 9:25 AM, Chris Olivier wrote: > > My $0.02 about the PR template. > > I think it's a good idea. I think (just my opinion) is that the

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

My $0.02 about the PR template. I think it's a good idea. I think (just my opinion) is that the adoption is low because it started out too big and daunting. It may get more adoption if we started a little smaller -- with maybe two checkboxes" and also didn't have a line at the top stating

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

Ideally, the JIRA work item should be created before coding starts -- long before the PR. So, I would suggest we don;t automatically create JIRAs because then it sort of defeats the purpose of JIRA managing a backlog. On Thu, Mar 8, 2018 at 8:49 AM, Nan Zhu wrote: > +1

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

The PR template is designed for that and its poor adoption is causing the same issue of missing information in PRs. My concern of using JIRA is that more overhead would deter contribution and worsen the quality of description. -sz > On Mar 8, 2018, at 8:49 AM, Nan Zhu

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

+1 on both suggestions a bit concern is on the quality of JIRA which is created automatically I can see a lot of PRs are not described comprehensively, if we just post what in description to JIRA, it's error-propagating but the quality of JIRA is a big topic worth more discussions On Thu,

Re: JIRA boards help needed

Ok, nevermind, fixed it. On Thu, Mar 8, 2018 at 8:32 AM, Chris Olivier wrote: > Call for help: > > > I am having a problem trying to get the "Backlog" button to appear ont he > new Kanban board. > > As you can see, on the scum board (which is being deprecated in favor of

JIRA boards help needed

Call for help: I am having a problem trying to get the "Backlog" button to appear ont he new Kanban board. As you can see, on the scum board (which is being deprecated in favor of a Kanban board), has a "Backlog" button on the left (four horizontal rectangles stacked on each other, one offset

Proposal: New namespace 'math' for (specific) mathematical functions

Hello, this relates to PR #9982 [MXNET-39]. There, I am implementing two new unary mathematical functions (log of CDF of standard normal distribution, and its derivative). As Eric rightly points out, they have clunky names, and while there are important use cases, they do not lie in the

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

Would it be possible to automatically create JIRA tickets when a GitHub issue is being created? We could then mirror all comments the same way it's happening in https://issues.apache.org/jira/projects/MXNET/issues/MXNET-42 but make sure that the bot works in both ways. A comment on GitHub would be