You are viewing a plain text version of this content. The canonical link for it is here.
Posted to adffaces-dev@incubator.apache.org by Matthias Wessendorf <ma...@apache.org> on 2007/01/12 18:18:47 UTC
release plan
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
Re: release plan
Posted by Simon Lessard <si...@gmail.com>.
Sounds good to me,
Furthermore this semester won't be as crazy as last one for me so I should
be able to be less useless. Hopefully I'll be able to do some cleaning work
to reduce a good chunk of Java 5 warnings before we release.
Regards,
~ Simon
On 1/13/07, Matthias Wessendorf <ma...@apache.org> wrote:
>
> yes!
> thanks. that is much more detailed than my old proposal. I put it
> together in a wiki page
>
> http://wiki.apache.org/myfaces/TrinidadReleasePlans
>
>
>
> On 1/13/07, Adam Winer <aw...@gmail.com> wrote:
> > 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 <br...@gmail.com> 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 <ma...@apache.org> 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
> > > >
> > >
> > >
> >
> >
>
>
> --
> Matthias Wessendorf
> http://tinyurl.com/fmywh
>
> further stuff:
> blog: http://jroller.com/page/mwessendorf
> mail: mwessendorf-at-gmail-dot-com
>
RE: release plan
Posted by Daniel Hannum <dh...@quovadx.com>.
Right, thanks.
Dan
-----Original Message-----
From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of
Matthias Wessendorf
Sent: Monday, January 15, 2007 9:26 AM
To: adffaces-dev@incubator.apache.org
Subject: Re: release plan
this is first on the release plan.
after we have released a m1 of trinidad (core and plugins),
we can start on talking again about getting out of incubator.
A release is a proof of being able to develop a product in the open
source
manner ;)
-M
On 1/15/07, Daniel Hannum <dh...@quovadx.com> wrote:
> Are we talking about a release plan to get out of incubator? Or a
> release plan to release the next snapshot?
>
> -----Original Message-----
> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf
Of
> Matthias Wessendorf
> Sent: Saturday, January 13, 2007 1:30 AM
> To: adffaces-dev@incubator.apache.org
> Subject: Re: release plan
>
> yes!
> thanks. that is much more detailed than my old proposal. I put it
> together in a wiki page
>
> http://wiki.apache.org/myfaces/TrinidadReleasePlans
>
>
>
> On 1/13/07, Adam Winer <aw...@gmail.com> wrote:
> > 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 <br...@gmail.com> 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 <ma...@apache.org> 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
> > > >
> > >
> > >
> >
> >
>
>
> --
> Matthias Wessendorf
> http://tinyurl.com/fmywh
>
> further stuff:
> blog: http://jroller.com/page/mwessendorf
> mail: mwessendorf-at-gmail-dot-com
>
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: release plan
Posted by Matthias Wessendorf <ma...@apache.org>.
this is first on the release plan.
after we have released a m1 of trinidad (core and plugins),
we can start on talking again about getting out of incubator.
A release is a proof of being able to develop a product in the open source
manner ;)
-M
On 1/15/07, Daniel Hannum <dh...@quovadx.com> wrote:
> Are we talking about a release plan to get out of incubator? Or a
> release plan to release the next snapshot?
>
> -----Original Message-----
> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of
> Matthias Wessendorf
> Sent: Saturday, January 13, 2007 1:30 AM
> To: adffaces-dev@incubator.apache.org
> Subject: Re: release plan
>
> yes!
> thanks. that is much more detailed than my old proposal. I put it
> together in a wiki page
>
> http://wiki.apache.org/myfaces/TrinidadReleasePlans
>
>
>
> On 1/13/07, Adam Winer <aw...@gmail.com> wrote:
> > 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 <br...@gmail.com> 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 <ma...@apache.org> 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
> > > >
> > >
> > >
> >
> >
>
>
> --
> Matthias Wessendorf
> http://tinyurl.com/fmywh
>
> further stuff:
> blog: http://jroller.com/page/mwessendorf
> mail: mwessendorf-at-gmail-dot-com
>
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
RE: release plan
Posted by Daniel Hannum <dh...@quovadx.com>.
Are we talking about a release plan to get out of incubator? Or a
release plan to release the next snapshot?
-----Original Message-----
From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com] On Behalf Of
Matthias Wessendorf
Sent: Saturday, January 13, 2007 1:30 AM
To: adffaces-dev@incubator.apache.org
Subject: Re: release plan
yes!
thanks. that is much more detailed than my old proposal. I put it
together in a wiki page
http://wiki.apache.org/myfaces/TrinidadReleasePlans
On 1/13/07, Adam Winer <aw...@gmail.com> wrote:
> 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 <br...@gmail.com> 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 <ma...@apache.org> 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
> > >
> >
> >
>
>
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: release plan
Posted by Matthias Wessendorf <ma...@apache.org>.
yes!
thanks. that is much more detailed than my old proposal. I put it
together in a wiki page
http://wiki.apache.org/myfaces/TrinidadReleasePlans
On 1/13/07, Adam Winer <aw...@gmail.com> wrote:
> 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 <br...@gmail.com> 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 <ma...@apache.org> 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
> > >
> >
> >
>
>
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: release plan
Posted by Adam Winer <aw...@gmail.com>.
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 <br...@gmail.com> 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 <ma...@apache.org> 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
> >
>
>
Re: release plan
Posted by Bruno Aranda <br...@gmail.com>.
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 <ma...@apache.org> 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
>