Etria Lists

Justizin wrote:
> Can we fix the workflow?  Maybe I can put some time into this in the
> next week or so.

If you can put time into this, then great!

> Are you otherwise ready to cut 1.5?  Do you need help?

Yes, I could do with a hand to get the last few loose ends tied up.  As 
far as I can work out, <http://plone.org/products/quills/issues/45> is 
the only outstanding bug *.  From the comments there, it seems like the 
problem has been resolved, but it needs some verification of that and 
then a checkin.

>  I agree with
> not wanting 1.5 to rot because they are some outstanding bugs which
> also exist in previous releases.
> 
> Let's get this thing out the door, and maybe we can cut 1.5.1 if I can
> solve this soon.

I agree.  1.5.0 has been too long coming!

Tim

p.s. There are some translation and bugfix checkins on the trunk that 
are not on the 1.5 branch.  I'm inclined to delete the 1.5 branch for 
now and just revert to releasing from the trunk.  I think the new policy 
should be that you *only* cut a maintenance branch when you want to 
commit a feature to the trunk that shouldn't be in the current stable 
release.  That should minimise the maintenance burden.


* Unfortunately, our Poi instance at plone.org/products/quills/issues 
seems to have taken to randomly tagging some issues as 'rejected', when 
they shouldn't be.  I've filed a bug report about it, but who knows 
what'll happen to that ;-).