Hi,
After our last
meeting discussion about GIT we began to discuss
internally about migrating Papyrus repository to
GIT.
We think it is
a good idea to do it ASAP while we are reworking
the global architecture, while perhaps wait for
the SR2 release so we don’t break any
build-related stuff just before the release.
The current
work will not be lost since we can keep the
history when migrating from SVN to GIT.
As you know GIT
has a very different philosophy than SVN and we
can’t “copy-paste” the usual SVN process if we
want to be able to take advantage of all the GIT
features.
We are willing
to evaluate the tools and find a good methodology
before switching and we will work on that during
January.
We tried to use GIT on an other
eclipse project and it appears eGIT doesn’t seem
mature enough to be used: we had several cases of
“detached HEAD” that were surely caused by wrong
methodology, but eGIT doesn’t help either since we
ran into less trouble using TortoiseGIT.
The other project was still
“patch-based” so we didn’t go as far as using a
reviewing tool as Gerrit but it would be cool to
have it.
Any insight /
GIT feedback is welcome.
Thanks,
Mathieu Velten
Raphael Faudou
Tristan Faure
Arthur Daussy
Ce message et les pièces jointes sont
confidentiels et réservés à l'usage exclusif de ses
destinataires. Il peut également être protégé par le
secret professionnel. Si vous recevez ce message par
erreur, merci d'en avertir immédiatement l'expéditeur et
de le détruire. L'intégrité du message ne pouvant être
assurée sur Internet, la responsabilité du groupe Atos
ne pourra être engagée quant au contenu de ce message.
Bien que les meilleurs efforts soient faits pour
maintenir cette transmission exempte de tout virus,
l'expéditeur ne donne aucune garantie à cet égard et sa
responsabilité ne saurait être engagée pour tout dommage
résultant d'un virus transmis.
This e-mail and the documents attached are confidential
and intended solely for the addressee; it may also be
privileged. If you receive this e-mail in error, please
notify the sender immediately and destroy it. As its
integrity cannot be secured on the Internet, the Atos
group liability cannot be triggered for the message
content. Although the sender endeavors to maintain a
computer virus-free network, the sender does not warrant
that this transmission is virus-free and will not be
liable for any damages resulting from any virus
transmitted.
