Om, Those emails hardly give a reliable time table...
One of the reasons this sudden move frustrates me so endlessly is that I literally was ready to commit the FlexJS in FalconJx code this morning and move on to actual payed work. Instead I ended up spending my day trying to figure out git (and in the process be amazed by how many problems this will introduce and how few problems - if any - it will solve) and trying to prepare for my first commit/push/rebase/branch. I'll shut up now, as everyone else seems very happy with their new toy. EdB On Tue, Mar 12, 2013 at 7:37 PM, Om <bigosma...@gmail.com> wrote: >> >> And more importantly: I don't see what this does for the project that >> needed to >> be done so desperately that we couldn't get a couple of days advance >> warning so we could at least commit our outstanding changes and finish >> the release(s) that were in progress? >> >> > Who is this question directed towards? You should probably talk to INFRA > about the timing. The Flex PMC has no control over when these things > happen. The ticket was open for 6 months. We did have a few emails in the > past few weeks about this impending migration [1], [2] > > Thanks, > Om > > [1] http://markmail.org/message/vyzzbumvwfcyzey2 > [2] http://markmail.org/message/h7licye6pw4qnrbv > > > >> >> >> On Tue, Mar 12, 2013 at 3:50 PM, Michael A. Labriola >> <labri...@digitalprimates.net> wrote: >> > Erik, >> > >> >>What advantage is having a local repo to having a local working copy? >> >>It seems to me that all it does is add an extra layer between me and my >> co-contributors. I need to 'commit' to my local repo and then 'push' to get >> it out to the world, where before only a >'commit' was needed... >> > >> > It will seem that way at first. Don't expect your first couple of weeks >> to be happy, but I promise it gets better. The big advantage is having >> local branching, roll back, staging and the ability to work completely >> offline. The thing is that it's a totally different workflow so it's hard >> to compare git versus svn accurately. >> > >> > My git workflow is constant committing and branching locally (all of >> which are nearly 0 overhead in git). It allows me to task switch very >> easily, to try things out and roll back when they don't work. I can be in >> the middle of a task, stash the half-baked code, switch over to do a bug >> fix, and then switch back and resume my state. >> > >> > I make potentially dozens if not hundreds of branches in the course of a >> day when I am really coding. Out of all of those branches and commits, I >> perhaps push 1 or 2 up to the outside world. Its more about local code >> organization and local workspace management and then sharing the daily or >> hourly results of those efforts. >> > >> > I can promise this will suck for you at first. You are asking all of the >> question I did and I frankly hated git and was frustrated with it for >> weeks. Now I strongly dislike when someone makes me use SVN. It feels >> clunky and inelegant. >> > >> > Mike >> > >> >> >> >> -- >> Ix Multimedia Software >> >> Jan Luykenstraat 27 >> 3521 VB Utrecht >> >> T. 06-51952295 >> I. www.ixsoftware.nl >> -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
