You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Thomas Spiegl <th...@gmail.com> on 2006/11/08 15:39:57 UTC
Core Release 1.1.5
We should release Core 1.1.5 soon, as it's needed for the next tomahawk release.
Therefore I tested the current trunk against Sun's TCK and fixed all
issues. MyFaces core is new 100 % compatible.
I have some time to prepare the release, but will need help from some
of you (eg. Wendy).
First of all I will create a branch for core 1.1.5 and shared 2.0.5
and start the release process.
-Thomas
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
Re: Core Release 1.1.5
Posted by Thomas Spiegl <th...@gmail.com>.
Yes, I will run the tests again.
On 11/9/06, Wendy Smoak <ws...@gmail.com> wrote:
> On 11/8/06, Mario Ivankovits <ma...@ops.co.at> wrote:
>
> > Hmmm ... but shared will be copied into the core (or tomahawk)
> > distribution - there is no shared.jar, so I see no advantage of *not*
> > upgrading to the latest shared. This should not introduce a
> > incompatibility with any other release. At least this was the idea.
> >
> > IMHO every release of tomahawk or core should always use the actual
> > shared, in the worst case, shared should be released at the same time as
> > core or tomahawk respectively.
>
> Up until yesterday, Core 1.1.5 was using Shared 2.0.4, and it was fine.
>
> Thomas, did you run the TCK before or after Martin's change? You
> might need to re-do it against Core 1.1.5 + Shared 2.0.5 if that's
> what we're going with.
>
> I'm vaguely concerned that there is code in Shared 2.0.5 that goes
> with the new Tomahawk code and possibly doesn't belong with Core
> 1.1.5. But I haven't been paying that much attention to commits, and
> it may not even be an issue.
>
> It's slightly less work all around if Core 1.1.5 and Tomahawk 1.1.4
> can use the same branch of Shared.
>
> It doesn't matter to me either way, I was just surprised to see the
> dependency version change with an explanation of "fixed", since as far
> as I know it wasn't a problem.
>
> Once it's decided, please update the Core 1.1.5 release plan and the
> project status document.
>
> --
> Wendy
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
Re: Core Release 1.1.5
Posted by Wendy Smoak <ws...@gmail.com>.
On 11/8/06, Mario Ivankovits <ma...@ops.co.at> wrote:
> Hmmm ... but shared will be copied into the core (or tomahawk)
> distribution - there is no shared.jar, so I see no advantage of *not*
> upgrading to the latest shared. This should not introduce a
> incompatibility with any other release. At least this was the idea.
>
> IMHO every release of tomahawk or core should always use the actual
> shared, in the worst case, shared should be released at the same time as
> core or tomahawk respectively.
Up until yesterday, Core 1.1.5 was using Shared 2.0.4, and it was fine.
Thomas, did you run the TCK before or after Martin's change? You
might need to re-do it against Core 1.1.5 + Shared 2.0.5 if that's
what we're going with.
I'm vaguely concerned that there is code in Shared 2.0.5 that goes
with the new Tomahawk code and possibly doesn't belong with Core
1.1.5. But I haven't been paying that much attention to commits, and
it may not even be an issue.
It's slightly less work all around if Core 1.1.5 and Tomahawk 1.1.4
can use the same branch of Shared.
It doesn't matter to me either way, I was just surprised to see the
dependency version change with an explanation of "fixed", since as far
as I know it wasn't a problem.
Once it's decided, please update the Core 1.1.5 release plan and the
project status document.
--
Wendy
Re: Core Release 1.1.5
Posted by Mario Ivankovits <ma...@ops.co.at>.
Hi Wendy!
> If not, Core 1.1.5 can stay at Shared 2.0.4 and can use the same
> Shared branch as Tomahawk 1.1.4.
Hmmm ... but shared will be copied into the core (or tomahawk)
distribution - there is no shared.jar, so I see no advantage of *not*
upgrading to the latest shared. This should not introduce a
incompatibility with any other release. At least this was the idea.
IMHO every release of tomahawk or core should always use the actual
shared, in the worst case, shared should be released at the same time as
core or tomahawk respectively.
Ciao,
Mario
Re: Core Release 1.1.5
Posted by Wendy Smoak <ws...@gmail.com>.
On 11/8/06, Wendy Smoak <ws...@gmail.com> wrote:
> Unless someone changed it, the trunk of Core (1.1.5-SNAPSHOT) still
> depends on the 2.0.4 branch of shared, so if all goes well we can use
> it for both Core and Tomahawk.
Martin changed the Shared dependency yesterday in r472050.
http://svn.apache.org/viewvc?view=rev&rev=472050
Was it changed for a reason, (are there changes on the trunk of Shared
that are needed by the trunk of Core?)
If not, Core 1.1.5 can stay at Shared 2.0.4 and can use the same
Shared branch as Tomahawk 1.1.4.
--
Wendy
Re: Core Release 1.1.5
Posted by Paul Spencer <pa...@apache.org>.
Wendy,
I have submitted a patch to correct the license headers for one of the
core maven projects [1]. As soon as it is committed, I will create
patches for the remaining maven projects.
FYI: I have an internal project that is waiting on the release, so I am
motivated to provided a patch for the remaining projects.
Paul Spencer
[1] http://issues.apache.org/jira/browse/MYFACES-1488?page=all
Wendy Smoak wrote:
> On 11/8/06, Thomas Spiegl <th...@gmail.com> wrote:
>
>> I have some time to prepare the release, but will need help from some
>> of you (eg. Wendy).
>>
>> First of all I will create a branch for core 1.1.5 and shared 2.0.5
>> and start the release process.
>
> We need to fix the license headers before branching, otherwise we'll
> have to do it twice.
>
> Unless someone changed it, the trunk of Core (1.1.5-SNAPSHOT) still
> depends on the 2.0.4 branch of shared, so if all goes well we can use
> it for both Core and Tomahawk.
>
> Please update the timeline on the release plan as you go along, so
> everyone stays informed:
>
> http://wiki.apache.org/myfaces/CoreRelease115
>
> There's also a status document that should be updated when a new
> branch is created:
>
> http://svn.apache.org/repos/asf/myfaces/current/STATUS.txt
>
> Thanks!
Re: Core Release 1.1.5
Posted by Wendy Smoak <ws...@gmail.com>.
On 11/8/06, Thomas Spiegl <th...@gmail.com> wrote:
> I have some time to prepare the release, but will need help from some
> of you (eg. Wendy).
>
> First of all I will create a branch for core 1.1.5 and shared 2.0.5
> and start the release process.
We need to fix the license headers before branching, otherwise we'll
have to do it twice.
Unless someone changed it, the trunk of Core (1.1.5-SNAPSHOT) still
depends on the 2.0.4 branch of shared, so if all goes well we can use
it for both Core and Tomahawk.
Please update the timeline on the release plan as you go along, so
everyone stays informed:
http://wiki.apache.org/myfaces/CoreRelease115
There's also a status document that should be updated when a new
branch is created:
http://svn.apache.org/repos/asf/myfaces/current/STATUS.txt
Thanks!
--
Wendy