I am not sure that even this would be acceptable. The problem with doing development behind the firewall is that it means that the project is Actuate's, not Eclipse's. How can someone from any other company participate equally on the project if the main development and the 'stable ' builds all happen behind a firewall?
Git is by its very nature a distributed system. Investing in
something like AWS for this makes no sense.
We have no issue with a project team working from a local clone.
Some amount of latency is expected, but a full month is too much for
a project that is expected to working in an open and transparent
manner. It is basically impossible for anybody else to participate
in the project if the repository is always days, weeks, or months
out-of-date.
The pushes back to eclipse.org have to be done more frequently.
At a minimum, you should be able to very quickly set up a cron job
that forces a push to eclipse.org every day, or--even better--a few
times a day (every hour). This should literally require a one-liner
cron entry. I can help if necessary.
Your developers shouldn't even notice the push is happening. Even
better would be some kind of commit hook that does the push (as
Jesse suggests). If a single push fails, the next one will do the
job. That's how Git works.
This needs to be automatic.
Please make this happen as soon as possible.
Wayne
On 04/26/2013 04:59 PM, Wenfeng Li
wrote:
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
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?
_______________________________________________
birt-pmc mailing list
birt-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/birt-pmc
