Wayne
Is it your recommendation that projects should not use a local
git depot, instead all should just use the Eclipse master git depot?
We had run into network and accessibility issue to the Eclipse
server in the past that causing delay of work and risking not meeting the simultaneous
release schedule. There were many times, developers can't do work for a
several hours to a couple of day. And there were one time when the whole team
was shut down for a week due to a undersea cable was cut between North America and
Asia.
One possible solution is for Eclipse foundation to create a distributed
git service around the world (using AWS?), it will allow committers to remove the
need of local gits.
For now, with distributed git, there is a question of how often
you push the local copy to the master copy. It is a matter of someone needs to
do the work. The more often the push, the more work. On the other hand, we
understand we don't want to have a big gap. so our plan is to push after
every stable build since we expect most users would only be using stable builds.
In short, I agree that we need to push the code now, since it
has been too long since last push. The intention was to push at least once a
month if not more often after each stable build.
br,
Wenfeng
From: birt-pmc-bounces@xxxxxxxxxxx
[mailto:birt-pmc-bounces@xxxxxxxxxxx] On Behalf Of Wayne Beaton
Sent: Friday, April 26, 2013 10:20 AM
To: birt-pmc@xxxxxxxxxxx
Subject: [birt-pmc] BIRT Git repository may be out of date.
I'm moving this discussion out of bugzilla an onto the PMC
list.
I assume that you mean "Git" rather than "GitHub".
How often does this push happen?
