Mailing List Archive: Zope: Dev

Re: [Checkins] SVN: zope.release/branches/3.4/ * Added latest version of zope.app.security to avoid deprecation

Index | Next | Previous | View Threaded

ccomb at free

Aug 1, 2008, 2:37 AM

Post #1 of 6 (397 views)
Permalink

*Re: [Checkins] SVN: zope.release/branches/3.4/ Added latest version of zope.app.security to avoid deprecation**

Stephan Richter a écrit :
> Log message for revision 89104:
> * Added latest version of zope.app.security to avoid deprecation
> warnings.
>
> * Added history file for the KGS to hopefully create better release
> notes.

Did you miss the CHANGES.txt in zope.release ? We have two histories now.

How did you choose the 3.4.0c5 version? I mean, where does the "5" come from?

Christophe
_______________________________________________
Zope-Dev maillist - Zope-Dev[at]zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )

srichter at cosmos

Aug 1, 2008, 6:55 AM

Post #2 of 6 (370 views)
Permalink

*Re: Re: [Checkins] SVN: zope.release/branches/3.4/ Added latest version of zope.app.security to avoid deprecation** [In reply to]

On Friday 01 August 2008, Christophe Combelles wrote:
> Did you miss the CHANGES.txt in zope.release ? We have two histories now.

Nope, but that file tracks the package -- source code -- changes of
zope.release.

I wanted a separate file that tracks the changes to the
controlled-packages.cfg file.

> How did you choose the 3.4.0c5 version? I mean, where does the "5" come
> from?

We have been doing c* KGS releases all along. See

http://download.zope.org/zope3.4/intro.html

I just have not bothered updating the Zope3 tree, making packages and
announcements. It just costs too much time. Unless Marius or someone else
signs up for producing TAR ball releases and announces them, I will only
create a TAR ball and announcement for Zope 3.4.0 final.

Regards,
Stephan
--
Stephan Richter
Web Software Design, Development and Training
Google me. "Zope Stephan Richter"
_______________________________________________
Zope-Dev maillist - Zope-Dev[at]zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )

ccomb at free

Aug 1, 2008, 7:34 AM

Post #3 of 6 (369 views)
Permalink

*Re: Re: [Checkins] SVN: zope.release/branches/3.4/ Added latest version of zope.app.security to avoid deprecation** [In reply to]

Stephan Richter a écrit :
> On Friday 01 August 2008, Christophe Combelles wrote:
>> Did you miss the CHANGES.txt in zope.release ? We have two histories now.
>
> Nope, but that file tracks the package -- source code -- changes of
> zope.release.
>
> I wanted a separate file that tracks the changes to the
> controlled-packages.cfg file.

In my understanding, there is almost no source code in 'zope.release', since it
has been moved into 'zope.kgs'. So there should be very few entries in
CHANGES.txt, and I'm not sure there is a real interest in having two separate
files. In my opinion, it adds confusion, people are more used to maintain
CHANGES.txt.
The other problem is there is no tag for c1, c2, c3 and c4. I thought
zope.release was meant to represent the release number of zope.

I would tend to:
- create a tag for all missing candidates
- merge KGS-HISTORY.txt into CHANGES.txt and recover missing information from
published control-packages.cfg

Christophe

>
>> How did you choose the 3.4.0c5 version? I mean, where does the "5" come
>> from?
>
> We have been doing c* KGS releases all along. See
>
> http://download.zope.org/zope3.4/intro.html
>
> I just have not bothered updating the Zope3 tree, making packages and
> announcements. It just costs too much time. Unless Marius or someone else
> signs up for producing TAR ball releases and announces them, I will only
> create a TAR ball and announcement for Zope 3.4.0 final.
>
> Regards,
> Stephan

_______________________________________________
Zope-Dev maillist - Zope-Dev[at]zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )

srichter at cosmos

Aug 1, 2008, 8:29 AM

Post #4 of 6 (370 views)
Permalink

*Re: Re: [Checkins] SVN: zope.release/branches/3.4/ Added latest version of zope.app.security to avoid deprecation** [In reply to]

On Friday 01 August 2008, Christophe Combelles wrote:
> > I wanted a separate file that tracks the changes to the
> > controlled-packages.cfg file.
>
> In my understanding, there is almost no source code in 'zope.release',
> since it has been moved into 'zope.kgs'. So there should be very few
> entries in CHANGES.txt, and I'm not sure there is a real interest in having
> two separate files. In my opinion, it adds confusion, people are more used
> to maintain CHANGES.txt.

