Re: jira rights

[kurt greaves]

I ran into this a few weeks ago. Basically contributors can assign any
Cassandra ticket to anyone with an account, however non-contributors can't
do anything. So you still have to get a contributor to assign you a ticket
if you are not one yourself (or get added to contributors).

Re: jira rights

[Jeff Jirsa]

It's probably the case that you could have self-assigned after creation,
but I've added you just to be safe.


On Fri, Jul 21, 2017 at 9:45 AM, Malcolm Taylor  wrote:

> Hi Jason,
> When I start to create a JIRA issue for Cassandra, I don't see the
> "Assignee" field. That makes me think I haven't got rights yet for
> Cassandra, because I do see assignee when creating issues for other Apache
> projects.
> thanks,
> Malcolm
>
> On 21 July 2017 at 16:53, Jason Brown  wrote:
>
> > Malcolm,
> >
> > You should be able to comment on and assign tickets to yourself, and all
> > the standard Jira use stuff. What specific behavior is not working for
> you?
> >
> > Thanks
> >
> > -Jason
> >
> > On Fri, Jul 21, 2017 at 08:36 Malcolm Taylor  wrote:
> >
> > > Please grant me (malcolmt) contributor rights for the Cassandra Jira
> > site.
> > > thanks,
> > > Malcolm
> > >
> >
>

Re: jira rights

[Malcolm Taylor]

Hi Jason,
When I start to create a JIRA issue for Cassandra, I don't see the
"Assignee" field. That makes me think I haven't got rights yet for
Cassandra, because I do see assignee when creating issues for other Apache
projects.
thanks,
Malcolm

On 21 July 2017 at 16:53, Jason Brown  wrote:

> Malcolm,
>
> You should be able to comment on and assign tickets to yourself, and all
> the standard Jira use stuff. What specific behavior is not working for you?
>
> Thanks
>
> -Jason
>
> On Fri, Jul 21, 2017 at 08:36 Malcolm Taylor  wrote:
>
> > Please grant me (malcolmt) contributor rights for the Cassandra Jira
> site.
> > thanks,
> > Malcolm
> >
>

Re: jira rights

[Jason Brown]

Malcolm,

You should be able to comment on and assign tickets to yourself, and all
the standard Jira use stuff. What specific behavior is not working for you?

Thanks

-Jason

On Fri, Jul 21, 2017 at 08:36 Malcolm Taylor  wrote:

> Please grant me (malcolmt) contributor rights for the Cassandra Jira site.
> thanks,
> Malcolm
>

jira rights

[Malcolm Taylor]

Please grant me (malcolmt) contributor rights for the Cassandra Jira site.
thanks,
Malcolm

Re: CHANGES.txt

[Stefan Podkowinski]

Thanks your responses! Seems like all of you prefer to have both trivial
and non-trivial updates in CHANGES.txt. I'm going to keep that in mind,
but will continue to omit them for documentation edits.


On 18.07.2017 23:49, kurt greaves wrote:
> I agree that all patches should be added to changes.txt, just to rule out
> any ambiguities. When people look at Changes.txt it's usually to find
> something specific, not to browse the list of changes. Anything significant
> should make it into news.txt, which is more appropriate for users.
> changes.txt is more aimed at developers in my opinion.
> 
> On that note, messages like "Remove unused method" should be more specific,
> that's just a bad commit message in general, and doesn't give at context.
> 

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org