On 02/03/2011, at 11:53 AM, Dan Allen wrote: > On Tue, Mar 1, 2011 at 14:52, Brian Leathem <[email protected]> wrote: > > Some of these issues have been already resolved in Weld, and can be > worked around by using a Weld SNAPSHOT. However, it is probable that > more issues will arise as more people start using Seam 3, and a quick > turnaround on Weld releases would help greatly with user acceptance of > Seam 3. It would also bode well for containers that were quick to adopt > the Weld maintenance releases. > > > I want to emphasize how critical it is that we keep problems at bay as we > near the first release of Seam 3. We've really asked the growing Seam 3 user > community to stomach a lot of complications and thus far, they've been > hanging in there and working around the problems. But we need to get these > problems behind us, swiftly, and let them focus on their real business > problems and not exceptions. It doesn't just help the acceptance of Seam 3, > it's crucial to it. > > -Dan
I agree, to the best of my knowledge every other RI that is part of EE does regular maintenance releases, and I think we should as well. I think to do otherwise will just hurt adoption. Stuart > > -- > Dan Allen > Principal Software Engineer, Red Hat | Author of Seam in Action > Registered Linux User #231597 > > http://www.google.com/profiles/dan.j.allen#about > http://mojavelinux.com > http://mojavelinux.com/seaminaction > > _______________________________________________ > weld-dev mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/weld-dev
_______________________________________________ weld-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/weld-dev
