flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erik de Bruin <e...@ixsoftware.nl>
Subject Planning for Git
Date Thu, 22 Nov 2012 15:46:01 GMT
Since we can't indefinitely postpone the inevitable, I think we should
start to plan for the move to Git. I think at least these points
should be addressed (if they haven't already been, in which case they
should be documented such that they can be easily referenced, e.g. on
the Wiki):

1) once Git becomes available, does SVN become unavailable right away,
or will both repos be able to coexist for a while (both being able to
receive updates and updating the other when they do)?

2) several committers are "on loan" from Adobe for a very specific
goal (Peter and Gordon). Are they comfortable working with Git,
willing and able (in that they have enough time available to do so) to
learn Git, or would moving to Git mean that they are no longer able to

3) what workflow does the project use (reading about Git, it seems
like there are endless possibilities), do we need to vote on that and
how do we 'enforce' one over the other? Also, this workflow needs to
be embedded in all the READMEs and the website, just like the SVN
workflow is now.

4) some technical aspects of the project are tied to SVN, like the
website with it's post-commit hook to the 'buildbot'. These apparently
have to stay with SVN, fragmenting the development environment. Are
there alternatives that will allow these types of services to move
over to Git as well?

5) is anyone aware of any technical issues with the codebase that are
specifically tied to SVN that need changing when the move happens
(can't think of any, but better safe than sorry)

That's all I've got now, just thought we needed a starting point and
I'm hoping this will help provide one.


Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

View raw message