Jorg Heymans wrote:
Reinhard Poetz wrote:
My understanding was that the staging repo is a mirror of everything
under org/apache/cocoon and when we really want to release, we call a
script that copies our changes to the public sync repo or if we want to
roll back, we copy back the changes by cop
Reinhard Poetz wrote:
> My understanding was that the staging repo is a mirror of everything
> under org/apache/cocoon and when we really want to release, we call a
> script that copies our changes to the public sync repo or if we want to
> roll back, we copy back the changes by copying the conte
Reinhard Poetz wrote:
>
> I tried it and run into the problem[1] that when I refer to the already
> released Cocoon parent artifact (org.apache.cocoon:cocoon:1), the old
> value for the distribution repository is taken. Because of this I
> accidently deployed the batik parent pom (org.apache.coco
Jorg Heymans wrote:
Jorg Heymans wrote:
Just agreed on this with Reinhard off-list, i'll make the required changes.
ok this is done now. I hope i got the permissions right (g+w and o+w on
all dirs involved, including my home dir).
Can someone please give it a spin ?
Is it on purpose that
Reinhard Poetz wrote:
Jorg Heymans wrote:
Jorg Heymans wrote:
Just agreed on this with Reinhard off-list, i'll make the required
changes.
ok this is done now. I hope i got the permissions right (g+w and o+w on
all dirs involved, including my home dir).
Can someone please give it a spin ?
Jorg Heymans wrote:
Jorg Heymans wrote:
Just agreed on this with Reinhard off-list, i'll make the required changes.
ok this is done now. I hope i got the permissions right (g+w and o+w on
all dirs involved, including my home dir).
Can someone please give it a spin ?
I'll give it a try to
Jorg Heymans wrote:
> Just agreed on this with Reinhard off-list, i'll make the required changes.
>
ok this is done now. I hope i got the permissions right (g+w and o+w on
all dirs involved, including my home dir).
Can someone please give it a spin ?
Regards
Jorg
Bertrand Delacretaz wrote:
>
> I think the safe way is to first rsync from the zone to a temporary
> location on people.a.o, which is on the same filesystem than the final
> location, then do a move (mv), which is atomic, to the final location
> on people.a.o.
>
> -Bertrand (I'm not being parano
Jorg Heymans 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
Note that, IMHO, you shouldn't rsync directly into the people.a.o
directories that are rsynced to the
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 Apac
Jorg Heymans wrote:
I've setup a staging repo on the zones,
http://cocoon.zones.apache.org/cocoon-staging-release-repository/. It's
configured in the root pom so any release:perform action will be going
there instead of people.a.o.
The idea is that we can verify releases from there *before* we s
11 matches
Mail list logo
