Hey Dan Please see my comments about components ownership below
On Fri, Nov 26, 2010 at 1:48 AM, Dan Haywood <[email protected]> wrote: > All, > We need to decide what we want to release for v0.1, and get some commitments > and outline plan in place for a release. > > To get the ball rolling... my personal view is that we should be releasing > what's "stable", and drop things that may still be in flux. When I say > "stable", I mean that it should at least be coherent to someone who might > come across Isis v0.1 and wonder what it's all about. I don't necessarily > mean that it is feature complete. But I do mean that it should have some > DocBook documentation, even if that documentation is not extensive. At the > moment, most of that DocBook stuff is stubbed out (though there's lots of > stuff in contrib/initial that can be reused). > > The following is a list of the components, with my suggestion as to the > "owner" with respect to v0.1 (meaning that this person would be responsible > for making sure that the docs etc are in place). I've also indicated > whether I think the component should be releasable, should not be released, > or I don't know its status: > > - applib: > - owner: Dan > - release: Yes > - core: > - owner: ??? Rob - would you pick up ??? > - release: Yes > - defaults > - owner: Dan > - release: Yes (need to confirm on defaults/security) > - alternatives/ > - bytecode: > - owner: Dan > - release: Yes > - embedded > - owner: Dan > - release: Yes > - objectstore/ > - nosql > - owner: Rob > - release: ??? > - sql > - owner: Kevin/Rob > - release: ??? > - xml > - owner: Rob > - release: Yes > - jpa: > - owner: Dan > - release: No (not migrated from contrib/initial, and won't be released > in v0.1) > - profilestore/ > - xml: > - owner: Rob > - release: Yes > - progmodel/ > - groovy: > - owner: Dan > - release: Yes > - wrapper: > - owner: Dan > - release: Yes > - remoting: > - owner: Rob ??? > - release: ??? (my preference would be to drop it for v0.1, pending > more testing) > - viewer/ > - bdd: > - owner: Dan > - release: Yes > - dnd: > - owner: Rob > - release: Yes > - html: > - owner: Rob > - release: Yes > - junit: > - owner: Dan > - release: Yes > - restful: > - owner: Dan > - release:Yes > - scimpi: > - owner: > - release: ??? Rob ??? > - wicket: > - owner: Dan > - release:Yes > > Other stuff: > > - support > - prototype: > - owner: ??? I want to own Support->Prototype (NOTE: Sabine may have shown some interest in this as well - Sabine is that right ?) > - release: Yes (more work required) > - screencasts > - owner: Dave > - release: Yes (in progress) > - image heatmap on index.apt > - owner: Alexander > - release: Yes (in progress) > - "the release process" [1] > - owner: ??? I want to own the "Release Process" thing. > > > Please chip in, amend as necessary, take ownership of modules if you feel > you'd like to. > > Once we know what we want to release, then we can think about setting some > dates to get it ready for release. Even before then, there is some > additional work in terms of someone getting up to speed with the Apache > release process (see [1]). > > [1] https://cwiki.apache.org/confluence/display/ISIS/ReleaseProcess > > > Thanks, > Dan > > > -- Thanks - Mohammad Nour Author of (WebSphere Application Server Community Edition 2.0 User Guide) http://www.redbooks.ibm.com/abstracts/sg247585.html - LinkedIn: http://www.linkedin.com/in/mnour - Blog: http://tadabborat.blogspot.com ---- "Life is like riding a bicycle. To keep your balance you must keep moving" - Albert Einstein "Writing clean code is what you must do in order to call yourself a professional. There is no reasonable excuse for doing anything less than your best." - Clean Code: A Handbook of Agile Software Craftsmanship "Stay hungry, stay foolish." - Steve Jobs
