cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Torsten Schlabach" <>
Subject Re: Updated Dev Guide -> Avalon (see bug #34696)
Date Fri, 06 May 2005 14:30:29 GMT

>> If you can't work out what to do, just ask.

Apparently I do NOT have write access to the Cocoon SVN. At least I don't
manage to get my commit through. I had never tried the Cocoon SVN before,
I just picked up the info that all Lenya committers had access to Cocoon
as well from a dicussion somewhere else. Apparently this isn't true for
all Lenya committers.

Could you please be so kind and check the page in?


> Torsten Schlabach wrote:
>> Hi folks,
>> I have recently updated the page about Avalon. The original version is
>> here:
>> The patch is filed unter bug #34696.
>> I am not sure what the procedure is. I think I have write access to the
>> Cocoon SVN because I am a PMC member of Apache Lenya, but I think it
>> would
>> be sort of unpolite at least to just go ahead and check this in as I am
>> not a committer in Ccooon.
>> So would anyone review this documentation patch and apply it or give me
>> feedback?
> (moved do dev list, doc list is now just for wiki notifications)
> It is certainly polite to ask(!), but I'm happy for you to commit this
> page. However, as we are in the process of creating docs for 2.2, we
> need to have something in the trunk repository, so that your changes
> don't get lost.
> So, if you're able, also commit something to
> cocoon/trunk/src/documentation/src/content/xdocs/
> Name it c21-avalon (which means that it is a straight copy from Cocoon
> 2.1, and hasn't been updated to Cocoon 2.2).
> If you can't work out what to do, just ask.
> Regards, Upayavira

View raw message