I just committed a new section to zope3docs about migration to newer Zope 3 releases. I think we should maintain a list of most important changes that could break backward-compatibility, like recent changing exception types used in zope.container in a separate document, so people who are upgrading from, say, Zope 3.4 to Zope 3.5 could easily find the bits about problems that can pop up in the transition. What are you thinking about that? -- WBR, Dan Korostelev
Dan Korostelev wrote:
I just committed a new section to zope3docs about migration to newer Zope 3 releases.
I think we should maintain a list of most important changes that could break backward-compatibility, like recent changing exception types used in zope.container in a separate document, so people who are upgrading from, say, Zope 3.4 to Zope 3.5 could easily find the bits about problems that can pop up in the transition.
What are you thinking about that?
I agree we should do that. For Grok we've been doing this with upgrade notes for some years now and we believe it works pretty well. What you created is this document, right? source/migration/34to35.rs Regards, Martijn
Hey Dan and everybody, I've taken the document Dan started and have reorganized it a bit and added bits I know of what happened at the sprint last week. I've also introduced an 'introduction' section which discusses the aim of many of the changes made and the general response a developer should have. Regards, Martijn
2009/2/6 Martijn Faassen <faassen@startifact.com>:
Hey Dan and everybody,
I've taken the document Dan started and have reorganized it a bit and added bits I know of what happened at the sprint last week. I've also introduced an 'introduction' section which discusses the aim of many of the changes made and the general response a developer should have.
That's great! Thank you. Looks like the 3.5 will be even better than 3.4 :) -- WBR, Dan Korostelev
participants (2)
-
Dan Korostelev -
Martijn Faassen