from my perspective: as soon as possible.
One less tool for people to learn.
A switch like this has _potentially_ unlimited side-effects. So as
soon as you start thinking about the risk of delaying software
releases that's just another way of saying you will never switch.
I would switch as fast as is technically possible.
Wolfgang
On May 12, 2008, at 4:20 PM, Graeme Gregory wrote:
Ok, this has been talked about internally for a while and the decision
has been made by majority that OM repo should change to GIT.
The only thing left to organise is the timetable of this event. We
need
to make sure that we can do it and iron out the wrinkles without
delaying any vital software releases.
One thing I would like to say is I think this is seperate issue from
any
SCM switch that is currently discussed on OE lists. We would not be
the first vendor to keep our local OE tree in a different SCM than
upstream as Poky Linux already does this.
I also think that compared to OE OMs usecase is a lot more limited. We
currently only have 4-5 keys enabled for write to our repo. And all
keys
are employees. So we dont have the problems OE has with traceability.
Anyway guys please comment, I would like to get this timetabled ASAP.
Graeme
