Supporting maintenance releases for our customers is one of the goals of IRIAN, so if you need a maintenance release for certain projects, I encourage you to take a look at the support contracts available from IRIAN.at.
regards, Martin On 12/21/06, Jeff Bischoff <[EMAIL PROTECTED]> wrote:
Aneesha Govil wrote: > I would second that. There is no way to apply bug-fix patches without > upgrading to a newer, "not-stable-yet" snapshot nightly build. > Well yes, unless you are comfortable applying the patches yourself and maintaining/building the source locally. While this will always be the preferred solution for a select few of the users, the broad majority of us would be much better served by official maintenance releases. Regards, Jeff Bischoff Kenneth L Kurz & Associates, Inc. Aneesha Govil wrote: > On 12/21/06, Jeff Bischoff <[EMAIL PROTECTED]> wrote: >> >> [...] >> The problem with this is >> that, despite lengthening your release cycle, you are still having >> trouble with release stability. In order to achieve this stability, you >> either need to be willing to branch for extensive testing before a >> release (even though it is meanwhile "getting out of date"). Or, you can >> take a look at ideas like Paul Spencer's idea for following a Tomcat >> style of release. >> >> If you're going to be releasing code that is only a few days or a week >> fresh from the trunk, then you're going to need to start releasing >> maintenance updates to gradually add to their stability. I'm just a >> humble user, but this is my 2 cents... > > > I would second that. There is no way to apply bug-fix patches without > upgrading to a newer, "not-stable-yet" snapshot nightly build. > > Regards, > Aneesha > > Regards, >> >> Jeff Bischoff >> Kenneth L Kurz & Associates, Inc. >> >> Thomas Spiegl wrote: >> > tomahawk 1.1.4 branch is quite out of date by now. I'd like to skip >> > this one, and start releasing core and tomahawk 1.1.5 asap. >> > >> > >> > On 12/18/06, Paul Spencer <[EMAIL PROTECTED]> wrote: >> >> This is yet another release status request. >> >> >> >> Current open issue with a Fix Version = 1.1.5-SNAPSHOT >> >> > MYFACES-1372 <h:messages> not shown (-> not working) >> >> ** Per an 8-Dec-2006 Posting from Mike Kienenberger: >> >> MYFACES-1372 <h:messages> not shown (-> not working) is important, >> >> but it's been broken for 18 months. It's not a regression as far as >> >> I know. >> >> >> >> > MYFACES-1409 incorrect behavior after RESTORE_VIEW >> responseComplete >> >> >> >> > MYFACES-1411 Lifecycle phase executions repetitions >> >> ** Per an 8-Dec-2006 Posting from Mike Kienenberger: >> >> MYFACES-1411 has I.P. issues. >> >> >> >> >> >> > MYFACES-1506 Translated messages in Messages.properties files >> >> ** Per an 8-Dec-2006 Posting from Mike Kienenberger: >> >> MYFACES-1506 is an improvement. It can be moved to 1.1.6. Actually, >> >> this is a Tomahawk issue, not a MyFaces one. Should be moved. Not >> >> sure how Messages.properties interacts with Tomahawk, though. >> >> >> >> >> >> None of the above issue are marked as blockers. Are any of the >> actually >> >> blockers to the 1.1.5 release? >> >> >> >> >> >> What is holding up this release? >> >> >> >> Paul Spencer >> >> >> >> >> > >> > >> >> >> >
-- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
