As you may have seen, TLF is ready for donation. Falcon will be next week.
Given that, I think there are two "vectors" here that can be worked on in parallel: 1) switching SVN usage to GBM and handling donations, and 2) Getting a read/write Git repo. It looks like there is a group of folks who are volunteering to work with Infra so hopefully they will organize and make (2) happen. Meanwhile, I think the rest of us can keep on using SVN. I don't think we need to hold off for Git. I think the steps are: (1) Rearrange SVN for new structure (2) Create "develop" branch in sdk/trunk/branches (3) Remove post-release commits from trunk and block the removal from merging to "develop" branch. (4) Start syncing and working from "develop" branch. (5) Fixes to mustella go into "develop" and get synced to trunk Thoughts? -Alex On 8/15/12 2:10 PM, "Alex Harui" <aha...@adobe.com> wrote: > > On 8/15/12 2:04 PM, "Dave Fisher" <dave2w...@comcast.net> wrote: > >> >> If this is how the project wishes to roll then I would suggest the following >> sequence assuming that Falcon is coming in a few days. > The VP that signs these things won't sign until Monday at the earliest. > > FWIW, I think there will be at least one more donation (3.x) that was in > Adobe SVN so keeping some sort of SVN around might be useful as a landing > point then transferring to Git. > > I was thinking that it will be a few days until we get Git up and running > even if we're very lucky so step 1.5 should be to create a develop branch in > SVN and have folks get working (and branching) in SVN until Git is up. > > >> >> (1) Rearrange the SVN Repository for the new structure. >> >> (2) Import Falcon into SVN. >> >> (3) INFRA JIRA request for Git in the current supported mode. Include the >> Flex >> Git volunteers along with the PPMC, Committer, and/or Contributor status for >> each. >> >> (4) Once the Git Mirrors are ready then let the pulls begin. >> >> (5) The Volunteers may help drive this to the desired, fully blessed, outcome >> faster, or they might not, only work and time will tell. (Contributors may >> very well earn enough merit for the PPMC to vote them Committer status.) >> >> BTW - There was an #asfinfra discussion about Apache Policy and enforcing no >> log history rewrites along with requiring a rebase this morning. Didn't >> follow >> it too closely, but the result was the closing of an INFRA JIRA. >> >> Regards, >> Dave >> >> >>> >>> >>> -- >>> Alex Harui >>> Flex SDK Team >>> Adobe Systems, Inc. >>> http://blogs.adobe.com/aharui >>> >> -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
