Shane, could you provide a link to this report. You should be able to make
any JIRA filter publically viewable.
-Dan
On Wed, Mar 23, 2011 at 04:40, Shane Bryzak <sbryzak(a)redhat.com> wrote:
In the interest of brevity, here's a link to a shared filter in JIRA
that displays the remaining open issues. Since my last update, we've
slipped a little bit - we're now up to 62 issues.
https://issues.jboss.org/secure/IssueNavigator.jspa?mode=hide&request...
<https://issues.jboss.org/secure/IssueNavigator.jspa?mode=hide&request...
In regards to the Glassfish issues, we're taking the following steps:
1) Created a new compatibility module -
https://github.com/seam/compatibility
This module will consist of tests solely designed to test the
compatibility of a container. We currently have tests in Solder (and
other modules) that test compatibility issues, these tests will be moved
into the compatibility module and we'll be creating new tests as we come
across undiscovered issues. The intent is for the QE guys to take
ownership of this module so that we have a single set of tests that we
can run in various containers to check for compliance.
2) Document all known compatibility issues in one place
Dan has made a start on this already - see
http://seamframework.org/Seam3/Compatibility
<http://seamframework.org/Seam3/CompatibilityHome>. This page is the
definitive source on compatibility issues, and should contain all our
notes and research about known issues. Ideally, we should have JIRA
links for each issue that's listed on this page.
It's my intent that these issues with Glassfish don't hold up the 3.0
Final release. There will be some definite problems with running Seam
in a GF container, however we've reached the point where there are no
reasonable workarounds for some of the newly discovered issues. We are
going to continue our research efforts and do our best to collaborate
with the Glassfish developers to resolve these issues, however our
message should be that Seam 3 is compliant with the CDI specification,
and any issues with using it in Glassfish are due to bugs in Glassfish
itself. Please don't blog or tweet about any of this at the moment
until we have a chance to touch base with the Glassfish team to make
them aware of the issues.
Thanks,
Shane
On 23/03/11 18:40, Shane Bryzak wrote:
I've decided to update the list twice a day, to be a bit more
granular. The good news is we're already down to 59 issues. The bad
news is that a potentially serious Glassfish issue has popped up. At
the moment we're still in the research phase, but as soon as we have
something more concrete I'll post an update.
https://issues.jboss.org/secure/IssueNavigator.jspa?mode=hide&request...
<https://issues.jboss.org/secure/IssueNavigator.jspa?mode=hide&request...
We've made some nice progress and I'm pleased to say we're down to 32
issues. Here's a couple of breakdowns:
By module:
SEAM: 7 issues
SEAMCATCH: 2 issues
SEAMFACES: 5 issues
SEAMINTL: 3 issues
SEAMREMOTING: 2 issues
SEAMREST: 3 issues
SEAMSECURITY: 4 issues
SEAMSERVLET: 2 issues
SEAMWICKET: 2 issues
SOLDER: 2 issues
By assignee:
Jose Freitas: 1
Shane Bryzak: 6
Dan Allen: 5
Jozef Hartinger: 9
Jason Porter: 2
Martin Gencur: 1
Brian Leathem: 3
Ken Finnigan: 3
Unassigned: 2
The module spread is quite evenly distributed, which is good. As for
issues per assignee, Jozef has by far the most so if you have some spare
time and are able to help him out then please step up.
I'll be sending out another update this evening (my time), so keep up
the good work! Let's try to get this down to less than 10 by the end of
tomorrow.
Shane
We are now at 16. Less than 24 hours ago, we were at 68. The IRC channel has
been on fire. Amazing work everyone! I've been at decent companies where
this many issues weren't addressed in a month. Many hands make light work,
as my (large) family always says.
-Dan
On Thu, Mar 24, 2011 at 19:34, Shane Bryzak <sbryzak(a)redhat.com> wrote:
https://issues.jboss.org/secure/IssueNavigator.jspa?mode=hide&request...
<
https://issues.jboss.org/secure/IssueNavigator.jspa?mode=hide&request...
>
We've made some nice progress and I'm pleased to say we're down to 32
issues. Here's a couple of breakdowns:
By module:
SEAM: 7 issues
SEAMCATCH: 2 issues
SEAMFACES: 5 issues
SEAMINTL: 3 issues
SEAMREMOTING: 2 issues
SEAMREST: 3 issues
SEAMSECURITY: 4 issues
SEAMSERVLET: 2 issues
SEAMWICKET: 2 issues
SOLDER: 2 issues
By assignee:
Jose Freitas: 1
Shane Bryzak: 6
Dan Allen: 5
Jozef Hartinger: 9
Jason Porter: 2
Martin Gencur: 1
Brian Leathem: 3
Ken Finnigan: 3
Unassigned: 2
The module spread is quite evenly distributed, which is good. As for
issues per assignee, Jozef has by far the most so if you have some spare
time and are able to help him out then please step up.
I'll be sending out another update this evening (my time), so keep up
the good work! Let's try to get this down to less than 10 by the end of
tomorrow.
Shane
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
project in
(SEAM,SEAMCATCH,SOLDER,SEAMXML,SEAMPERSIST,SEAMINTL,SEAMFACES,SEAMREMOTING,SEAMSERVLET,SEAMREST,SEAMVALIDATE,SEAMWICKET,SEAMSECURITY)
AND issuetype in standardIssueTypes() AND resolution = Unresolved and
fixVersion="3.0.0.Final" ORDER BY key ASC
note the: resolution = Unresolved
-Dan
On Fri, Mar 25, 2011 at 17:20, Dan Allen <dan.j.allen(a)gmail.com> wrote:
On Fri, Mar 25, 2011 at 16:41, Jozef Hartinger
<jharting(a)redhat.com>wrote:
> The filter hides "Reopened" issues.
>
Doh! I *hate* JIRA for that.
Instead of searching for open issues, you should always search for
unresolved issues (different field). That covers all ways an issue can be
open.
-Dan
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://www.google.com/profiles/dan.j.allen#abouthttp://mojavelinux.comhttp://mojavelinux.com/seaminaction
I've updated the filter as Dan suggested. Unfortunately it brought us
back up to 16 issues. Fortunately, we've just fixed another 4 so we're
down to 12 issues now. Can't stop the momentum!
On 26/03/11 07:24, Dan Allen wrote:
project in
(SEAM,SEAMCATCH,SOLDER,SEAMXML,SEAMPERSIST,SEAMINTL,SEAMFACES,SEAMREMOTING,SEAMSERVLET,SEAMREST,SEAMVALIDATE,SEAMWICKET,SEAMSECURITY)
AND issuetype in standardIssueTypes() AND resolution = Unresolved and
fixVersion="3.0.0.Final" ORDER BY key ASC
note the: resolution = Unresolved
-Dan
On Fri, Mar 25, 2011 at 17:20, Dan Allen <dan.j.allen(a)gmail.com
<mailto:dan.j.allen@gmail.com>> wrote:
On Fri, Mar 25, 2011 at 16:41, Jozef Hartinger
<jharting(a)redhat.com <mailto:jharting@redhat.com>> wrote:
The filter hides "Reopened" issues.
Doh! I *hate* JIRA for that.
Instead of searching for open issues, you should always search for
unresolved issues (different field). That covers all ways an issue
can be open.
-Dan
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://www.google.com/profiles/dan.j.allen#abouthttp://mojavelinux.comhttp://mojavelinux.com/seaminaction
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://www.google.com/profiles/dan.j.allen#abouthttp://mojavelinux.comhttp://mojavelinux.com/seaminaction
Thank you everyone for the huge effort over the last few days. I'm
pleased to say that we're down to just 1 issue remaining, and both Dan
and I are now busy writing the last few chapters of documentation for
the release. If anyone isn't totally exhausted yet, you may wish to
spend a little bit of time over the next 10 or so hours checking over
your docs, otherwise go and drink some beer! I'll be announcing the
code freeze either late tonight (Aussie time) or tomorrow morning, after
which I'll start releasing the modules to the staging repository. After
that, we'll give QE a couple more days to review the artifacts and
staged distribution, then when they give us the all clear we'll push the
modules out to the release repository.
I especially want to thank everyone for giving up their personal time
(including their weekend, I know there's a few of you) to help eliminate
our remaining issues in what I think is a record amount of time. I
don't think I've ever seen so many issues resolved in such a short time
before. :)
Good job everyone.
Shane