Ok. I see where you're going. I also don't want 1.1.5 delayed because of the next release version number. And even if we pick 1.1.6 now, we can release it as 1.6 later. My preference is 1.1.6, but if I'm the only one that feels this way, use 1.6.
On 2/23/07, Paul Spencer <[EMAIL PROTECTED]> wrote:
Mike, As a part of the 1.1.5 release, the next version is set. Based on your comments, the version should be set to 1.1.6. I have no problem with this. The release of 1.1.5 should not be delayed while we determine the next version number. Paul Spencer Mike Kienenberger wrote: > I think it's too soon to be making the decision on what to call the > next version. Let's wait and see how things go with a Tomahawk 1.1.5 > release. We're still encountering dependency issues with current > Tomahawk releases. We've promised to deliver > implementation-dependent releases twice in the past and failed. > Let's wait and see before making that promise again. > > On 2/23/07, Paul Spencer <[EMAIL PROTECTED]> wrote: >> Mike, >> As soon as Tomahawk is compatible with the JSF 1.1 spec, then it should >> be considered implementation independent. If their are known >> incompatibilities with an implementation, i.e. MyFaces 1.1.4, then those >> should be noted in Tomahawk's release notes. >> >> We can make the testing easer by defining implementation specific >> profiles for testing Tomahawk against different MyFaces versions, and >> any other JSF implementations, using profiles. This is currently done >> in Tomahawk's example pom.xml. See the "Deploy with Sun's RI" section >> of the Selenium testing page [1]. >> >> Keeping in mind we may want to change the answer in the future, what >> should the next version be? >> >> __ 1.6.0 - JSF 1.1 implementation independent >> __ 1.1.6 - Dependent on MyFaces 1.1.6 >> >> Paul Spencer >> >> [1] http://myfaces.apache.org/tomahawk/testing/selenium.html >> >> >> >> Mike Kienenberger wrote: >> > I don't think Tomahawk has proved yet that it is independent from core >> > versioning. Take the MyFaces Core 1.1.4 incompatiblities between >> > Tomahawk 1.1.5 as an example. >> > >> > I think we should take a "wait and see" attitude before we decide >> > we're going to start with Tomahawk 1.6 numbering. Remember, we >> > started with Tomahawk 1.1.3 as "independent of core" and we've still >> > not accomplished the task with releases to date. >> > >> > And if it's truely independent from the core, then it would mean that >> > someone could use Tomahawk 1.1.5 for any version of MyFaces, 1.1.4, >> > 1.1.3, 1.1.2, 1.1.1, 1.0.9, etc., and we know that's not the case. >> > >> > -Mike >> > >> > On 2/23/07, Paul Spencer <[EMAIL PROTECTED]> wrote: >> >> This is to summarize the version number discussion. >> >> >> >> MyFaces for JSF 1.1 >> >> 1.1.5 - Current Release (Announced 19-Feb-2007) >> >> 1.1.6 - Next release not currently scheduled >> >> >> >> MyFaces for JSF 1.2 >> >> 2.0.0 - Currently being developed as MyFaces 1.2 >> >> >> >> MyFaces for JSF 2.0 / JSF 6 >> >> 3.0.0 - ? >> >> >> >> Tomahawk for JSF 1.1 >> >> 1.1.3 - Current Release (Announced 14-Jun-2006) >> >> 1.1.5 - Next release, currently in process >> >> 1.6.0 - Following release >> >> >> >> Tomahawk for JSF 1.2 >> >> 2.x - Not started >> >> >> >> Paul Spencer >> >> >> >> >> >> >> > >> >> >
