You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@livy.apache.org by Albert Cheng <cq...@qq.com> on 2018/02/05 13:55:42 UTC
how to assign issue to myself?
According to the document in `https://livy.incubator.apache.org/community/`.I have subscribed dev@livy.incubator.apache.org, but I cannot assign issue to myself still.
Re: how to assign issue to myself?
Posted by Alex Bozarth <aj...@us.ibm.com>.
Odd about the JIRA permissions, the user claims he couldn't select Livy in
the project drop down in the Create new JIRA pop up.
Alex Bozarth
Software Engineer
Spark Technology Center
E-mail: ajbozart@us.ibm.com
GitHub: github.com/ajbozarth
505 Howard Street
San Francisco, CA 94105
United States
From: Marcelo Vanzin <va...@cloudera.com>
To: dev@livy.incubator.apache.org
Date: 02/05/2018 01:22 PM
Subject: Re: how to assign issue to myself?
On Mon, Feb 5, 2018 at 1:17 PM, Alex Bozarth <aj...@us.ibm.com> wrote:
> So far we've been assigning JIRAs when someone opens a PR on them as we
did before joining the incubator, but it may be better to update on
completion instead like Spark. If we decide to do so we should update the
website to say so and update the merge script to reassign users if
possible. What does everyone else think?
Don't really have an opinion here.
> And on a related note, are there restrictions on who can *open* JIRAs for
Livy, we have at least one person on user who could open a Livy JIRA (but
could still open a Spark one).
I remember checking the JIRA permissions and they seem correct. Any
logged in user should be able to create a new bug.
--
Marcelo
Re: how to assign issue to myself?
Posted by Marcelo Vanzin <va...@cloudera.com>.
On Mon, Feb 5, 2018 at 1:17 PM, Alex Bozarth <aj...@us.ibm.com> wrote:
> So far we've been assigning JIRAs when someone opens a PR on them as we did before joining the incubator, but it may be better to update on completion instead like Spark. If we decide to do so we should update the website to say so and update the merge script to reassign users if possible. What does everyone else think?
Don't really have an opinion here.
> And on a related note, are there restrictions on who can *open* JIRAs for Livy, we have at least one person on user who could open a Livy JIRA (but could still open a Spark one).
I remember checking the JIRA permissions and they seem correct. Any
logged in user should be able to create a new bug.
--
Marcelo
Re: how to assign issue to myself?
Posted by Alex Bozarth <aj...@us.ibm.com>.
So far we've been assigning JIRAs when someone opens a PR on them as we did
before joining the incubator, but it may be better to update on completion
instead like Spark. If we decide to do so we should update the website to
say so and update the merge script to reassign users if possible. What does
everyone else think?
And on a related note, are there restrictions on who can *open* JIRAs for
Livy, we have at least one person on user who could open a Livy JIRA (but
could still open a Spark one).
Alex Bozarth
Software Engineer
Spark Technology Center
E-mail: ajbozart@us.ibm.com
GitHub: github.com/ajbozarth
505 Howard Street
San Francisco, CA 94105
United States
From: Marcelo Vanzin <va...@cloudera.com>
To: dev@livy.incubator.apache.org
Date: 02/05/2018 10:01 AM
Subject: Re: how to assign issue to myself?
If I remember how the tracker was set up, only Livy committers can
assign bugs. I believe we follow a model similar to Spark's where
issues are only assigned after the PR associated with them is merged.
On Mon, Feb 5, 2018 at 5:55 AM, Albert Cheng <cq...@qq.com> wrote:
> According to the document in
`https://urldefense.proofpoint.com/v2/url?u=https-3A__livy.incubator.apache.org_community_-2560.I&d=DwIBaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo&m=u-2HiUHkfOAxEZZQWuLSJYBi-z4PClvKVHsytLievX8&s=wSxsTQrhG9xaXcR0PFKqnh8Nf9dOnxPkK4geo7Zvy60&e=
have subscribed dev@livy.incubator.apache.org, but I cannot assign issue
to myself still.
--
Marcelo
Re: how to assign issue to myself?
Posted by Marcelo Vanzin <va...@cloudera.com>.
If I remember how the tracker was set up, only Livy committers can
assign bugs. I believe we follow a model similar to Spark's where
issues are only assigned after the PR associated with them is merged.
On Mon, Feb 5, 2018 at 5:55 AM, Albert Cheng <cq...@qq.com> wrote:
> According to the document in `https://livy.incubator.apache.org/community/`.I have subscribed dev@livy.incubator.apache.org, but I cannot assign issue to myself still.
--
Marcelo