Etria Lists

Tim Hicks schreef:
> 
> I'd like to merge my various tim2p-towards-1.7 branches to the various 
> trunks.  This means cutting 1.6 maintenance branches before I do that, 
> of course.
> 
> The only thing in the way of this atm is a single failing browser test 
> in Products.Quills.  I think it's something very simple as I have looked 
> at the point the test fails at in a real browser, and all seems well. 
> There must be a spelling mistake, or some such, but I just can't figure 
> out what it is.  Would anyone be able to take a look with me?

I wouldn't mind that single failing test. Get it merged and more 
eyeballs can look at it. What helps if you get an error like 
"'This_test_is_known_to_fail' != the value you want".

> So, my question is: how does that mean I should release 1.7b1?  What 
> does releasing as eggs actually mean?  What would instructions to 
> testers to install/use the release look like, then?

Releasing: tagging in svn; python setup.py sdist bdist_egg upload. 
That's basically it for the individual eggs.

If there's an overall-egg (which would be handy): have it depend on the 
specific revisions of the eggs that you've just made so that I can put 
"Products.Quills" or whatever in my buildout and get all the dependent 
eggs in the right versions.

Install: tell 'em what to include in the buildout. Yes, make the release 
in such a way that this is a minimal list. Just an entry in eggs and 
zcml sections ought to be enough.

For the non-buildout users, make a tarball ready to dump into lib/python 
and just point them at the "how to install lib/python stuff" doc on 
plone.org.


One last thing: before releasing: remove any 
use-svn-suffix-in-version-string from setup.cfg if they're there. 
Otherwise you get 1.7b1-r1234 version numbers.


Reinout

-- 
Reinout van Rees          Blog: http://vanrees.org/weblog/
reinout at vanrees.org          Work: http://zestsoftware.nl/
http://vanrees.org          Video: http://reinout.blip.tv/