Hi,
Am Feb 23, 2011 um 2:10 AM schrieb Dirk Reiners <dirk.rein...@gmail.com>:
>
> Hi All,
>
> On 02/22/2011 08:55 AM, Michael Raab wrote:
>> Hi,
>>
>> two questions on that issue:
>>
>> 1.) What is planned to be final solution for the 1.8 repository? SVN?
>> 2.) Is there an estimate when this solution could be ready?
>
> Given that SF supports a lot more VCSs and in general seems to be much more
> active now there is very little reason to run our own server for this. Now
> the question is what to use. A bunch of people on the project use (and
> apparently like) git, mostly using github for their work, so git is probably
> the preferred system. SF would serve as the master/stable repository, work
> repos would be on github.
>
> So here's my proposal:
>
> - Migrate SF CVS to SF GIT as a OpenSG_1 repository. I have a cvs2git.options
> file attached that I tried and the results seem ok to me. I would need input
> from anybody that has committed to OpenSG 1 if they're ok with putting their
> name/email (and which one) into this. I extracted the following list from CVS:
>
>
> If you are on this list and want to have an email in the conversion, please
> let me know privately. If you don't want your name in here please let me
> know, too, and I will use the CVS Unix name.
>
> - Migrate the OpenSG.org SVN to SF GIT as OpenSG_2 repository. I know Gerrit
> has a live link between his git and svn, so that should be easy to do.
> - Turn off SVN and CVS on SF, and the SVN on opensg.org, make SF GIT the
> official repo.
>
hmm, while I like git for my local work I still would prefer a central
repository that ensures
a linear history where the history can not be changed easily. I still run this
combination
locally for repositories where groups of people can commit to.
I feel that one has to change the workflow when transitioning to git and adapt
to the multi-repository model with a very limited set of comitters for a single
repository
and pulls between repositories or patches per mail as the norm.
Just replacing svn by git and go on like before does not seem to be the best
approach to me.
IMHO we need to put in a little more thinking about how we want to have the
workflow
before switching to git.
just my 0.02€
kind regards
gerrit
------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in
Real-Time with Splunk. Collect, index and harness all the fast moving IT data
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business
insights. http://p.sf.net/sfu/splunk-dev2dev
_______________________________________________
Opensg-users mailing list
Opensg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensg-users
