[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 <[EMAIL PROTECTED]> 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
>
> [EMAIL PROTECTED]
>
>
>
>
