And, I'd love to have the JSF 1.2 version released too - plugins and Trinidad itself - 'cause that's what I'm spending most of my time working with these days.
I think that the full process for release should be: FOR PLUGINS: - Create m1 branch of plugins - Update version in POM of plugins trunk to m2-SNAPSHOT - Vote on releasing plugins, if approved by incubator, then: - Update version in POMs of m1 branch to remove SNAPSHOT - Release plugins BETWEEN THE PLUGINS AND TRINIDAD: - Update Trinidad trunk to point at m1, non-snapshot plugins *or* to m2-SNAPSHOT, depending on how confident we are FOR TRINIDAD: - create m1 branch of Trinidad - Update version in POM of Trinidad trunk to m2-SNAPSHOT - Vote on releasing Trinidad, if approved by incubator - Update version in POMs of m1 branch to remove SNAPSHOT - Release Trinidad These'll be consecutive, but in the future should in theory be totally disconnected. How's this sound? -- Adam On 1/12/07, Bruno Aranda <[EMAIL PROTECTED]> wrote:
Yes, thanks Matthias for opening the thread. As you point out, we will need to have the jsf 1.2 maven-faces-plugin released when the jsf myfaces implementation is ready. Cheers, Bruno On 12/01/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > > Hi, > > I have the following release plan in mind: > > -getting the JSF 1.1 plugins release out > (needs approval by the Incubator PMC) > -making Trinidad core (the /trinidad folder) depend on them and deploy > a RC for the M1 of core > -getting the JSF 1.1 core release out > (needs approval by the Incubator PMC) > > doing the same procedure for the JSF 1.2 bits. Why JSF 1.2? Because > your friends at MyFaces currently working on JSF 1.2 release and at > least they need a *release* version of the JSF 1.2 plugins to get a > RC1 out for that. An Apache policy says "no -SNAPSHOT dependencies" in > a release. > > comments? > > -M > > > -- > Matthias Wessendorf > http://tinyurl.com/fmywh > > further stuff: > blog: http://jroller.com/page/mwessendorf > mail: mwessendorf-at-gmail-dot-com >