Okay, I am open to suggestions and want to hear others give an opinion too.

> The other problem is there is no tag for c1, c2, c3 and c4. I thought
> zope.release was meant to represent the release number of zope.

It is. I and Marius simply did not create those tags.

> I would tend to:
> - create a tag for all missing candidates

Cool, I take you up on that.

> - merge KGS-HISTORY.txt into CHANGES.txt and recover missing information
> from published control-packages.cfg

These are two tasks:

- Update KGS-HISTORY.txt to contain the changes of the previous releases.
(Luckily you can just look at the SVN changelog for controlled-packages.cfg.)
I take you up on that one as well! :-)

- Merge KGS-HISTORY.txt into CHANGES.txt. I want to hear a couple more
opinions on that.

Regards,
Stephan
--
Stephan Richter
Web Software Design, Development and Training
Google me. "Zope Stephan Richter"
_______________________________________________
Zope-Dev maillist - Zope-Dev[at]zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )

ccomb at free

Aug 1, 2008, 11:19 AM

Post #5 of 6 (370 views)
Permalink

*Re: Re: [Checkins] SVN: zope.release/branches/3.4/ Added latest version of zope.app.security to avoid deprecation** [In reply to]

Stephan Richter a écrit :
> On Friday 01 August 2008, Christophe Combelles wrote:
>>> I wanted a separate file that tracks the changes to the
>>> controlled-packages.cfg file.
>> In my understanding, there is almost no source code in 'zope.release',
>> since it has been moved into 'zope.kgs'. So there should be very few
>> entries in CHANGES.txt, and I'm not sure there is a real interest in having
>> two separate files. In my opinion, it adds confusion, people are more used
>> to maintain CHANGES.txt.
>
> Okay, I am open to suggestions and want to hear others give an opinion too.
>
>> The other problem is there is no tag for c1, c2, c3 and c4. I thought
>> zope.release was meant to represent the release number of zope.
>
> It is. I and Marius simply did not create those tags.
>
>> I would tend to:
>> - create a tag for all missing candidates
>
> Cool, I take you up on that.

Done.

>
>> - merge KGS-HISTORY.txt into CHANGES.txt and recover missing information
>> from published control-packages.cfg
>
> These are two tasks:
>
> - Update KGS-HISTORY.txt to contain the changes of the previous releases.
> (Luckily you can just look at the SVN changelog for controlled-packages.cfg.)
> I take you up on that one as well! :-)

I've updated KGS-HISTORY.txt and CHANGES.txt.

Actually KGS-HISTORY.txt is just a reformatted svn diff between successive
versions. I'm not sure it has a real added value, excepted when there are
explanations about the version upgrades.

Christophe

>
> - Merge KGS-HISTORY.txt into CHANGES.txt. I want to hear a couple more
> opinions on that.
>
> Regards,
> Stephan

_______________________________________________
Zope-Dev maillist - Zope-Dev[at]zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )

philipp at weitershausen

Aug 1, 2008, 4:05 PM

Post #6 of 6 (360 views)
Permalink

*Re: [Checkins] SVN: zope.release/branches/3.4/ Added latest version of zope.app.security to avoid deprecation** [In reply to]

Christophe Combelles wrote:
> Stephan Richter a écrit :
>> On Friday 01 August 2008, Christophe Combelles wrote:
>>> Did you miss the CHANGES.txt in zope.release ? We have two histories
>>> now.
>>
>> Nope, but that file tracks the package -- source code -- changes of
>> zope.release.
>>
>> I wanted a separate file that tracks the changes to the
>> controlled-packages.cfg file.
>
> In my understanding, there is almost no source code in 'zope.release',
> since it has been moved into 'zope.kgs'. So there should be very few
> entries in CHANGES.txt, and I'm not sure there is a real interest in
> having two separate files. In my opinion, it adds confusion, people are
> more used to maintain CHANGES.txt.

Exactly.

> The other problem is there is no tag for c1, c2, c3 and c4. I thought
> zope.release was meant to represent the release number of zope.
>
> I would tend to:
> - create a tag for all missing candidates
> - merge KGS-HISTORY.txt into CHANGES.txt and recover missing information
> from published control-packages.cfg

+1
_______________________________________________
Zope-Dev maillist - Zope-Dev[at]zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com