apparently there is a bug in senders would be good to investigate that.
ok. I think we should seriously check the remaining errors/failures before marking them.
I would like to see a few process things discussed -how we maintain 1.0 stable branch -how we maintain 1.1 alpha. i.e do we try out some other package meta system? that could be worth some hacking at the start of the cycle to see the mechanism. It is not something to mess around with when we get near beta.
We can use the current update stream as the 1.0 stable branch and create a new stream, maybe based on another mechanism, for 1.1 alpha.
I think we should get all tests green and the remaining issues fixed before declaring a release candidate. There are also 3 OmniBrowser issues in the list and I wonder whether somebody plans to fix them? If we concentrate on these tasks in the next days and during the sprint, I am sure we are able to get a reasonable RC1 within the next 14 days.
ok but I would really like to integrate all the cool fixes of nicolas. so this is why I was thinking about 1.1 alpha. too Stef