Reinhard Poetz wrote: >> The only thing i'm still unsure about is how to do the sync between the >> zone and people.a.o, rsync might not work too well given the metadata >> that's involved. > > Why do you think so? As long there is no other process that manipulates > Cocoon artifacts in the Apache m2-sync repo *directly* and circumvents > the staging repo, I don't see any problems.
OK i see now, it will work if nobody circumvents the staging repo. > How can we trigger the sync from cocoon.zones.apache.org given that we > shouldn't/mustn't store private ssh keys on this potentially unsecure > machine? Wouldn't it be a better option to have our staging repo on > people.apache.org too? i didn't know the zone is potentially unsecure. If we are allowed to create people.a.o/repo/cocoon-staging-release-repository then that's ok as well (and probably easier to access for all). Jorg
