git-gui i18n / 0.9.x plans

Now that git-gui 0.8.0 has been released I have updated both the maint and master branches to 0.8.0. maint will carry the 0.8.0 development forward, and is strictly for bug fixes to the current non-i18n codebase. I'm unlikely to make changes here except to address current critical issues.

Regarding future development for the off-in-the-future 0.9.0 release I'd like to see the i18n work merge in before we do anything else major to git-gui. I'm likely to shift my focus to fast-import this week, which means git-gui will probably see no major activity from me for about the next two weeks. As soon as the i18n team has something rebased onto current master that is ready for merging, I'll bring it over. Yes, that's a promise on my part to try and keep my tree frozen for a little while. :)

Other things I'd like to do in 0.9.0, but may or may not actually do myself:

 - Automatically refetch tracking branches in merge
 - Text mode log viewer:
   `git-log`, `git-log -g`
 - File monitor on WinNT (to avoid costly Rescan on large projects)
 - Remove more porcelain shell dependencies:
   `git-merge`, `git-repack`, `git-remote prune`
 - UI for cherry-pick/revert
 - Generational GC for 'Compress Database'
 - Integration with git-stash
 - Hunk splitting/selection
 - UI for git-tag
 - Push specific tags by name (rather than by --tags)
 - Pull from arbitrary URL/branch pair

Those are roughly ordered by how much I think myself and my fellow day-job coworkers want these features, so that's probably roughly the order I'll try to work through them after the i18n current changes are merged in. Of course patches are also welcome. :)

I haven't yet settled on whether the first i18n enabled version would be 0.9.0 or a 0.8.1/2. That's one reason why I want to get the i18n changes merged early. If we have a few high quality translations ready to go I'd rather ship them in a 0.8.x maint release than hang onto them for another 1-2 months while the major features of the 0.9.0 release get worked on and stablized.