You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Stan Silvert <st...@jboss.com> on 2007/01/04 22:17:24 UTC

Patch Branch?

Are we maintaining a "service pack" type of branch for MyFaces 1.1.4
core?  There is a critical portlet bug that is fixed in 1.1.5, but I
don't think we are planning a 1.1.5 release any time soon.

 

What do you guys think of starting an SP branch for critical fixes (if
we don't already have one)?

 

Stan Silvert

JBoss, a division of RedHat

ssilvert@jboss.com

 


Re: Patch Branch?

Posted by Paul Spencer <pa...@apache.org>.
Mike Kienenberger wrote:
>> [release 1.1.5 now instead]
>> 1) Mitigates the need for a 1.1.4.1 branch.
> 
> Not really.   In all likelihood, there are always going to be bugs in
> the latest release since new features are constantly being worked on.
> Users want to have access to a bug-fix release that does not add new
> features.
> 

Point taken.

>> 2) No need to run the TCK prior to the release.
> 
> We have to run the TCK on all releases, whether 1.1.5 or 1.1.4.1.
>

I understand this for release we announce as stable, but can we cut a 
release we believe will pass the TCK, and only announce it as stable 
after it passes the TCK.  Granted we may have gaps in the list of stable 
version number, but this is what tomcat does today.

>> 3) A release is a sign of progress to the community.
> 
>> From the email I've received both on and off list, the community would
> consider bug fix releases a more practical sign of progress.
> 

Point taken.

>> 4) Allows Maven based project currently using 1.1.5 functionality
>>     a version of MyFaces they can use in a release.  (I am in this 
>> position)
> 
> Irrelevent.   Having a bug fix release of 1.1.4.1 should not impact a
> release of 1.1.5.
> 
> 

Point taken.

 >
 >

<snip>


Paul Spencer

Re: Patch Branch?

Posted by Mike Kienenberger <mk...@gmail.com>.
> [release 1.1.5 now instead]
> 1) Mitigates the need for a 1.1.4.1 branch.

Not really.   In all likelihood, there are always going to be bugs in
the latest release since new features are constantly being worked on.
Users want to have access to a bug-fix release that does not add new
features.

> 2) No need to run the TCK prior to the release.

We have to run the TCK on all releases, whether 1.1.5 or 1.1.4.1.

> 3) A release is a sign of progress to the community.

>From the email I've received both on and off list, the community would
consider bug fix releases a more practical sign of progress.

> 4) Allows Maven based project currently using 1.1.5 functionality
>     a version of MyFaces they can use in a release.  (I am in this position)

Irrelevent.   Having a bug fix release of 1.1.4.1 should not impact a
release of 1.1.5.


On 1/4/07, Paul Spencer <pa...@apache.org> wrote:
> Is their a reason NOT to release 1.1.5?
>
> Based on a Tomcat style release model I purposed earlier [1] we can
> label this release Alpha status and change it's status later.
> Assuming the current source is stable, which it appeared to be as
> of this weekend, we can release it meets the requirement for Alpha status.
>
> Advantages:
> 1) Mitigates the need for a 1.1.4.1 branch.
>
> 2) No need to run the TCK prior to the release.
>
> 3) A release is a sign of progress to the community.
>
> 4) Allows Maven based project currently using 1.1.5 functionality
>     a version of MyFaces they can use in a release.  (I am in this position)
>
> Paul Spencer
>
>
> [1] http://www.mail-archive.com/dev@myfaces.apache.org/msg19257.html
>
>
>
> Stan Silvert wrote:
> > Are we maintaining a "service pack" type of branch for MyFaces 1.1.4
> > core?  There is a critical portlet bug that is fixed in 1.1.5, but I
> > don't think we are planning a 1.1.5 release any time soon.
> >
> >
> >
> > What do you guys think of starting an SP branch for critical fixes (if
> > we don't already have one)?
> >
> >
> >
> > Stan Silvert
> >
> > JBoss, a division of RedHat
> >
> > ssilvert@jboss.com
> >
> >
> >
> >
>
>

Re: Status of Issue MYFACES-1411 (was Re: Patch Branch?)

Posted by Wendy Smoak <ws...@gmail.com>.
On 1/5/07, Paul Spencer <pa...@mindspring.com> wrote:

> Wendy,
> Is this a blocker or just one we really would like to have fixed prior
> to a 1.1.5 release?
>
> If it is a blocker, please update the issue accordingly.

I think it is, but it's up to the MyFaces PMC to decide.  I have not
changed the priority because it will likely send an email to the
contributor, and I don't want to make waves if someone is already in
contact with him.

-- 
Wendy

Status of Issue MYFACES-1411 (was Re: Patch Branch?)

Posted by Paul Spencer <pa...@mindspring.com>.
Wendy,
Is this a blocker or just one we really would like to have fixed prior
to a 1.1.5 release?

If it is a blocker, please update the issue accordingly.

Paul Spencer

Wendy Smoak wrote:
> On 1/4/07, Paul Spencer <pa...@apache.org> wrote:
> 
>> Is their a reason NOT to release 1.1.5?
> 
> 
> Yes.  There are still open issues for 1.1.5.  MYFACES-1411 is the one
> that concerns me.  I'm not familiar with the situation, I just flagged
> it as a contribution of new classes with no CLA on file.
> 


Re: Patch Branch?

Posted by Wendy Smoak <ws...@gmail.com>.
On 1/4/07, Paul Spencer <pa...@apache.org> wrote:

> Is their a reason NOT to release 1.1.5?

Yes.  There are still open issues for 1.1.5.  MYFACES-1411 is the one
that concerns me.  I'm not familiar with the situation, I just flagged
it as a contribution of new classes with no CLA on file.

-- 
Wendy

Re: Patch Branch?

Posted by Paul Spencer <pa...@apache.org>.
Is their a reason NOT to release 1.1.5?

Based on a Tomcat style release model I purposed earlier [1] we can
label this release Alpha status and change it's status later.
Assuming the current source is stable, which it appeared to be as
of this weekend, we can release it meets the requirement for Alpha status.

Advantages:
1) Mitigates the need for a 1.1.4.1 branch.

2) No need to run the TCK prior to the release.

3) A release is a sign of progress to the community.

4) Allows Maven based project currently using 1.1.5 functionality
    a version of MyFaces they can use in a release.  (I am in this position)

Paul Spencer


[1] http://www.mail-archive.com/dev@myfaces.apache.org/msg19257.html



Stan Silvert wrote:
> Are we maintaining a "service pack" type of branch for MyFaces 1.1.4
> core?  There is a critical portlet bug that is fixed in 1.1.5, but I
> don't think we are planning a 1.1.5 release any time soon.
> 
>  
> 
> What do you guys think of starting an SP branch for critical fixes (if
> we don't already have one)?
> 
>  
> 
> Stan Silvert
> 
> JBoss, a division of RedHat
> 
> ssilvert@jboss.com
> 
>  
> 
> 


Re: Patch Branch?

Posted by Mike Kienenberger <mk...@gmail.com>.
We don't have one.
It's frequently requested.

+1 on creating a 1.1.4.1 maintenance branch.

On 1/4/07, Stan Silvert <st...@jboss.com> wrote:
>
>
>
>
> Are we maintaining a "service pack" type of branch for MyFaces 1.1.4 core?
> There is a critical portlet bug that is fixed in 1.1.5, but I don't think we
> are planning a 1.1.5 release any time soon.
>
>
>
> What do you guys think of starting an SP branch for critical fixes (if we
> don't already have one)?
>
>
>
> Stan Silvert
>
> JBoss, a division of RedHat
>
> ssilvert@jboss.com
>
>