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 Shah wrote: > > > @G

Re: Issue Tracker not available

2016-01-25 Thread Gino Bustelo
@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 Shah wrote: > @Gino, agreed. I was just pointing out that it would be good to come up > with a list of a few people/volunteers from the PPMC and add all of them as > a

Re: Issue Tracker not available

2016-01-25 Thread Hitesh Shah
@Gino, agreed. I was just pointing out that it would be good to come up with a list of a few people/volunteers from the PPMC and add all of them as admins for the Toree jira project. thanks — Hitesh On Jan 25, 2016, at 7:00 AM, Gino Bustelo wrote: > @hitesh I'm assuming that we need @lresend

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 the toree project >

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 contrib

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 wrote: > >> Mine is lbustelo >> >> O

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 add me (Chip Senkbeil) as well. >> >> On Tue

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 > > wrote: > > > > > Oh, I assumed you had all

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 they > were > > supposed to email you their IDs, ri

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 > were > > supposed to email you their IDs, right

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 jira id is not the same as ap

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-18 Thread Luciano Resende
On Mon, Jan 18, 2016 at 7:58 AM, Chip Senkbeil wrote: > > Were we planning to use the dev mailing list as the destination for jira > notifications? Or is there some other mailing list that makes more sense? > > Do we want to create an issues list ? Otherwise dev will be. -- Luciano Resende ht

Re: Issue Tracker not available

2016-01-18 Thread Luciano Resende
On Mon, Jan 18, 2016 at 12:31 PM, Corey Stubbs wrote: > Everything seems to have imported correctly. And +1 on all PMC members > should have access to the project JIRA. > > I would need the jira username for the pmc members in the jira. -- Luciano Resende http://people.apache.org/~lresende htt

Re: Issue Tracker not available

2016-01-18 Thread Corey Stubbs
Everything seems to have imported correctly. And +1 on all PMC members should have access to the project JIRA. On Mon, Jan 18, 2016 at 9:58 AM Chip Senkbeil wrote: > What feedback were you wanting on the infrastructure jira? It looks like > the issues imported fine, although I'm wondering how we

Re: Issue Tracker not available

2016-01-18 Thread Chip Senkbeil
What feedback were you wanting on the infrastructure jira? It looks like the issues imported fine, although I'm wondering how we link ourselves to the existing comments under our names. Were we planning to use the dev mailing list as the destination for jira notifications? Or is there some other m

Re: Issue Tracker not available

2016-01-17 Thread Luciano Resende
Could you please review https://issues.apache.org/jira/browse/TOREE And provide feedback on https://issues.apache.org/jira/browse/INFRA-11082 Note that the jira has some questions on the last comment from Gavin. Thanks On Fri, Jan 15, 2016 at 7:00 AM, Gino Bustelo wrote: > @lresende Awesom

Re: Issue Tracker not available

2016-01-15 Thread Gino Bustelo
@lresende Awesome, Thanks! On Thu, Jan 14, 2016 at 3:22 PM, Luciano Resende wrote: > Created task for creating Toree jira and importing issues from Github > > https://issues.apache.org/jira/browse/INFRA-11082 > > On Wed, Jan 13, 2016 at 12:16 PM, Chip Senkbeil > wrote: > > > Thanks for the tip,

Re: Issue Tracker not available

2016-01-14 Thread Luciano Resende
Created task for creating Toree jira and importing issues from Github https://issues.apache.org/jira/browse/INFRA-11082 On Wed, Jan 13, 2016 at 12:16 PM, Chip Senkbeil wrote: > Thanks for the tip, Hitesh! > > On Wed, Jan 13, 2016 at 12:55 PM Hitesh Shah wrote: > > > I believe the INFRA folks m

Re: Issue Tracker not available

2016-01-13 Thread Chip Senkbeil
Thanks for the tip, Hitesh! On Wed, Jan 13, 2016 at 12:55 PM Hitesh Shah wrote: > I believe the INFRA folks may have tools to do the import. A jira can be > filed against INFRA to get some help in this regard. > > The Apex folks went through a complex import earlier ( > https://issues.apache.org

Re: Issue Tracker not available

2016-01-13 Thread Hitesh Shah
I believe the INFRA folks may have tools to do the import. A jira can be filed against INFRA to get some help in this regard. The Apex folks went through a complex import earlier ( https://issues.apache.org/jira/browse/INFRA-10144 ) but that was from their own atlassian instance. — Hitesh O

Re: Issue Tracker not available

2016-01-13 Thread Chip Senkbeil
+1 to that. Any automation would be a great help. Going back and closing ones we don't need is a lot easier than selectively picking them at the beginning. On Wed, Jan 13, 2016 at 8:55 AM Gino Bustelo wrote: > Do we want all the Issues from Github ported or no? > > @lresende hinted of a tool Apa

Re: Issue Tracker not available

2016-01-13 Thread Gino Bustelo
Do we want all 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 we would then go through them and clean them up. Thoughts? On Wed, Jan 13, 2016 at 8:30 AM,

Issue Tracker not available

2016-01-13 Thread Chip Senkbeil
Is there a timeline for when the issue tracker will be available for Toree? Is there something we haven't done yet? Currently, https://issues.apache.org/jira/browse/TOREE gives me a "Project does not exist" message.