[mdt-ocl.dev] GIT Practice

[Ed Willink <ed@xxxxxxxxxxxxx>]

Hi

Branch names
-------------------

Axel has used bugs/nnnn. I've used bug/nnn. We need to standardize. I 
thought one of the GIT tutorials had a recommendation but can't find it.

Presumably the branches get renamed/deleted after push otherwise the 
remote tracking will become unmanageable.
Should we rename historic branches to have hierarchy: e.g. maintenance/3.0?

Bugzilla status
--------------------

I think anyone can commit to a bug branch at any time. Eventually the 
bug branch is submitted for review as a result of which +1's authorize 
push to master and consequently RESOLVED. cf 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=348504 where my +1 seems 
to have been interpreted as commit to bug branch which then got a 
RESOLVED without a push to master.

SSH keys
-----------

Axel: I'm waiting for clarification on what keys you want me to put where.

Size
-----

I'm already finding GIT incredibly slow. The tutorials recommend small 
repositories. I'm wondering if we should be partitioning.

Working Directory
-------------------------

EGIT seems to create a Working Directory and Eclipse seems to use it for 
Import Projects, which puzzles me as regards switching branches. I 
expect my Workspace files to be extra-repository, whereas GIT seems to 
have them 'inside'. Has GIT/me done something stupid?

    Regards

        Ed