[Zope-dev] Dependencies on new packages should require feature releases

Christian Theune ct at gocept.com
Fri Apr 3 06:08:20 EDT 2009


Hi,

(this message probably just has a reminder function)

in one of my apps I had to upgrade many packages to a lot of new
versions suddenly when updating zope.publisher. That was caused because
zope.publisher started depending on a new (previously non-existing)
package within a bugfix release and I was only interested in that
bugfix.

Reading the Steering Group decisions, I think that's what the last
sentence wants to say, but it abruptly ends mid-sentence. 

@Martijn: You started writing that sentence, you mind finishing whatever
you tried to say? (I think it's what I wanted to say with this mail.) :)

Christian

-- 
Christian Theune · ct at gocept.com
gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany
http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1
Zope and Plone consulting and development
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://mail.zope.org/pipermail/zope-dev/attachments/20090403/060a0511/attachment.bin 


More information about the Zope-Dev mailing list