I don't have any experience using git but from what I've read it sounds
like it could help our community.
In an ideal world, our release process should not involve 10+ release
candidates and a QA process spread over many months, but since we don't
live in this world should we consider moving to git? The main issue is
that we can't/shouldn't put a code freeze on trunk as we fix bugs on our
1.1.x and 1.2.x branches, but merging fixes back into trunk has become a
challenge. As time passes our branches and trunk grow significantly out
of sync. There are fixes in 1.1.x that had never made their way back
into trunk, and it is likely that additional fixes in other branches
will fall through the cracks as we proceed.
This is by no means a criticism, as many open source projects
continually struggle with these same issues. I don't necessarily think
we should go this route as it is difficult to shift developer practices
and apply an administrative process around a new repo approach. I guess
this is more of a request for proposals rather than an actual proposal
because I haven't used git and can't make a confident
recommendation/comparison. I've pinged some of my colleagues from Sakai
OAE in case they want to chime in, as they had decided to move from svn
to git. Thoughts/Comments are welcome by all.
~Adam
P.S. jira studio's apps support github so it should provide the same
niceties we get from svn.
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
