Does anyone know how I can see all the commits I have made since the
1.1.4 release?
I'm running cardemo as a portlet on the same page as another JSF
portlet. This causes cardemo to break with 1.1.4.1.
1.1.4 Works
1.1.5 Works
1.1.4.1 Breaks
Wendy, I assume the patch branch is exactly what
On 1/8/07, Jeff Bischoff [EMAIL PROTECTED] wrote:
What will be the compatibility situation between Myfaces Core 1.1.4.1
and Tomahawk 1.1.4/1.1.5? Any trivial fixes we can backport to improve this?
I expect 1.1.4.1 to have the same compatibility as 1.1.4.
I'd like to keep 1.1.4.1 tightly
as another JSF
portlet. This causes cardemo to break with 1.1.4.1.
1.1.4 Works
1.1.5 Works
1.1.4.1 Breaks
Wendy, I assume the patch branch is exactly what was released with 1.1.4
including the shared_impl that went with it?
That's odd. 1.1.4.1 was copied from the 1.1.4 tag. If you haven't
made any
Awesome.
What will be the compatibility situation between Myfaces Core 1.1.4.1
and Tomahawk 1.1.4/1.1.5? Any trivial fixes we can backport to improve this?
Regards,
Jeff Bischoff
Kenneth L Kurz Associates, Inc.
Wendy Smoak wrote:
On 1/5/07, Stan Silvert [EMAIL PROTECTED] wrote:
Stan,
]
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: Friday, January 05, 2007 10:35 PM
To: MyFaces Development
Subject: Re: Patch Branch?
On 1/5/07, Stan Silvert [EMAIL PROTECTED] wrote:
Stan, do you have the JIRA issue and svn revision(s) for the
portlet
Awesome. I'll apply the patch on Sunday.
Stan Silvert
JBoss, a division of RedHat
[EMAIL PROTECTED]
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: Friday, January 05, 2007 10:35 PM
To: MyFaces Development
Subject: Re: Patch Branch?
On 1/5/07, Stan Silvert
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 [EMAIL PROTECTED] wrote:
Is their a reason NOT to release 1.1.5?
Yes. There
On 1/5/07, Paul Spencer [EMAIL PROTECTED] 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
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
.
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
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
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.
It's just core.
http://issues.apache.org/jira/browse/MYFACES-1481
OK, then we can use the released Shared 2.0.3
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 [EMAIL PROTECTED] 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
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
Hi Paul,
1) Mitigates the need for a 1.1.4.1 branch.
There is still some small value for orgs that want the one fix w/out the
inherit risk that comes with a new release of any piece of software. I do
agree with you that a 1.1.5 release would be a better use of resources though.
2) No need to
[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)
Dennis Byrne wrote:
Hi Paul,
1) Mitigates the need for a 1.1.4.1 branch.
There is still some small value for orgs that want the one fix w/out
the inherit risk that comes with a new release of any piece of
software. I do agree with you that a 1.1.5 release would be a better
use of resources
Hello,
is the new copyright policy a blocker for a 1.1.4.1 release?
See: http://www.apache.org/legal/src-headers.html
Regards
Bernd
Paul Spencer wrote:
Dennis Byrne wrote:
Hi Paul,
1) Mitigates the need for a 1.1.4.1 branch.
There is still some small value for orgs that want the one
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
On 1/4/07, Paul Spencer [EMAIL PROTECTED] 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.
--
On 1/4/07, Bernd Bohmann [EMAIL PROTECTED] wrote:
is the new copyright policy a blocker for a 1.1.4.1 release?
See: http://www.apache.org/legal/src-headers.html
Yes, but it's fairly simple to fix. I think the Maven developers have
been using an IDEA plugin to do it, and there are some
21 matches
Mail list logo
