[cosmo-dev] Cosmo 0.11 status

[Jared Rhine]

All planned changes to Cosmo 0.11 are in the branch.

We got to the point of being able to build a 0.11 Hub-style instance  
yesterday.  We've found some cases where unit tests fail, but that  
only seems to happen to me.  There's some indication that it's  
timezone related.  We're not going to block the release to figure that  
out.

I don't currently know if we're "automated test clean", like for  
Windmill.  If QA could list automated test statuses for 0.11 here,  
we'll confirm if we're close to triple zero.

I see these tickets as deserving a double-check before the triple zero  
stage:

#8481 Invert text and icon color when a row is selected
#9818 Users should be allowed to leave Title field blank
#10238 During collection switch, "loading" box moves to end of load
#10431 Better error message when user clicks on activate account link 2x
#10733 Can't log in to hub -- problem with percent char in username?
#10764 "Starts on" sorting results in unexpected results
#10866 unstamping recurring event as event results in js error
#11099 Calendar not refreshing when unstamping eventness from a  
recurring series
#11100 Web UI support for BMP unicode characters
#11125 Collection dialog elements need unique ID's
#11175 : in username causes chaos
#11268 Go to date field squishes into the sidebar
#11341 Change quick entry hint text to Create a new item.
#11350 IE 7 alert errors in VM when interacting with the canvas
#11358 DTSTAMP not exported correctly
#11377 make sure validation works for all form elements in detail view
#11510 can't save recurring events (All Occurrences) in list view
#11541 Deleting the last collection in my account leaves me stuck at  
"Loading"
#11614 Can't sort list view by date

Mikeal, could you look at 11358?  We're not doing a data migration,  
but you know more than anyone except Randy about what expected to  
change from this ticket.  I can take the activate one #10431 so QA  
doesn't need to create a separate instance for it.

For bug 11681 "bogus VALARMs present on Hub", we'll apply the database  
changes to Hub directly and not put a data migration into 0.11 (and  
reconsider for 0.12).

-- Jared