RE: Core Release 1.1.5
Great news! How about the current blocking issues for core 1.1.5? Shouldn't they be fixed first? E.g. https://issues.apache.org/jira/browse/MYFACES-1488 -- ASF source header + copyright notice And https://issues.apache.org/jira/browse/MYFACES-1479 -- SerialFactory breaks portlet bridge Also there are some 1.1.5 issues with patch available status. Any chance that these might be included? Regards, Erik-Berndt Scheper -Oorspronkelijk bericht- Van: Thomas Spiegl [mailto:[EMAIL PROTECTED] Verzonden: woensdag 8 november 2006 15:40 Aan: MyFaces Development Onderwerp: 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 Disclaimer: This message contains information that may be privileged or confidential and is the property of Sogeti Nederland B.V. or its Group members. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Re: Core Release 1.1.5
On 11/8/06, Thomas Spiegl [EMAIL PROTECTED] 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
Re: Core Release 1.1.5
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 [EMAIL PROTECTED] 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
On 11/8/06, Wendy Smoak [EMAIL PROTECTED] 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=revrev=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
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
On 11/8/06, Mario Ivankovits [EMAIL PROTECTED] 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
Yes, I will run the tests again. On 11/9/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 11/8/06, Mario Ivankovits [EMAIL PROTECTED] 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
