Re: Issue Tracker not available

2016-01-27 Thread Chip Senkbeil
Luciano, can you confirm Gino's, Corey's, and my JIRA ids on the infrastructure JIRA? On Mon, Jan 25, 2016 at 2:23 PM Gino Bustelo wrote: > @hitesh I'm totally cool with that... but I don't have any access to do > it... @lresende? > > On Mon, Jan 25, 2016 at 1:30 PM, Hitesh

Re: Issue Tracker not available

2016-01-25 Thread Gino Bustelo
@hitesh I'm assuming that we need @lresende to do this. I need to start doing JIRA cleanup and there is very little I can do with the access that I have at the moment. On Thu, Jan 21, 2016 at 3:33 PM, Hitesh Shah wrote: > It might be good to add a few of the PMC as Admins for

Re: Issue Tracker not available

2016-01-21 Thread Gino Bustelo
@lresende It does not seem that I have the ability to assign issues. On Tue, Jan 19, 2016 at 11:42 AM, Gino Bustelo wrote: > Seems like all 'closed' issues are now 'closed' Jira but are marked > 'Unresolved' > > On Tue, Jan 19, 2016 at 11:39 AM, Gino Bustelo

Re: Issue Tracker not available

2016-01-21 Thread Hitesh Shah
It might be good to add a few of the PMC as Admins for the toree project on JIRA. Once that is done, the relevant folks can be added into the committer/contributor roles as needed. Also, the jira rules template that has been applied for the project will be relevant. Some projects allow

Re: Issue Tracker not available

2016-01-19 Thread Gino Bustelo
Seems like all 'closed' issues are now 'closed' Jira but are marked 'Unresolved' On Tue, Jan 19, 2016 at 11:39 AM, Gino Bustelo wrote: > Mine is lbustelo > > On Tue, Jan 19, 2016 at 11:04 AM, Chip Senkbeil > wrote: > >> My jira id is senkwich. Please

Re: Issue Tracker not available

2016-01-19 Thread Chip Senkbeil
Oh, I assumed you had all of the usernames for pmc members since they were supposed to email you their IDs, right? Would it make sense to list them here? Or for each of us to comment on the JIRA itself? I've been getting emails when others got their accounts set up and the only one I haven't seen

Re: Issue Tracker not available

2016-01-19 Thread Luciano Resende
On Tuesday, January 19, 2016, Chip Senkbeil wrote: > Oh, I assumed you had all of the usernames for pmc members since they were > supposed to email you their IDs, right? Would it make sense to list them > here? Or for each of us to comment on the JIRA itself? > > The

Re: Issue Tracker not available

2016-01-19 Thread Corey Stubbs
Luciano, My jira id is Lull3rSkat3r. Please add me to jira. On Tue, Jan 19, 2016 at 9:01 AM Luciano Resende wrote: > On Tuesday, January 19, 2016, Chip Senkbeil > wrote: > > > Oh, I assumed you had all of the usernames for pmc members since they >

Re: Issue Tracker not available

2016-01-19 Thread Chip Senkbeil
My jira id is senkwich. Please add me (Chip Senkbeil) as well. On Tue, Jan 19, 2016 at 9:01 AM Luciano Resende wrote: > On Tuesday, January 19, 2016, Chip Senkbeil > wrote: > > > Oh, I assumed you had all of the usernames for pmc members since

Re: Issue Tracker not available

2016-01-19 Thread Gino Bustelo
Mine is lbustelo On Tue, Jan 19, 2016 at 11:04 AM, Chip Senkbeil wrote: > My jira id is senkwich. Please add me (Chip Senkbeil) as well. > > On Tue, Jan 19, 2016 at 9:01 AM Luciano Resende > wrote: > > > On Tuesday, January 19, 2016, Chip Senkbeil

Re: Issue Tracker not available

2016-01-18 Thread Chip Senkbeil
t; > beginning. > > > > > > > > > > > > On Wed, Jan 13, 2016 at 8:55 AM Gino Bustelo <g...@bustelos.com> > > > > wrote: > > > > > > > > > > > >> Do we want all the Issues from Github ported or no? > > > > > >> >

Re: Issue Tracker not available

2016-01-18 Thread Corey Stubbs
help. Going back > and > > > > > closing > > > > > > > ones we don't need is a lot easier than selectively picking > them > > at > > > > the > > > > > > > beginning. > > > > > > > &

Re: Issue Tracker not available

2016-01-15 Thread Gino Bustelo
ll the Issues from Github ported or no? > > > >> > > > >> @lresende hinted of a tool Apache has to port Issues into JIRA. I > > > mentioned > > > >> to him that if it was easy, than then porting the issues would be > good > > > and > > >