I have created intrepid personal package archive repository at ubuntu launchpad. Now you can install teamgit 0.0.4 using apt system on intrepid.
Head on to teamgit/download for instructions.

Just for fun i removed kpty (this was the only bit which was guaranteed not to work with win32.
And downloaded and compiled it on qt4.4.3-win32-mingw.
Fired it up :o !! i saw the ui... well not too much surprise there, its qt after all,
But then gave it path for msysgit binary and that worked as well.... Hurra!!!
Tested setting up user name/email, works. Tested with teamgit repo almost everything i tried worked.
Tested 'send patch by email', heck it even fired up outlook express.

Damn QT is the best toolkit i have used ever.
Patches are upstream, you can compile current teamgit on windows

I tagged the repo as v0.0.4

Here are changes since v0.0.3
Abhijit Bhopatkar (36):
      Added .desktop file and icons to install target
      Added support files for running checkinstall
      Don't depend on qt 4.4.1 we can do with just 4.4
      Changed the signoff check box label
      Added auto "add sign off line" to commit
      Added auto sign off option to general settings
      Added auto sign off option in settings
      Change libqt-core to libqtcore4 for intrepid in checkinstall script
      Make default new project directory ~/linux-2.6
      Add base dir selection for new project dialog
      Current project is no longer used
      Add base dir selection to the new projects dialog
      Fix new project stuff to open up correct repo after clone
      Cleaned up icons directory
      Removed unneeded icon pngs
      Qdevelop cleaned up the project fine
      Added git blam support to backend gitprocess
      Added file annotation support with commit search
      Make sure first column is visible when searching
      Scrool annotation text box to top after receiving annotaion
      Cleanup: we no longer use mutex
      Bring annotated file to front when received
      FIX: Open dialog failed to refresh the UI
      Added apply mailbox function to git process backend
      Added support to push to a selected remote
      Removed an uneeded debug output message
      Added apply mail action in tools
      Added apply mail functionality
      Fix: apply mail didn't use the file provided in path and did nothing
      Fix: Make apply mail  actully store the last path for it to remember later
      Fix: apply mail did not refresh after operation completed
      Added send patch by email functionality
      Added send patch by mail in toolbar menu
      Activated send patch by mail menu action
      Added quit action to file menu and activated it
      teamGit will now print sha id of the selected commit while exiting to stdout

Horst H. von Brand (1):
      Fix typo in src/mainwindowimpl.cpp

Fedora seems to have picked up on teamgit announce,
that means a rpm for teamgit is ready
hopefully they can upgrade that fast when i announce 0.0.5 shortly.

Since i didn't get time to do proper docs yet i thought i will put very quick and dirty piece here to help testers make sense of teamgit.

Starting:
you can start teamgit from git repo and it will work with that,
you can change the repo from open command in file menu,
if working dir is not git repo it will fall back to last opened repo.

In general actions work on the selected item or don't do anything (i need to add helpfull messages here).
e.g.
checkout will checkout whatever is selected branch,tag or commit.
cherry-pick will try to pick whatever commit is selected,

to view log other than current log
just d-click  file to see log belonging to that file in current branch
d-click branch or tag to see log for those refs

if there are uncommited changes they will show up in unstaged files pane on left side,
click on file will show the diff
d-click hunk inside diff will stage that hunk for commit
d-click file will stage the file
d-click on staged hunk/file will unstage it.

once you'r happy with stagged stuff you can commit and enter commit message.

You can set your username/email in setting dialog that will be used by git (it changes global preferences for git)
Don't hesitate to mail me anything, even if its just plane teamgit sucks email.

to add new files click on show-untracked button and the pane will show all files not tracked by git in the directory.
d-click will stage the file for inclusion in next commit.

Just tagged the repo with v0.0.3 [github.org]
We are yet closer to milestone 1
Hope to finish all the stuff for m1 by v0.0.5

Also making a freshmeat announcement with this release, i think its ready for public consumption now. 

First few tests out in wild (with few friends and family) showed that i am such a pathetic ui designer.
I have delayed the release till i fix few of the obvious usability issues.
e.g. Making open button first one rather than new, since thats the one you should be using most often. Infact i will be moving "new" to tools rather than file.

I have decided to go ahead and announce teamgit to git mailing list without the rebase and merge support,

I will have to polish it a bit first and then announce it later this week.

Teamgit can now stage individual hunks,
This completes my original 1st milestone featurelist, but i have now added mergetool and rebase support to that list so its still a little while before i make a major release.

First teamgit release is approaching fast

I have added lots of features and i am using most of them so they are getting tested as well.
I did encounter few remote corner quirks, but couldn't reproduce them.

But its overall quite stable and does what is expected.
Few annoyances remain such as i can't select atag or branch without gathering a log for it. May be i should conver log gather to double click etc.

But on the whole its quite ready for release.
I will now add some documentation and do a stabilization run for one week.
Then after release, will go full swing again with feature adds.

No 1 item on wishlist: rebase support

I have just tagged the repo as v0.0.1

Now i can do basic commits from teamgit. The result is that now i put my main development teamgit repo under ~/teamgit and now manage teamgit from teamgit.

So now i will just start adding features as i need them while i work on it :D sort of cumulative explosion development process.

e.g. The first task i had to go to shell was tagging :D so next feature to add will be tagging support.