On Tue, Feb 3, 2009 at 7:59 AM, Gurkan Erdogdu <[email protected]> wrote: > +1 > I will re-start release process today. I will run RAT before deploying to > staging-repo.
you can integrate it on the maven build > > Mark, > In the samples/guess/pom.xml, there is a myfaces JSF dependencies as > *compile* scope. Is there any reason why its scope has not a *provided*? When > the scope is *compile*, all dependencies are injected into WEB-INF/lib. I > think that we mark the Java EE related libraries as *provided*. > > WDYT? > > > > > ________________________________ > From: Mark Struberg <[email protected]> > To: [email protected] > Sent: Monday, February 2, 2009 11:39:50 PM > Subject: Re: AW: [CANCELED] Publish OpenWebBeans 1.0.0-incubating-M1 > > but the release-tag will be on that branch in this case, isn't? So deleting > it afterwards is maybe not such a good idea. Imho all releases must have a > tag in the repo which exactly matches the released artifacts. But maybe I'm > too fussy. > > Anyway, it's probably better I let Gurkan do the release and only make the > changes in my local GIT archive. > > LieGrue, > strub > > > --- Kevan Miller <[email protected]> schrieb am Mo, 2.2.2009: > >> Von: Kevan Miller <[email protected]> >> Betreff: Re: AW: [CANCELED] Publish OpenWebBeans 1.0.0-incubating-M1 >> An: [email protected] >> Datum: Montag, 2. Februar 2009, 22:32 >> On Feb 2, 2009, at 4:08 PM, Mark Struberg wrote: >> >> > Gurkan, Kevan, should I wait with the SPI >> implementation as long as you do the release? >> >> I'd wait. >> >> One way you can handle this type of conflict, is to create >> a release branch (e.g. svn copy trunk branches/1.0.0-M1) and >> finalize the release. This allows new development to >> continue, even if release voting takes a while...). Does >> require merging of changes, if updates are made to the >> release branch. Since you don't really plan on >> supporting the M1 branch, you can delete it after the >> release vote passes... >> >> --kevan > > > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
