FYI, we're taking extra time on 4.0.2 to bring it up from a
development release to a stable release. That process is taking
several weeks of extra work. Our current target is the end of October,
but that may slip if 4.0.2 is not ready by then.
-- Scott
Scott,
Any possibility of getting a snapshot ahead of the end of October, or is that
an impossibility due to regressions, etc?
The main reason I ask is because we'd love to do further testing of the 4.0
line in our QA environment, but the previously-resolved bug (3673) causes one
of our sites
Thanks for the update.
Would it be helpful if we filed bugs against trunk? I tried it out a
week ago but pretty quickly ran into a problem (@Named @RequestScoped
didn't show up in the request attrs). I figured you guys were still
working on it and probably didn't need the distraction, but if it
On Oct 12, 2009, at 1:06 PM, Jeff Schnitzer wrote:
Thanks for the update.
Would it be helpful if we filed bugs against trunk? I tried it out a
week ago but pretty quickly ran into a problem (@Named @RequestScoped
didn't show up in the request attrs). I figured you guys were still
working
On Oct 12, 2009, at 9:49 AM, Jamison Novak wrote:
Scott,
Any possibility of getting a snapshot ahead of the end of October,
or is that an impossibility due to regressions, etc?
The main reason I ask is because we'd love to do further testing of
the 4.0 line in our QA environment, but
