On 1/5/07, Sean Schofield <[EMAIL PROTECTED]> wrote:

A patch release certainly would be a good idea but it takes time and
resources to pull off each release.  Its probably worth the effort
since we tend to shoot ourselves in the foot when we release a whole
set of features that sometimes contain radical changes and have not
been tested extensively.

Although it takes more effort, it might be nice to always have a patch
branch available and then have an informal discussion on the dev list
about which fixes belong in the patch vs. the next major release.  Its
the major refactoring that tends to cause problems due to our lack of
unit tests.


FWIW, this is the path we're going to follow for Shale.  The 1.0.4 release
is about to happen (vote in progress), and we created a SHALE_1_0_X branch
to allow us to do any patch releases needed (1.0.5, ...).  Feature
development (towards a 1.1 release) will *only* happen on the trunk, so the
fact that the trunk might be unstable at a particular point in time will
have no effect on our ability to, say, fix a security vulnerability quickly.

Craig


Sean

On 1/5/07, Stan Silvert <[EMAIL PROTECTED]> wrote:
> > Stan, do you have the JIRA issue and svn revision(s) for the portlet
> > bug fix?  I need to know if it affects Shared or just Core.
> >
> > --
> > Wendy
>
> It's just core.
>
> http://issues.apache.org/jira/browse/MYFACES-1481
>
>
>

Reply via email to