I believe they're related. I believe I can, they used to work.
Will you be able to get to them John?On Tue, Dec 13, 2011 at 18:46, John D. Ament <john.d.ament@gmail.com> wrote:
SEAMJMS 61/62 are considered blockers. I think 49 is now resolved though.On Tue, Dec 13, 2011 at 7:17 PM, Shane Bryzak <sbryzak@redhat.com> wrote:
We're now down to 18 issues. I'll be bumping these tomorrow if they're still not resolved, so if you would like to get any of them included in the 3.1 release please let me know.
On 11/12/11 21:49, Shane Bryzak wrote:Hi everyone,
I'm pleased to say that we're down to just 25 open issues for the 3.1 Final release. Here's the filtered list in JIRA:
https://issues.jboss.org/secure/IssueNavigator.jspa?mode=hide&requestId=12314291
If any of these issues are assigned to you however you don't think you'll have time to address them in the next couple of days, could you please let me know and we'll either find someone to help out, or see if we can postpone the issue for the next release. If you don't have any issues assigned to you but would like to help out anyway, likewise please let us know and we'll find something for you to do. ;)
Thanks!
Shane
_______________________________________________
seam-dev mailing list
seam-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
_______________________________________________
seam-dev mailing list
seam-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
--
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp
Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling
PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu