From arnar.lundesgaard at gmail.com Wed Apr 28 14:53:26 2010 From: arnar.lundesgaard at gmail.com (Arnar Lundesgaard) Date: Wed, 28 Apr 2010 14:53:26 +0200 Subject: [ztm] 2010.1 release Message-ID: Earlier today I uploaded eggs and documentation for the second quarterly release of ZTM Topic Maps. Based on the experience of this and the previous release we're targeting a tertial release schedule. (Every 4th month instead of every 3rd). The official release is made up of the three packages from the previous release: ztm.topicmaps 0.8.1 The core Topic Maps engine. - It has seen many smaller improvements and better documentation. See its CHANGES.txt. Repository: ztm.interfacemanager 0.8.1 Connects topics with the Zope Component Architecture - Minor updates Repository: ztm.navigator 0.8.1 Omnigator-like interface for navigating a topic map. Views are now pagelets for easier embedding. Mostly smaller bug-fixes. Repository: There are also some new packages that these build on: ztm.collation 0.0.4 Unicode collation. This package is functional but needs more work to support all locales. Repository: Other: ztm.humanmsg 1.0 Packages the latest version of the humanmsg library for consumption by `ZTM Topic Maps` modules. Repository: ztm.jquery.core 1.4.2 Packages the latest version of the `jQuery` Javascript library for consumption by `ZTM Topic Maps` modules. Repository: ztm.jquery.ui 1.8 Packages the latest version of the `jQuery UI` Javascript library for consumption by `ZTM Topic Maps` modules. Repository: Zope Toolkit ------------ The biggest change is that we're no longer bound to Zope 3.4 (or its successor BlueBream 1.0 which is currently in beta.) ZTM now builds on the Zope Toolkit[1]. This allowed us access to two years of bugfixes, stabilization, Python 2.6 support, performance improvements and a much improved dependency story. The toolkit represents the shared packages between the big users of Zope, like Plone, repoze, grok, BlueBream and many more. We made the decision to adopt ZTK somewhat late in the release process and the ensuing work is what held up the release. The reason was simply that 1) it contained virtually all the packages that we're using anyway, 2) it is the future of Zope and 3) it was becoming painful to remain bound to the Zope 3.4 KGS. It should make it easier for use to reuse functionality from other packages that build on Zope and we can now automate integration tests. Packages replaced by ZTK have backwards compatibility (mostly in the zope.app.* namespace). We expect some problems with imports since some packages are likely to have relied on implicit dependencies of ztm.packages. Backwards compatibility is maintained in all zope.app.* packages. Packages simply need to declare that depenency themselves or update their imports according to [2] What about all the other packages? ---------------------------------- Many of the packages affiliated with the content management side of ZTM has undergone upgrades and bugfixes. Unfortunately they still need to be tested properly with the new core packages and the ZTK upgrade. Most of the work in adapting to ZTK is done but packaging has proven time-consuming. Expect this to happen in the next week. We'll post another email once that process is complete. After internal testing we will provide a Known Good Set aimed at portal developers and update ztm.demonstration (which provides a basic portal when installed.) Two of the packages have particularly relevant changes. The changes are available in the source code repository. ztm.webdesk The webdesk has been reimplemented. It has been given an AJAX workover allowing users to do more from the webdesk and we now have an API for configuration and plugging in new features. Repository: ztm.publishing The toolbar is now inserted by the publishing process meaning that developers no longer have to adapt templates to include it. Repository: ztm.filearchive Rewritten to use blobs. There is a new basic GUI and extractors for getting text out of the uploaded files. NB: this version of the file archive is not backwards compatible and no upgrade routine has yet been written. Repository: We're also now in a better shape to release packages between quarterly releases, making future releases "just" tested known good sets. Roadmap ======== Priorities for the next release has not yet been decided. Feedback is welcome. We're aiming for a new release between 15. august and 15. september. [1] http://docs.zope.org/zopetoolkit/ [2] http://docs.zope.org/zopetoolkit/releases/overview-trunk.html