[Grok-dev] dependencies missing needed for Grok 1.1 backwards compatibility

[Uli Fouquet]

Hi there,

Steve Schmechel wrote:

> Is there a reason that someone would have to quickly upgrade to 
> Grok 1.1, and not have the time to fix the dependencies in their
> own application?  If there is some sort of major security issue
> discovered, it should probably be fixed in version 1.0 and 1.1 
> anyway.
> 
> I think having this package available will just tempt people to 
> be lazy and put off really updating their application.  Either
> it just delays the inevitable, or the package would need to be
> maintained indefinitely.
> 
> I am +1 on good upgrade notes (regardless of whether the 
> "backwards compatibility" package is available or not).

Just having (nearly) finished such an upgrade for a larger project, I
agree with Steve (and Souheil and JW).

A backward-compat package would mean much work, could not guarantee to
succeed and would only delay the inevitable. Beside this, the upgrade
was not _that_ difficult. A list of 'moved' packages/components would,
however, make sense for me (especially for zope.pluggableauth, where I
had some issues). But that'd certainly be part of good upgrade notes.

Best regards,

-- 
Uli

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://mail.zope.org/pipermail/grok-dev/attachments/20100311/b5e05a82/attachment.bin