On 08/02/2013 12:23 PM, Jack Moffitt wrote:
We are starting to plan what will go in the first numbered version of
Servo. The proposal is to gate the initial release on a set of
criteria, and after that releases will be time based and include
whatever features are done by the release date (much like Rust).
We need to define what the release criteria are for this 0.1 release.
I'm not sure what specific timeline others were thinking, but I expect
we want to get this out there soon, perhaps the latest target would be
early next year.
I've created a page with a straw-man proposal of these criteria, and
any input is welcome. Should we have more things? Or less?
https://github.com/mozilla/servo/wiki/Version-0.1
As you've indicated, I think the most important criteria for a release
is having some kind of shell, which probably entails having an decent
embedding story. This is mostly as a convenience for people who want to
follow servo's progress, but also because it's important to get the
embedding API started early.
It could be nice to have a broad selection of sites that we at least
don't *crash* on, simply for the sake of appearances.
Do we need some kind of performance baseline for 0.1? There are some
pretty huge bottlenecks currently, and we may not want to make a release
announcement if perf looks very bad.
Finally, networking is currently a pretty big obstacle to actually using
servo, so there may be a few specific things that need to be beefed up
there. Is SSL required for servo 0.1?
_______________________________________________
dev-servo mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-servo