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 mailing list that makes more sense? I'm assuming that all of the PMC members for Toree would be project admins for the jira project, right? Did you want us to comment individually, or were you going to submit a list like was asked in the jira? On Mon, Jan 18, 2016 at 12:59 AM Luciano Resende <luckbr1...@gmail.com> wrote: > 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 <g...@bustelos.com> wrote: > > > @lresende Awesome, Thanks! > > > > On Thu, Jan 14, 2016 at 3:22 PM, Luciano Resende <luckbr1...@gmail.com> > > 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 < > chip.senkb...@gmail.com > > > > > > wrote: > > > > > > > Thanks for the tip, Hitesh! > > > > > > > > On Wed, Jan 13, 2016 at 12:55 PM Hitesh Shah <hit...@apache.org> > > 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/jira/browse/INFRA-10144 ) but that was > > from > > > > > their own atlassian instance. > > > > > > > > > > — Hitesh > > > > > > > > > > On Jan 13, 2016, at 6:58 AM, Chip Senkbeil < > chip.senkb...@gmail.com> > > > > > wrote: > > > > > > > > > > > +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 <g...@bustelos.com> > > > > wrote: > > > > > > > > > > > >> 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, Chip Senkbeil < > > > > chip.senkb...@gmail.com > > > > > > > > > > > >> wrote: > > > > > >> > > > > > >>> 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. > > > > > >>> > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Luciano Resende > > > http://people.apache.org/~lresende > > > http://twitter.com/lresende1975 > > > http://lresende.blogspot.com/ > > > > > > > > > -- > Luciano Resende > http://people.apache.org/~lresende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/ >
