Another, less painful approach might be to write a little program that imports into JIRA from the CSV file. Not sure if the JIRA REST API is enabled or not, though.
On Thu, Jan 30, 2014 at 1:11 PM, Andrew Purtell <[email protected]> wrote: > Didn't mean to imply that would gate the release. > > In the absence of a JIRA issue import, I am willing to volunteer to bring > over all of the open issues as in at least filing new JIRAs with the > initial post of the GH issue. Deeply suboptimal, I know, but anyway. > > I'm not sure on the status of INFRA exactly. I believe the Foundation pays > a salary for ops based on the yearly reports I have seen, implying > employment. However most Foundation functions are indeed performed by > volunteers (the board, legal affairs, project management, ...). > > > On Wed, Jan 29, 2014 at 4:14 PM, James Taylor <[email protected] > >wrote: > > > Yes, true, but I don't think that's a gating factor for us releasing. I > > think we should bring it up in our report, though. You guys would have a > > much better perspective, but it seems like there's a need for more folks > in > > INFRA (says the newbie :-) ). All the INFRA folks are just volunteering > > their time? That's extremely generous of them, if that's the case, but is > > that a sustainable model for Apache? > > > > > > On Wed, Jan 29, 2014 at 4:06 PM, Andrew Purtell <[email protected]> > > wrote: > > > > > The JIRA issue import also hasn't happened yet. > > > > > > > > > On Wed, Jan 29, 2014 at 2:42 PM, James Taylor <[email protected] > > > >wrote: > > > > > > > Waiting on two things for a potential release: > > > > - software grant paperwork from Salesforce. Hopefully by Fri, but may > > > slip > > > > to next week as it EOY for us so legal is busy. > > > > - determination of whether we can keep our name as "Apache Phoenix", > as > > > I'd > > > > like to do releases under our permanent name. I don't know how long > or > > > when > > > > this will happen. > > > > > > > > We're ready with the software, though - it's sitting in a 2.2.3 > branch > > in > > > > our Apache git repo... > > > > > > > > James > > > > > > > > > > > > On Wed, Jan 29, 2014 at 9:26 AM, Stack <[email protected]> wrote: > > > > > > > > > Lets be on top of it this time (smile). Any sign of a release soon > > out > > > > of > > > > > incubator? > > > > > St.Ack > > > > > > > > > > > > > > > On Wed, Jan 29, 2014 at 6:15 AM, Marvin <[email protected]> > wrote: > > > > > > > > > > > > > > > > > > > > > > > Dear podling, > > > > > > > > > > > > This email was sent by an automated system on behalf of the > Apache > > > > > > Incubator PMC. > > > > > > It is an initial reminder to give you plenty of time to prepare > > your > > > > > > quarterly > > > > > > board report. > > > > > > > > > > > > The board meeting is scheduled for Wed, 19 February 2014, > > 10:30:30:00 > > > > > PST. > > > > > > The report > > > > > > for your podling will form a part of the Incubator PMC report. > The > > > > > > Incubator PMC > > > > > > requires your report to be submitted 2 weeks before the board > > > meeting, > > > > to > > > > > > allow > > > > > > sufficient time for review and submission (Wed, Feb 5th). > > > > > > > > > > > > Please submit your report with sufficient time to allow the > > incubator > > > > > PMC, > > > > > > and > > > > > > subsequently board members to review and digest. Again, the very > > > latest > > > > > you > > > > > > should submit your report is 2 weeks prior to the board meeting. > > > > > > > > > > > > Thanks, > > > > > > > > > > > > The Apache Incubator PMC > > > > > > > > > > > > Submitting your Report > > > > > > ---------------------- > > > > > > > > > > > > Your report should contain the following: > > > > > > > > > > > > * Your project name > > > > > > * A brief description of your project, which assumes no > knowledge > > of > > > > the > > > > > > project > > > > > > or necessarily of its field > > > > > > * A list of the three most important issues to address in the > move > > > > > towards > > > > > > graduation. > > > > > > * Any issues that the Incubator PMC or ASF Board might wish/need > > to > > > be > > > > > > aware of > > > > > > * How has the community developed since the last report > > > > > > * How has the project developed since the last report. > > > > > > > > > > > > This should be appended to the Incubator Wiki page at: > > > > > > > > > > > > http://wiki.apache.org/incubator/February2014 > > > > > > > > > > > > Note: This manually populated. You may need to wait a little > before > > > > this > > > > > > page is > > > > > > created from a template. > > > > > > > > > > > > Mentors > > > > > > ------- > > > > > > Mentors should review reports for their project(s) and sign them > > off > > > on > > > > > the > > > > > > Incubator wiki page. Signing off reports shows that you are > > following > > > > the > > > > > > project - projects that are not signed may raise alarms for the > > > > Incubator > > > > > > PMC. > > > > > > > > > > > > Incubator PMC > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Best regards, > > > > > > - Andy > > > > > > Problems worthy of attack prove their worth by hitting back. - Piet > Hein > > > (via Tom White) > > > > > > > > > -- > Best regards, > > - Andy > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > (via Tom White) >
