On Sat, Jan 10, 2009 at 1:00 PM, Mark Struberg <[email protected]> wrote: > I've checked my list and found a few things we should possibly do before the > milestone: > > 1.) create a site.
+1 but not that important :-) but I totally agree, that having a site would be more than appreciated by lot's of folks. This may be done via maven in the main projets src/site or we may also create an own site module . > Is there any documentation standard as we e.g. have for maven-plugins? > I've seen Gurkan wrote a few slide as introduction to WebBeans already. Maybe > we can use this as a starting point? > I guess it's not legally possible to include the spec, but there should be no > problem linking to the JSR-299 page. > > 2.) code formatting, remove unused imports etc. The usual polishing > suspects... +0 > > 3.) Check the dependencies via mvn dependency:analyze. > Which dependencies have to be passed transitively? > Which dependencies are only used at compile time > Which dependencies are only used for testing? > Just to make sure we don't have a rat tail full of jars no one needs. > > 4.) incorporate the TCK Peter Muir wrote. I must admit I'm not sure how we > should do this best. it is maven-based, right? So we can somehow automate it. > There is also the legal aspect we should keep an eye on. I read through the > license for the JSR-299 download and don't know what I actually should think > about it :/ Though I'v only studied law in vienna so I'm not an expert in US > contracts. the TCK, for webBeans is ASL-based. However all JCP-based JSR usually suck. a) they are not open (even if the call it it java COMMUNITY process) b) their licenses are pretty damn restrictive > > 5.) Create a sample with myfaces and openjpa to show webbeans usage with > @Transactional and stuff. For what I understand we don't need to use Marios > orchestra in this scenario anymore (LazyInitializationException and > NonUniqueObjectException handling), insn't it? yep. I have the same understanding. > > LieGrue, are you German? Or Austrian ? Cheers, Matthias > strub > > --- Matthias Wessendorf <[email protected]> schrieb am Sa, 10.1.2009: > >> Von: Matthias Wessendorf <[email protected]> >> Betreff: Re: Milestone release planing >> An: [email protected] >> Datum: Samstag, 10. Januar 2009, 17:30 >> On Fri, Jan 9, 2009 at 2:48 PM, Kevan Miller >> <[email protected]> wrote: >> > >> > On Jan 9, 2009, at 10:58 AM, Mark Struberg wrote: >> > >> >> Hi Gurkan! >> >> >> >> You talked about doing a milestone release in the >> next days. >> >> >> >> Just like to make sure that we've finally met >> all prerequisites before you >> >> start the vote. >> > >> > >> > Thanks for the discussion Mark... >> > >> > The normal process would be: >> > >> > * release discussion - describing proposed release >> plans (e.g. approximate >> > timing, remaining functional items, etc). This gives >> community members a >> > chance to comment, register additional function/bug >> fixes that they'd like >> > to see included, etc. >> > >> > * release preparation - once consensus is reached, >> prepare for the release. >> > Finalize desired functionality, prepare documentation, >> etc. Good time to ask >> > community members to review (easier to fix now, rather >> than spinning a new >> > release candidate, starting a new vote, etc...) >> > >> > * release vote - prepare a release for review and call >> a vote. >> > >> > In incubator, we'll then go through an incubator >> vote. We should expect that >> > this incubator vote will identify problems. But >> that's all goodness... Once >> > the incubator vote passes, then we have our first >> release. >> >> +1 >> when Trinidad was still in the incubator mode, the folks on >> the >> [email protected] list >> really helped to polish some of the (maven) artifacts. The >> Trinidad >> project is still >> gaining from that. All good stuff there. But don't >> expect the first >> vote to pass ;-) >> > > > > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
