Last updated October 7, 2011.
Phase 3 of the Git migration is really more accurately referred to as 'phase next': anything and everything that didn't fall under the umbrella of "directly porting existing CVS-based features to Git" was relegated to Phase 3. Now that Phase 2, the actual migration, is finished, we are revisiting the Phase 3 feature list to decide just what we actually want done, and what order we want it done in.
See the video of DrupalCon Chicago 2011 presentation Git Phase Next: The Promised Land for a general idea of Git phase 3.
===========
Key changes for phase 3
- #714102: Decide on the possible ways to contribute to an issue with git
- #720700: Come up with an update hook to mitigate abuse of sandboxes
- #713102: Host sandbox Git repositories for any user who wants one
- #1077884: Allow the deletion of sandbox projects
Other feature ideas
Better issue/commit integration
- Block of "All commits that reference this issue" that shows up on issue nodes (TODO)
- Generalizing "project maintainer" for issue assignment within project (not just CVS access anymore)
List of all projects a user has Commit access to
- This doesn't exist yet, but it'd be nice to add while we're thinking about VCS integration
- E.g. another tab at http://drupal.org/project/user or something
- #101341: 'My projects' should also display projects that are being co-maintained
Stronger checks and sanity checking on commit messages
- Basing lots of stats on this
- Maybe it's worth doing more sanity checks to validate that the message is valid
- Proper sign-offs on core commits