Re: [Zope-dev] [Zope-Checkins] SVN: Zope/tags/2.12.0/doc/WINDOWS. Renamed to avoid warning.
Baiju M wrote:
Log message for revision 104986: Renamed to avoid warning. Should we remove it ?
Changed: D Zope/tags/2.12.0/doc/WINDOWS.rst A Zope/tags/2.12.0/doc/WINDOWS.txt
Why are you editing a tag? This is already gone on the 2.12 branch and trunk. Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk
On Tue, Oct 20, 2009 at 8:25 PM, Chris Withers <chris@simplistix.co.uk> wrote:
Baiju M wrote:
Log message for revision 104986: Renamed to avoid warning. Should we remove it ?
Changed: D Zope/tags/2.12.0/doc/WINDOWS.rst A Zope/tags/2.12.0/doc/WINDOWS.txt
Why are you editing a tag?
This is already gone on the 2.12 branch and trunk.
Sorry, I meant to do it in branch. I will revert it. Regards, Baiju M
On Wed, Oct 21, 2009 at 8:19 AM, Baiju M <mbaiju@zeomega.com> wrote:
On Tue, Oct 20, 2009 at 8:25 PM, Chris Withers <chris@simplistix.co.uk> wrote:
Baiju M wrote:
Log message for revision 104986: Renamed to avoid warning. Should we remove it ?
Changed: D Zope/tags/2.12.0/doc/WINDOWS.rst A Zope/tags/2.12.0/doc/WINDOWS.txt
Why are you editing a tag?
This is already gone on the 2.12 branch and trunk.
Sorry, I meant to do it in branch. I will revert it.
Now I realize how it happened. There is an svn:external inside zope2docs/trunk/releases (svn://svn.zope.org/repos/main/zope2docs/releases) which is pointing to 2.12 tag, should we change this to 2.12 branch ? Regards, Baiju M
Am 21.10.09 04:55, schrieb Baiju M:
On Wed, Oct 21, 2009 at 8:19 AM, Baiju M <mbaiju@zeomega.com> wrote:
On Tue, Oct 20, 2009 at 8:25 PM, Chris Withers <chris@simplistix.co.uk> wrote:
Baiju M wrote:
Log message for revision 104986: Renamed to avoid warning. Should we remove it ?
Changed: D Zope/tags/2.12.0/doc/WINDOWS.rst A Zope/tags/2.12.0/doc/WINDOWS.txt
Why are you editing a tag?
This is already gone on the 2.12 branch and trunk.
Sorry, I meant to do it in branch. I will revert it.
Now I realize how it happened. There is an svn:external inside zope2docs/trunk/releases (svn://svn.zope.org/repos/main/zope2docs/releases) which is pointing to 2.12 tag, should we change this to 2.12 branch ? No, otherwise docs.zope.org should display only the release notes of the release versions - w/o the release notes of the upcoming version. That's why it refers to the latest release tag.
Andreas
Baiju M wrote:
Now I realize how it happened. There is an svn:external inside zope2docs/trunk/releases (svn://svn.zope.org/repos/main/zope2docs/releases) which is pointing to 2.12 tag, should we change this to 2.12 branch ?
Have you actually checked the branch and trunk? I've already done quite a bit of cleanup on these docs... Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk
On Wed, Oct 21, 2009 at 1:00 PM, Chris Withers <chris@simplistix.co.uk> wrote:
Baiju M wrote:
Now I realize how it happened. There is an svn:external inside zope2docs/trunk/releases (svn://svn.zope.org/repos/main/zope2docs/releases) which is pointing to 2.12 tag, should we change this to 2.12 branch ?
Have you actually checked the branch and trunk? I've already done quite a bit of cleanup on these docs...
I can see your changes, but it will appear in the site when 2.12.1 is released. May be we should have a '2.13' or 'dev' doc site which is pointing to trunk. Regards, Baiju M
Baiju M wrote:
I can see your changes, but it will appear in the site when 2.12.1 is released.
May be we should have a '2.13' or 'dev' doc site which is pointing to trunk.
I think having a 'dev' doc site, like Django does, would be cool. I guess that would be built nightly from trunk or some such? cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk
participants (3)
-
Andreas Jung -
Baiju M -
Chris Withers