from Colin Finck:

> Let me give a public update about our Git Migration Decisions after the last
> meeting:

> * The migration of our SVN repository "reactos" is going to happen in
> September/October.

> * https://github.com/reactos/reactos will become our master repository as we
> want to take advantage of GitHub's Pull Request features.
> This means, all developers must register for GitHub accounts now.

> * git.reactos.org will remain as a replication slave. If we ever have severe
> problems with GitHub, we can switch back to a self-hosted Git in no time.

> * We will enforce a linear history in the "master" branch through server-side
> GitHub settings. You may create and push as many branches as you want and do
> whatever you want there, but when you want to commit the changes back to
> "master", you can only do so over a "git rebase".

> * BuildBot builds will get a naming scheme like:

>     reactos-bootcd-0.4.7-dev+344-5f3c53e2a-gcc.7z

>   That means 344 commits after the tag "0.4.7-dev" has been created, with this
> particular commit having the short hash "5f3c53e2a".
> Whenever we branch for a release like "0.4.6", we will now not just create the
> branch, but also tag "master" with "0.4.7-dev" to make this naming scheme
> possible.


> More newsletters like this may follow when I have more information to share or
> get the impression that some decisions haven't reached all developers yet.

Is there a convenient way to migrate an svn tree to git, or would it be necessary to git-clone to a separate tree?

Will the boot CD images be in 7z (p7zip) format:

What has kept me from trying ReactOS is not having a place to put it, considering ReactOS does not successfully boot from USB.

My hard drives are partitioned GPT.

Tom

_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev