[quills-dev] Status of trunk(s)
Tim Hicks tim at sitefusion.co.ukThu Apr 10 12:21:40 UTC 2008
- Previous message: [quills-dev] Please help with merge
- Next message: [quills-dev] Static portlet in quills blog
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Folks, A few developments that you may be interested in: - I've now merged my tim2p-towards-1.7 branches to trunk (thanks Tom!). - I've eggified QuillsEnabled (now at Products.QuillsEnabled) and QuillsEnabledRemoteBlogging (now at Products.QuillsEnabledRemoteBlogging). - I've created new buildouts for Products.Quills and Products.QuillsEnabled, for their trunks, as well as for the 1.6 maintenance branch for Products.Quills. See Products.Quills[Enabled]/buildouts/. These buildouts use eggs for everything - albeit with svn checkouts rather than downloads from pypi. - I've verified that tests pass for the (trunk) buildouts. The next step is to figure out the best way to make a 1.7 beta release for Products.QuillsEnabled (and Products.Quills, I suppose) - i.e. whether to use pypi or not. I'll post to product-developers at lists.plone.org to get opinions on this, shortly. One outstanding issue is that I've not focused on migrations, at all. This should be such a problem for QuillsEnabled (which is new), but those currently using Quills may wish to take a look at this... Tim
- Previous message: [quills-dev] Please help with merge
- Next message: [quills-dev] Static portlet in quills blog
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the quills-dev mailing list