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

he title of the PR to >> [MXNET-JIRA_ID]ORIGINAL_TITLE. During the process I find step-3/4 are >> somehow unnecessary. >> >> >> Best, >> >> Xingjian >> >> >> From: Naveen Swamy <mnnav...@gmail.com&g

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

4 are > somehow unnecessary. > > > Best, > > Xingjian > > > From: Naveen Swamy <mnnav...@gmail.com> > Sent: Friday, March 9, 2018 3:26 AM > To: dev@mxnet.incubator.apache.org > Subject: Re: [RESULT][VOTE] tracking code cha

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

> > From: Naveen Swamy <mnnav...@gmail.com> > Sent: Friday, March 9, 2018 3:26 AM > To: dev@mxnet.incubator.apache.org > Subject: Re: [RESULT][VOTE] tracking code changes with JIRA by associating > pull requests > > Whether to use Jira

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

]ORIGINAL_TITLE. During the process I find step-3/4 are somehow unnecessary. Best, Xingjian From: Naveen Swamy <mnnav...@gmail.com> Sent: Friday, March 9, 2018 3:26 AM To: dev@mxnet.incubator.apache.org Subject: Re: [RESULT][VOTE] tracking code changes wit

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

t/issues?q=is%3Aopen+is%3Aissue+label%3A%22Feature+request%22 Xingjian From: Naveen Swamy <mnnav...@gmail.com> Sent: Friday, March 9, 2018 3:08 AM To: dev@mxnet.incubator.apache.org Subject: Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull r

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

homepage, > which encourages them to do more for the community. > > Best, > Xingjian > > > > From: Nan Zhu <zhunanmcg...@gmail.com> > Sent: Friday, March 9, 2018 2:14 AM > To: dev@mxnet.incubator.apache.org > Subject: Re: [RESULT][

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

, Xingjian From: Nan Zhu <zhunanmcg...@gmail.com> Sent: Friday, March 9, 2018 2:14 AM To: dev@mxnet.incubator.apache.org Subject: Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests just giving an example about Chris's opinion (how JIRA

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: [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

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

I also see this as a big advantage in terms of transparency. I personally will try to move away from any company internal issue trackers (except for confidential cases) and instead work on Jira that is being managed by the community. This allows everybody to see what is being worked on and gives

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

I am +1 for using JIRA. Managing bigger projects within MXNet on JIRA brings openness to the project. MXNet Users and the contributors also get a sense of where the project is heading. Bigger Tasks can be divided into sub-tasks which contributors can pick up small tasks based on their expertise on

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

The vote was discussed on private@ before the vote on dev@, and the vote went on for a very long time. There was ZERO resistance. No one "snuck" it in or "slipped it by". This, hopefully, phases out both SIM and tt, which are both are being used in ways that aren't what they're even designed

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

I'm not quite sure if I have enough background on reasons for or against this to vote in the next round, but my two cents: I didn't see much debate on why we need yet another tool for issues that we have to manually maintain...the vote kind of slid in there without many stakeholders realizing what

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

Would it be possible to add the instruction to the PR template (along with a link to Jira) in order to provide users with an easy way to create an issue if required. -Marco On Wed, Mar 7, 2018 at 6:34 AM, Chris Olivier wrote: > Eric, > > while you may not be, most people

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

Eric, while you may not be, most people are using some sort of crappy-JIRA-like-tool (such as SIM) which is both way behind JIRA in utility and usability as well as not public, so the rest of the world can’t see the backlog or what work orders are or whatever. the development process does not

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

I think the right approach here is to start another vote on terminate the starting process of using JIRA, since we have passed this vote On Tue, Mar 6, 2018 at 9:13 PM, Eric Xie wrote: > -1 > > JIRA is ancient and arcane. This adds unnecessary overhead. > > On 2018/03/03

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

-1 JIRA is ancient and arcane. This adds unnecessary overhead. On 2018/03/03 06:11:12, CodingCat wrote: > This vote passes with 6 +1 votes (6 bindings) and no 0 or -1 votes. > > Binding +1: > Chris Olivier > Indhu Bharathi > Suneel Marthi > Yuan Tang > Marco de Abreu >