Cosmo server or whatever we use as a default -> unless we get a real certificate we will get the popup "do you want to trust this certificate?".
Is this ok? Heikki turned this on for Zythos (works ok), he tried with Venue Comm (went to some random shopping site).
PLAN -> We should go ahead and do this and buy certificates for our public facing servers.
OSAF Web Mail
mail.osafoundation.org does'nt work.
Did anyone file a ticket for this?
Aparna will send an email support.
Staff Meeting
Aparna will demo the qa test framework.
Since we want to keep the meeting brief, we will do the timezone and qa demos.
Defer the recurrence and sharing demos for next week.
Is the length of release too long for 0.6?
Are we going to have a bug fix release after we release 0.6?
Could this be a milestone rather than a release
We think there should be some room for this in 0.7 but we aren't sure how to handle this.
Do we have a specific bug fix milestone or is this handled scattered throughout the release?
For example, schema evolution we would not support this on a per milestone basis, on a release level only.
How are we going to service the release.
This kind of depends on our message - try it out vs use it day to day.
Need to decide on our message for 0.6.
Ted is in favor of shorter releases -> to get feedback from the outside world and feed that back into the product.
Can this work from a milestone? do we need to use releases?
Lisa feel that short releases are easier to plan in general.
I think we agree that we should try and make 0.7 shorter perhaps by trying to stage the features a bit better. We will continue the discussions on this as part of the 0.7 planning.
As a target...
2 milestones -> short
4 milestones -> medium
5+ milestones -> long
We should try and aim for 3 development milestones - 2 design phases
Other outstanding questions for further discussion
Do we want to have a really short response release? Talk to Mitch about this.