Thanks for expediting this David, it is much appreciated. - Ian
On Thu, Jul 23, 2015 at 10:02 PM, David Nalley <[email protected]> wrote: > We'll have Infra folks looking at this tomorrow, and at least some > forward progress. > > Thanks, > > --David > > On Fri, Jul 24, 2015 at 12:57 AM, Mike Carey <[email protected]> wrote: >> Just to add a quick thought: We have been watching and indirectly trying to >> learn from the Apache Ignite discussion, and it seems really important that >> we have the JIRA system available for tracking our feature requests, bug >> fixes, etc. We don't want to start using the Apache system until we have >> initialized it with the Google code issues (which we continue to use in the >> meantime for lack of an alternative). PLEASE HELP! We would love to shut >> down the old system and start using the new system - but we can't get seem >> to the new one off the ground... :-( >> >> On 7/23/15 6:20 PM, Ian Maxon wrote: >>> >>> Hi, >>> >>> As part of the migration to ASF infrastructure, AsterixDB has been >>> migrating off of our old issue tracker (Google Code) to ASF's JIRA >>> instance. It seems lately that the process has become stuck though. >>> There have been a few JIRAs filed about this already (from most recent >>> to oldest): >>> >>> https://issues.apache.org/jira/browse/INFRA-9954 >>> https://issues.apache.org/jira/browse/INFRA-9621 >>> https://issues.apache.org/jira/browse/INFRA-9352 >>> >>> However none of them seem to have made much progress. Time is becoming >>> a constricting factor now, because Google Code is shutting down soon >>> (going read-only in August). If the migration isn't complete soon, I >>> am not sure where new issues will be filed. >>> >>> Is there anything that can be done to move this process forward? I >>> believe the issues are in a format (attached to the most recent issue) >>> that should be importable into JIRA directly now, but I don't have a >>> way to test this directly. Any assistance would be much appreciated. >>> >>> Thanks! >>> >>> - Ian >> >>
