On Thu, Aug 30, 2012 at 12:10 PM, Michael A. Labriola < labri...@digitalprimates.net> wrote:
> >That would probably save one migration, otherwise you'll have to migrate > to SVN and then to Git again, sounds like a pain... > > I am mostly concerned about losing the history and the GIT to SVN > migration seems to only keep some limited history. > I get the concern, it'd be nice to keep all the Git history. I didn't make a ticket for switching to read/write Apache Git because I am not proficient in Python and so I can not help Apache Infra with asfgit-admin (I believe that's what they need help with). I submitted the ticket to create new Git mirrors based on the SVN restructure so we can at least get those up and figure out a GitHub -> SVN workflow while read/write Apache Git gets going. Some info I think Dave posted made it seem to me like helping with Python coding wasn't actually a requirement, but I am still unsure so I haven't created a ticket for Read/Write Apache Git for Apache Flex yet. Not sure how long we want to wait before we try to do that? -omar
