Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-incubator-dev] 0.5M8 and the future


> should we wait until the following week to do our 0.5M8 release?
 
Well, first, remember at this point it's simply a "milestone"
I'm sure you'll recall me harping on "release" being a reserved word at Eclipse.

I'd say if you can, to go ahead and produce your M8 milestone now, so it can be on the WTP downloads page right away with Ganymede.
We can still do some separate announcements and publicity the following week (and, yes, in that case,
I think better to follow the main Ganymede announcements and publicity).

Then, if I'm reading you right, you'd like to plan on a formal pre 1.0 release, call it 0.5.
I'd say we should plan on that for about 1 month following Ganymede. That'd give us time to discuss
with EMO, schedule a formal release review, etc. Plus, would give you a couple more weeks to fix up those
icons, etc., that you mention. (so the formal release would be very similar to the M8 milestone, but not exactly the same).

Am I hearing you right so far?

> ... what should the next version be called, I would go for 0.6 for now

Do you mean for release? Or just what you label it in your milestones.  Assuming you don't need another release until next June, I would recommend that after a formal 0.5 release, that you "join" the main WTP stream/builds and just produce milestones along with the rest of WTP. (milestones towards Io, 2009 release, that is). If you'd like to be conservative, you can certainly start off with 0.6 version numbers, and then move to 1.0 next spring ... nearer your graduation and Io simultaneous release. But, it's not unheard of for projects to start using 1.0 in their milestone builds, under their confidence (and plans) to graduate before/during the formal 1.0 release. To be explicit, you can still be "incubating" and be part of WTP builds/milestones ... it just needs to keep the "incubating" name until you graduate. I would recommend you/we plan on a graduation review roughly next March (2009) [perhaps right before EclipseCon?] and then have your 1.0 release review with the rest of the Io release review of WTP, in June 2009.

Feel free to correct me if I am misreading your desired plans/schedules, but this seems like a good one to me.

Oh, and BTW, we haven't really talked about it in WTP exactly, but we in the rest of WTP probably won't have much, if any, milestones until M2 or M3 (September) or so (due to getting a quick start on maintenance releases).

> David what else do you think we need to do to get us along in the incubation phase.

I think you all are doing great and well on your way to graduation. Any "community activity" you can engage in would help the case ... such as the Eclipse Live webinar you mentioned, perhaps present at some UI Working Group walk through (e.g. present on how you specifying XSL "engines" in preferences, the xpath view, etc.). I'm assuming you follow Eclipse enough to know what "UI Working Group walk through" means ... if not, well, then there's an example of the importance of community involvement :) As I've mentioned, my only concern is not getting that many bugs open from (early) end-users. Perhaps that will change when we have a more unified build and delivery mechanism.






From: David Carver <d_a_carver@xxxxxxxxx>
To: WTP Incubator Dev list <wtp-incubator-dev@xxxxxxxxxxx>
Date: 06/19/2008 10:59 PM
Subject: [wtp-incubator-dev] 0.5M8 and the future





So, we are nearing the 0.5M8 release.   David since next week is
Ganymede release should we wait until the following week to do our 0.5M8
release?   I think we would get lost otherwise.   It also would be nice
to have another announcement on the Web Tools home page about the
release.   This version is a bit more polished, we still need a few more
icons, and there is one annoying issue with the content assistance that
still needs to be worked out.  However, I think for an official 0.5
release we are close to being ready.

For polishing, I think we need to make sure there is enough user
documentation in place.  If anybody needs help with creating the
necessary docbook files please let me know, and I'll help get you going.

Also, for when we do release 0.5 we should plan on doing an Eclipse Live
seminar.   Any volunteers?

As for what should the next version be called, I would go for 0.6 for
now...There are several areas that still need addressing before we
contemplate a 1.0 release.   Their are portions of the debugging support
that still need to be addressed to make it more usefull, and a few areas
in content assistance, as well as a generall available model accessible
through the Content Model api.

Oh as for adopter usage, I know that the company I work for will be
adopting the current XSL Tooling 0.5M8 into our latest version our XML
IDE product we give to our members, so there is at least one adopter. :)

David what else do you think we need to do to get us along in the
incubation phase.   I know I've been doing community relations via my
blog which is part of planeteclipse, and I believe Doug is working on a
couple of articles.   Anything else you can think of?

Dave


_______________________________________________
wtp-incubator-dev mailing list
wtp-incubator-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev



Back to the top