[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[jetty-dev] Re: On Leaving Incubation...
|
Jesse McConnell wrote:
I wanted to send out a mail to the dev list and to our mentors to sort
of bring everyone up to speed on our current reasoning and intentions.
on mention of mentors, technically who is the other one? I am the only
one listed in the proposal. Bjorn may have been on the list but is no
longer involved in Eclipse...
We would like to get out of incubation by early June if possible and I
am working towards taking care of that goal from the eclipse
perspective right now. I believe I am fairly up on what the
requirements are for getting this done and one of the first steps was
to at least declare interest to the mentors (which we have mentioned
before and I am formally declaring now :).
Cool. So to be clear you want to do two relatively independent things,
release and graduate. These are separate reviews (though they can be
done concurrently AFAIK).
We have a lot to take care of in a fairly short amount of time so I
mostly wanted to detail out here what I see remaining and then likely
check in and follow up at the end of next week on where we are and
what is left. I say end of next week as that is when I would like to
get the actual notification out to EMO and see about setting up an
actual review date. I'll write out a bullet list of things now and
anyone that wants to add to it please feel free to.
- First thing I would do is talk to the IP team to see if the IP review
required for the release is possible in the timeframe you want. As I
understand it, the current work is on getting things INTO Eclipse. For
a release the the IP status of the project needs to be reviewed to
ensure it is in good shape to go OUT.
* finish up changes for 7.0.0 (configuration mechanism, etc)
This is a release topic. Get the code finished.
* finish up porting documentation from Codehaus Wiki
(http://docs.codehaus.org/display/JETTY/Jetty+Documentation) into
Eclipse Wiki (http://wiki.eclipse.org/Jetty)
This is both a release and graduation topic. Releases should have doc
and mature (i.e., graduated projects) should have doc.
* get first cut of at least of the jetty eclipse plugins I worked on a
couple months back into svn and with an initial release
Unless you think the function is critical this does not feel essential
for either release or graduation.
As a side question, where is this code now? Was it part of the initial
contribution that got IP reviewed?
* update the project plan to include more milestones and flesh out the
themes and priorities section
Mostly a graduation review topic. Mature projects should have a plan.
* get others testing the update site for jetty milestones and
hopefully work with someone to make it more of a static site for
updating on each release
Seems optional though useful. Updates come after the release :-)
* wire in the conditioning process for jars going into the update site
Release topic
* add in remaining jetty features to update site
Release topic
* complete IP validation process (which is slated to be complete end
of may, fingers crossed)
Release topic
* produce release review docuware
(http://wiki.eclipse.org/Development_Resources/HOWTO/Release_Reviews)
Release topic
In the grand scheme of things I figure we meet the objectives of the
the incubation graduation process once we get a good many of the above
items resolved.
For the most part I agree. Having a release at Eclipse under your belt
is an essential part of the graduation process IMHO. The key element of
graduation for me is that the project can and is operating in "the
Eclipse way" -- openness, process, milestones, ... Jetty certainly has
many of these attributes. An interesting thought experiment: what if
all the mentors (all one of us afaict) disappeared? would the project
crash and burn? Clearly Jetty would not. The community is still
finding its way around but I have to say that I am extremely impressed
with your willingness to and interest in "getting it".
Jeff
