https://wiki.blender.jp/index.php?action=history&feed=atom&title=Dev%3ARef%2FProposals%2FMigration_to_Git_Phabricator 2026-06-08T20:28:36Z このウィキのこのページに関する変更履歴 MediaWiki 1.31.0 https://wiki.blender.jp/index.php?title=Dev:Ref/Proposals/Migration_to_Git_Phabricator&diff=143923&oldid=prev 2018-06-28T21:04:39Z

<p>1版 をインポートしました</p> <table class="diff diff-contentalign-left" data-mw="interface"> <tr class="diff-title" lang="ja"> <td colspan="1" style="background-color: #fff; color: #222; text-align: center;">← 古い版</td> <td colspan="1" style="background-color: #fff; color: #222; text-align: center;">2018年6月28日 (木) 21:04時点における版</td> </tr><tr><td colspan="2" class="diff-notice" lang="ja"><div class="mw-diff-empty">(相違点なし)</div> </td></tr></table>

Yamyam https://wiki.blender.jp/index.php?title=Dev:Ref/Proposals/Migration_to_Git_Phabricator&diff=143922&oldid=prev 2013-11-19T15:01:35Z

<p></p> <p><b>新規ページ</b></p><div>= Migration to Git and Phabricator =<br /> <br /> == Plan ==<br /> <br /> We intend have migrated from Subversion to Git for Blender code, and from GForge to Phabricator for bugs and code review.<br /> <br /> Most of the core Blender developers prefer working with Git, and have already been using it with git-svn and in various external repositories. It makes sense to switch the main repository to Git then as well, so that we have a common base to merge patches and branches onto.<br /> <br /> Phabricator will give us a centralized place to do code reviews and audits, integrated with bug reports and patch submissions. Currently there isn't a single mechanism and there are too many steps, with phabricator we can send code for review, and later merge it when approved with a single command, automatically closing associated tasks and bugs. Phabricator should also make it easier to do task management for modules, releases and user interface design.<br /> <br /> We will host development infrastructure on our own servers, so that we can keep it under our control and customize where needed.<br /> <br /> ==== Goals ====<br /> <br /> * Make using Git easier for developers<br /> * Make code reviews centralized and efficient for developers<br /> * Try to lower barrier to entry for new developers<br /> * Use trackers for UI design and task management, not only bugs<br /> * Create developer website that truly reflects project organization<br /> <br /> == Questions ==<br /> <br /> ====== What about an official github or gitorious mirror? ======<br /> We think this would be useful, but have not yet decided how or if this will work, it can be looked at after our own repository is up and running well.<br /> <br /> ====== Would we accept pull requests from github or similar on such a mirror?======<br /> We want to keep the threshold for new developers low, however doing this would make things somewhat complicated for us (syncing, duplicate issues/tasks, ..), it would be simpler if everything went through phabricator. We may at some point experiment with this or figure out a way to make submitting patches from such git hosts easier.<br /> <br /> ====== What will be the branching workflow? ======<br /> We did not decide on a clear answer to this yet, there are a few options:<br /> * Let developers push branches to main repository on git.blender.org<br /> * Let developers push branches to some experimental repository on git.blender.org<br /> * Developers have own git repositories on some git host<br /> * Developers have local branches<br /> <br /> Probably it will be a combination of these, but we need to agree on some guidelines.<br /> <br /> ====== What about the lib/ directory with precompiled libraries? ======<br /> This will stay in subversion for now, because git is not efficient at storing binary file differences, and this would make the repositories very large to check out.</div>

wiki>Brecht