12:30 p.m.
After Sep/14th and until Beta3 is out we'll only be updating libs in order to fix
bugs.
Take a look at the following JIRA to make sure your work on a particular library is
properly
recorded/linked:
http://jira.jboss.com/jira/browse/JBAS-4562
--------------------------------------------------------------------
Also, for the next AS5 CRx release make sure any library updates are recorded here:
http://jira.jboss.com/jira/browse/JBAS-4647
(e.g. discussions about jbroups 2.6)
--------------------------------------------------------------------
The current Beta3 status is summarized below:
- MC 2.0.0.Beta4 and dependencies have been resolved/tagged.
- Snapshots that need to be replaced with tagged releases.
What's currently left:
<componentref name="jboss/jboss-ejb3-cache"
version="0.11-SNAPSHOT"/>
<componentref name="jboss/jboss-jaspi-api"
version="1.0-SNAPSHOT"/>
<componentref name="jboss/jboss-security-spi"
version="2.0.1-SNAPSHOT"/>
<componentref name="jboss/jbosssx" version="2.0.1-SNAPSHOT"/>
<componentref name="jboss/jbosssx-client"
version="2.0.1-SNAPSHOT"/>
- Waiting for AOP 2.0.0.beta + Javassist 3.6.0.CR2
- JBoss Transactions
(now at 4.2.3.SP5) to be updated to a 4.3.x version that implements JTA 1.1
- JBoss Messaging
waiting for the final 1.4.0.GA release
- JGroups. It's still questionable at this point if we can move to v2.5 (from
2.4.1.SP3) due
to the JBoss Messaging dependency
- Hibernate Validator
We'll be probably adding this, as it is now an independent package.
If you have any comments/concerns let me know.
Cheers
/Dimitris
1:54 p.m.
Dimitris Andreadis wrote:
- JGroups. It's still questionable at this point if we can move
to
v2.5 (from 2.4.1.SP3) due to the JBoss Messaging dependency
Why ? 2.5 is backward
compatible, so JBoss Messaging should have no
issues with this, even if they use 2.5 as a better 2.4. Tim, can you
comment ?
I strongly recommend 2.5 for inclusion, or else we'll have to wait until
JBoss 6 to include it. Customers would upgrade to 2.5 independently,
causing headaches for the support team.
--
Bela Ban
Lead JGroups / Clustering Team
JBoss - a division of Red Hat
2:40 p.m.
Bela Ban wrote:
Dimitris Andreadis wrote:
> - JGroups. It's still questionable at this point if we can move to
> v2.5 (from 2.4.1.SP3) due to the JBoss Messaging dependency
Why ? 2.5 is backward compatible, so JBoss Messaging should have no
issues with this, even if they use 2.5 as a better 2.4. Tim, can you
comment ?
I strongly recommend 2.5 for inclusion, or else we'll have to wait until
JBoss 6 to include it. Customers would upgrade to 2.5 independently,
causing headaches for the support team.
Clebert and I were discussing this last week, and JBM being able to
declare compatibility w/ 2.5 was looking fine.
Clebert, has anything changed on this?
--
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry(a)redhat.com
8:10 p.m.
Since JG 2.5 has better concurrency than 2.4 we need to test with it to
ensure it doesn't highlight areas of JBM code that didn't need to be
thread-safe before, but now do.
I believe Clebert gave the JBM test suite a spin with JG 2.5 while I was
on hols, and several tests failed that do not fail with 2.4.
Apart from that, I don't see any other issues.
Brian Stansberry wrote:
Bela Ban wrote:
> Dimitris Andreadis wrote:
>> - JGroups. It's still questionable at this point if we can move to
>> v2.5 (from 2.4.1.SP3) due to the JBoss Messaging dependency
> Why ? 2.5 is backward compatible, so JBoss Messaging should have no
> issues with this, even if they use 2.5 as a better 2.4. Tim, can you
> comment ?
>
> I strongly recommend 2.5 for inclusion, or else we'll have to wait
> until JBoss 6 to include it. Customers would upgrade to 2.5
> independently, causing headaches for the support team.
>
Clebert and I were discussing this last week, and JBM being able to
declare compatibility w/ 2.5 was looking fine.
Clebert, has anything changed on this?
--
Tim Fox
Messaging lead
JBoss - a division of Red Hat
5:09 p.m.
The current Hibernate core release is not compatible with JBoss Cache
2.0 (JBC API is very different.) This breaks using JBC as a Hibernate
2nd level cache.
For EJB3 entity caching I've written a CacheProvider impl that deals
with JBC 2.0, so that use case is handled. But if people want to use
Hibernate+JBC outside of EJB3, that will be a problem.
A workaround to this would be to write an equivalent to what I did for
EJB3 and include it in the hibernate-int module.
I'm currently working with Steve on a *much* improved Hibernate/JBC
integration for Hibernate 3.3. It would certainly be nicer to have AS 5
use that.
Dimitris Andreadis wrote:
After Sep/14th and until Beta3 is out we'll only be updating libs
in
order to fix bugs.
Take a look at the following JIRA to make sure your work on a particular
library is properly recorded/linked:
http://jira.jboss.com/jira/browse/JBAS-4562
--------------------------------------------------------------------
Also, for the next AS5 CRx release make sure any library updates are
recorded here:
http://jira.jboss.com/jira/browse/JBAS-4647
(e.g. discussions about jbroups 2.6)
--------------------------------------------------------------------
The current Beta3 status is summarized below:
- MC 2.0.0.Beta4 and dependencies have been resolved/tagged.
- Snapshots that need to be replaced with tagged releases.
What's currently left:
<componentref name="jboss/jboss-ejb3-cache"
version="0.11-SNAPSHOT"/>
<componentref name="jboss/jboss-jaspi-api"
version="1.0-SNAPSHOT"/>
<componentref name="jboss/jboss-security-spi"
version="2.0.1-SNAPSHOT"/>
<componentref name="jboss/jbosssx" version="2.0.1-SNAPSHOT"/>
<componentref name="jboss/jbosssx-client"
version="2.0.1-SNAPSHOT"/>
- Waiting for AOP 2.0.0.beta + Javassist 3.6.0.CR2
- JBoss Transactions
(now at 4.2.3.SP5) to be updated to a 4.3.x version that implements JTA 1.1
- JBoss Messaging
waiting for the final 1.4.0.GA release
- JGroups. It's still questionable at this point if we can move to v2.5
(from 2.4.1.SP3) due to the JBoss Messaging dependency
- Hibernate Validator
We'll be probably adding this, as it is now an independent package.
If you have any comments/concerns let me know.
Cheers
/Dimitris
--
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry(a)redhat.com
5:54 p.m.
On Friday 07 September 2007 10:09:16 am Brian Stansberry wrote:
The current Hibernate core release is not compatible with JBoss
Cache
2.0 (JBC API is very different.) This breaks using JBC as a Hibernate
2nd level cache.
For EJB3 entity caching I've written a CacheProvider impl that deals
with JBC 2.0, so that use case is handled. But if people want to use
Hibernate+JBC outside of EJB3, that will be a problem.
A workaround to this would be to write an equivalent to what I did for
EJB3 and include it in the hibernate-int module.
I'm currently working with Steve on a *much* improved Hibernate/JBC
integration for Hibernate 3.3. It would certainly be nicer to have AS 5
use that.
No way I'll have anything other than alphas/betas of 3.3 before 9/14.
6:07 p.m.
New subject: Sep/14th cutoff date for component updates in AS5 Beta3
Steve Ebersole wrote:
On Friday 07 September 2007 10:09:16 am Brian Stansberry wrote:
> The current Hibernate core release is not compatible with JBoss Cache
> 2.0 (JBC API is very different.) This breaks using JBC as a Hibernate
> 2nd level cache.
>
> For EJB3 entity caching I've written a CacheProvider impl that deals
> with JBC 2.0, so that use case is handled. But if people want to use
> Hibernate+JBC outside of EJB3, that will be a problem.
>
> A workaround to this would be to write an equivalent to what I did for
> EJB3 and include it in the hibernate-int module.
>
> I'm currently working with Steve on a *much* improved Hibernate/JBC
> integration for Hibernate 3.3. It would certainly be nicer to have AS 5
> use that.
>
No way I'll have anything other than alphas/betas of 3.3 before 9/14.
A Hibernate 3.3 Beta might be Ok, if it's compatible with the other modules
EJB3
Hibernate Entity Manager
Hibernate Annotation
jbpm/jpdl
Otherwise, we should target an update after Beta3 is out.
6:13 p.m.
New subject: Sep/14th cutoff date for component updates in AS5 Beta3
Let me know as soon as possible which version of JGroups you want in AS
5. If you want to stick with 2.5, there is no reason for us to scramble
releasing 2.6 and pushing 50% of the features into 2.7...
Brian ? Dimitris ?
Bela Ban
Lead JGroups / Clustering Team
JBoss - a division of Red Hat
6:30 p.m.
New subject: Sep/14th cutoff date for component updates in AS5 Beta3
I think we should be fine with 2.5.1.
Bela Ban wrote:
Let me know as soon as possible which version of JGroups you want in
AS
5. If you want to stick with 2.5, there is no reason for us to scramble
releasing 2.6 and pushing 50% of the features into 2.7...
Brian ? Dimitris ?
Bela Ban
Lead JGroups / Clustering Team
JBoss - a division of Red Hat
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
12:31 a.m.
New subject: Sep/14th cutoff date for component updates in AS5 Beta3
You're killing me, my friend ! 2.6 has an API change that I'd like to
establish as baseline for AS 5. We've already started pushing (almost)
all open issues into 2.7, in order to release a 2.6 (almost) GA by the
end of September. Now you're telling me this effort is futile ?
*What's the reason ?* 2.6 is not a big change from 2.5, but that 1 API
change is something JBossCache and AS Clustering will benefit from.
Stability wise, 2.6 is as stable as 2.5...
Dimitris Andreadis wrote:
I think we should be fine with 2.5.1.
Bela Ban wrote:
> Let me know as soon as possible which version of JGroups you want in
> AS 5. If you want to stick with 2.5, there is no reason for us to
> scramble releasing 2.6 and pushing 50% of the features into 2.7...
> Brian ? Dimitris ?
>
> Bela Ban
> Lead JGroups / Clustering Team
> JBoss - a division of Red Hat
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
Bela Ban
Lead JGroups / Clustering Team
JBoss - a division of Red Hat
6:39 p.m.
New subject: Sep/14th cutoff date for component updates in AS5 Beta3
I am fine with 2.5 unless in your opinion 2.6 includes some major bug
fixes that really need to be in AS 5.0.0. My assumption has always been
that AS 5 would be targeted toward JGroups 2.5, with 2.6 integrated if
it came out far enough in advance of the AS CR1 that we could properly
test it. Only reason for interest in 2.6 is just the normal desire to
pick up any bug fixes or perf improvements that come along.
Seems we're locking down the libraries for beta3 instead of CR1. That
doesn't change the above.
AIUI, the main reason for pushing for 2.6 was the API for the combined
flush for connect+ multiple state transfers we discussed yesterday. That
doesn't seem like something that can be high impact in AS 5.0.0. I
don't see how the different, completely unrelated services that do state
transfer can coordinate their state transfers, at least not without a
major effort that there's no bandwidth for. So, that leaves saving 1
flush cycle when the channel shared by all the services connects. That
would be nice, but IMHO not a huge thing worth disrupting your road map
to get in.
Bela Ban wrote:
Let me know as soon as possible which version of JGroups you want in
AS
5. If you want to stick with 2.5, there is no reason for us to scramble
releasing 2.6 and pushing 50% of the features into 2.7...
Brian ? Dimitris ?
Bela Ban
Lead JGroups / Clustering Team
JBoss - a division of Red Hat
--
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry(a)redhat.com
12:34 a.m.
New subject: Sep/14th cutoff date for component updates in AS5 Beta3
I leave this up to you guys. I would include 2.6 not 2.5 in AS 5, as we
will *NOT* be able to upgrade AS 5 to 2.6 ever. But it's not my call. As
a matter of fact, I don't mind *not* having to rush a 2.6 GA out the door...
So 2.5 then huh ?
Brian Stansberry wrote:
I am fine with 2.5 unless in your opinion 2.6 includes some major bug
fixes that really need to be in AS 5.0.0. My assumption has always
been that AS 5 would be targeted toward JGroups 2.5, with 2.6
integrated if it came out far enough in advance of the AS CR1 that we
could properly test it. Only reason for interest in 2.6 is just the
normal desire to pick up any bug fixes or perf improvements that come
along.
Seems we're locking down the libraries for beta3 instead of CR1. That
doesn't change the above.
AIUI, the main reason for pushing for 2.6 was the API for the combined
flush for connect+ multiple state transfers we discussed yesterday.
That doesn't seem like something that can be high impact in AS 5.0.0.
I don't see how the different, completely unrelated services that do
state transfer can coordinate their state transfers, at least not
without a major effort that there's no bandwidth for. So, that leaves
saving 1 flush cycle when the channel shared by all the services
connects. That would be nice, but IMHO not a huge thing worth
disrupting your road map to get in.
Bela Ban wrote:
> Let me know as soon as possible which version of JGroups you want in
> AS 5. If you want to stick with 2.5, there is no reason for us to
> scramble releasing 2.6 and pushing 50% of the features into 2.7...
> Brian ? Dimitris ?
>
> Bela Ban
> Lead JGroups / Clustering Team
> JBoss - a division of Red Hat
>
--
Bela Ban
Lead JGroups / Clustering Team
JBoss - a division of Red Hat
1:26 a.m.
New subject: Sep/14th cutoff date for component updates in AS5 Beta3
Can you clarify a bit why moving to 2.6 will never be possible?
JBC and ClusterPartition currently call:
Channel.connect(String)
Channel.getState(Address, long)
Channel.getState(Address, String, long)
Is the issue that you're changing the API of the 2 getState calls to
throw an exception instead of returning boolean? Is that absolutely
necessary? Changes to any other overloaded flavors of connect or
getState don't matter since we don't call them.
Or is the issue more that the connect+getState stuff will change the way
connecting and state transfer work so much that 2.6 will never be
interoperable with 2.5? Kind of the old "AS 4.0.x forever stuck on
2.2.7" problem.
In an AS 5.1
Bela Ban wrote:
I leave this up to you guys. I would include 2.6 not 2.5 in AS 5, as
we
will *NOT* be able to upgrade AS 5 to 2.6 ever. But it's not my call. As
a matter of fact, I don't mind *not* having to rush a 2.6 GA out the
door...
So 2.5 then huh ?
Brian Stansberry wrote:
> I am fine with 2.5 unless in your opinion 2.6 includes some major bug
> fixes that really need to be in AS 5.0.0. My assumption has always
> been that AS 5 would be targeted toward JGroups 2.5, with 2.6
> integrated if it came out far enough in advance of the AS CR1 that we
> could properly test it. Only reason for interest in 2.6 is just the
> normal desire to pick up any bug fixes or perf improvements that come
> along.
>
> Seems we're locking down the libraries for beta3 instead of CR1. That
> doesn't change the above.
>
> AIUI, the main reason for pushing for 2.6 was the API for the combined
> flush for connect+ multiple state transfers we discussed yesterday.
> That doesn't seem like something that can be high impact in AS 5.0.0.
> I don't see how the different, completely unrelated services that do
> state transfer can coordinate their state transfers, at least not
> without a major effort that there's no bandwidth for. So, that leaves
> saving 1 flush cycle when the channel shared by all the services
> connects. That would be nice, but IMHO not a huge thing worth
> disrupting your road map to get in.
>
> Bela Ban wrote:
>> Let me know as soon as possible which version of JGroups you want in
>> AS 5. If you want to stick with 2.5, there is no reason for us to
>> scramble releasing 2.6 and pushing 50% of the features into 2.7...
>> Brian ? Dimitris ?
>>
>> Bela Ban
>> Lead JGroups / Clustering Team
>> JBoss - a division of Red Hat
>>
>
>
--
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry(a)redhat.com
8:50 a.m.
New subject: Sep/14th cutoff date for component updates in AS5 Beta3
Brian Stansberry wrote:
Can you clarify a bit why moving to 2.6 will never be possible?
Because of the policy of only including dot release upgrade of component
libraries in AS, or has this changed ? So 2.5.1, 2.5.2 and so on
wouldn't be an issue, but 2.6 would. Correct ?
JBC and ClusterPartition currently call:
Channel.connect(String)
Channel.getState(Address, long)
Channel.getState(Address, String, long)
Is the issue that you're changing the API of the 2 getState calls to
throw an exception instead of returning boolean?
Yes
Is that absolutely necessary?
Yes. But remember, this is a new method, we do *not* overload the
existing connect().
Changes to any other overloaded flavors of connect or getState
don't
matter since we don't call them.
Or is the issue more that the connect+getState stuff will change the
way connecting and state transfer work so much that 2.6 will never be
interoperable with 2.5? Kind of the old "AS 4.0.x forever stuck on
2.2.7" problem.
Yes exactly. My main beef is that we have something stable (API and
implementation wise) that we can include in AS 5, so why not do it ?
--
Bela Ban
Lead JGroups / Clustering Team
JBoss - a division of Red Hat
4:45 p.m.
New subject: Sep/14th cutoff date for component updates in AS5 Beta3
I'll respond to your last point first, as it's the "bottom line." Other
responses in-line.
My impression when you first asked on this thread yesterday is you'd
decided you really did not want to disrupt your 2.6 roadmap in order to
get it in AS 5, and were seeking buy-in from Dimitris and myself. Seems
I was mistaken.
If 2.6 can't interoperate with 2.5, we should get 2.6 in AS 5. I'd
thought the change was a difference in an API we weren't using, or that
we could code around if we wanted to upgrade.
Bela Ban wrote:
Brian Stansberry wrote:
> Can you clarify a bit why moving to 2.6 will never be possible?
Because of the policy of only including dot release upgrade of component
libraries in AS, or has this changed ? So 2.5.1, 2.5.2 and so on
wouldn't be an issue, but 2.6 would. Correct ?
Dimitris, please comment with the official answer. :)
I'd think there'd be no problem upgrading across minor releases if we
went from 5.0.x to 5.1.0, but there would likely be a problem if we went
from 5.0.0 to 5.0.1.
Either way, this points to a larger issue where it's unclear what the
big picture AS roadmap is. Do we want to do a bunch of 5.0.x releases,
or fairly shortly after 5.0.0 go to a 5.1.0?
> JBC and ClusterPartition currently call:
>
> Channel.connect(String)
> Channel.getState(Address, long)
> Channel.getState(Address, String, long)
> Is the issue that you're changing the API of the 2 getState calls to
> throw an exception instead of returning boolean?
Yes
> Is that absolutely necessary?
Yes. But remember, this is a new method, we do *not* overload the
existing connect().
Still confused; this and your answer to the above seem to contradict.
But no matter, I'll understand when I look at the API. :) Key thing is
2.5 and 2.6 can't interoperate.
> Changes to any other overloaded flavors of connect or getState
don't
> matter since we don't call them.
>
> Or is the issue more that the connect+getState stuff will change the
> way connecting and state transfer work so much that 2.6 will never be
> interoperable with 2.5? Kind of the old "AS 4.0.x forever stuck on
> 2.2.7" problem.
Yes exactly. My main beef is that we have something stable (API and
implementation wise) that we can include in AS 5, so why not do it ?
--
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry(a)redhat.com
6:18 p.m.
New subject: Sep/14th cutoff date for component updates in AS5 Beta3
Dimitris, please comment with the official answer. :)
I'd think there'd be no problem upgrading across minor releases if we
went from 5.0.x to 5.1.0, but there would likely be a problem if we went
from 5.0.0 to 5.0.1.
Correct.
Either way, this points to a larger issue where it's unclear what
the
big picture AS roadmap is. Do we want to do a bunch of 5.0.x releases,
or fairly shortly after 5.0.0 go to a 5.1.0?
That's not clear yet. Chances are, we'll need a couple of point releases first.
As far as I'm concerned we can go with jgroups 2.6 if
a) Brian is ok
b) The JBoss Messaging team are ok
c) 2.6 is ready for the AS5 CR release
For AS Beta3 we should upgrade to 2.5, ASAP.
12:29 p.m.
New subject: Sep/14th cutoff date for component updates in AS5 Beta3
Brian Stansberry wrote:
I'll respond to your last point first, as it's the
"bottom line."
Other responses in-line.
My impression when you first asked on this thread yesterday is you'd
decided you really did not want to disrupt your 2.6 roadmap in order
to get it in AS 5, and were seeking buy-in from Dimitris and myself.
Seems I was mistaken.
No, I said I would cut a 2.6 *before* the planned release data, with
come features pushed into 2.7, if you guys were willing to accept it
into AS 5. Of course, since this is more work for me, I would not mind
if I didn't have to do it ... :-)
If 2.6 can't interoperate with 2.5, we should get 2.6 in AS 5.
2.6 is backward compatible with 2.5 if you don't use the new connect()
call added in 2.6.
I'd think there'd be no problem upgrading across minor
releases if we
went from 5.0.x to 5.1.0, but there would likely be a problem if we
went from 5.0.0 to 5.0.1.
That is my understanding too. And if we go for 5.0/2.5 and 5.1/2.6, then
we would *not* support the 5.1/2.6 combo; according to the standard Red
Hat policy, customers would have to upgrade to 5.1 to use 2.6.
Either way, this points to a larger issue where it's unclear what
the
big picture AS roadmap is. Do we want to do a bunch of 5.0.x releases,
or fairly shortly after 5.0.0 go to a 5.1.0?
I'm interested in the answer to this too...
> Yes. But remember, this is a new method, we do *not* overload the
> existing connect().
>
>
Still confused; this and your answer to the above seem to contradict.
But no matter, I'll understand when I look at the API. :)
My yes was to "is it absolutely necessary to throw exceptions?", *NOT*
to "is upgrading to 2.6 a must", maybe that's the src of the confusion.
Key thing is 2.5 and 2.6 can't interoperate.
No, not true, they can if you don't use the new connect() methods.
--
Bela Ban
Lead JGroups / Clustering Team
JBoss - a division of Red Hat
6:05 p.m.
New subject: Sep/14th cutoff date for component updates in AS5 Beta3
Bela Ban wrote:
I leave this up to you guys. I would include 2.6 not 2.5 in AS 5, as
we
will *NOT* be able to upgrade AS 5 to 2.6 ever. But it's not my call. As
a matter of fact, I don't mind *not* having to rush a 2.6 GA out the
door...
So 2.5 then huh ?
You are bluffing :)
3:17 p.m.
New subject: AS5 Beta3 status - Sep/13th
Tomorrow (After Sep/14th) is the target date for completing component updates in jboss
trunk, in preparation for AS5 Beta3. After this round of updates is complete we should
avoid
making API changes, rather concentrate on bug fixes and implementation of missing
features.
I've send out mails to individual components owner about the pending updates below,
but you
may update the corresponding JIRA tasks starting from:
http://jira.jboss.com/jira/browse/JBAS-4562
For tracking updates for the next AS5 CRx please use:
http://jira.jboss.com/jira/browse/JBAS-4647
A summary of the current status:
The snapshot list is the same like last week
<componentref name="jboss/jboss-ejb3-cache"
version="0.11-SNAPSHOT"/>
<componentref name="jboss/jboss-jaspi-api"
version="1.0-SNAPSHOT"/>
<componentref name="jboss/jboss-security-spi"
version="2.0.1-SNAPSHOT"/>
<componentref name="jboss/jbosssx" version="2.0.1-SNAPSHOT"/>
<componentref name="jboss/jbosssx-client"
version="2.0.1-SNAPSHOT"/>
- Security libs are waiting on Anil, he will tag tomorrow.
- The jboss-ejb3-cache tag (Carlo) is waiting on jboss-javaee. Some tagging issues there:
http://jira.jboss.com/jira/browse/JBAS-4533
http://jira.jboss.com/jira/browse/JBAS-4687
- AOP 2.0.0.beta + Javassist 3.6.0.GA is on track (Kabir/Chiba).
- JBoss Transactions, Jonathan almost there for producing an updated to a 4.3.x version.
- JBoss Messaging, waiting for the final 1.4.0.GA release. Will have to wait for next
week.
- JGroups. Need to move to v.2.5 ASAP
- Hibernate Validator, we'll be adding this, as it is now an independent package.
- JBoss Common needs updating, initially at snapshot (Anil?)
----------------------------------------------------------------------
Testsuites
http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-testsuite-sun-1.5
The CC runs are unstable due to a server minimal shutdown issue
http://jira.jboss.com/jira/browse/JBAS-4587
The hudson noip builds also got a little worse due to ongoing clustering test refactoring
http://hudson.jboss.org/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15-noip/
A large part of our testsuite is failing due to the deployer changes.
If you work on the AS testsuite, record your work/findings here:
http://jira.jboss.com/jira/browse/JBAS-4636
Other
-----
The AppClient deployer needs refactoring as ejb-refs resolved from 1.4 appclients have no
connection to ejb3 deployment types.
http://jira.jboss.com/jira/browse/JBCTS-654
http://jira.jboss.com/jira/browse/JBAS-4707
Some important EJB3 dependencies:
http://jira.jboss.com/jira/browse/EJBTHREE-1026 (done?)
http://jira.jboss.com/jira/browse/JBAS-4423 (work on-going)
http://jira.jboss.com/jira/browse/JBAS-4679 (waiting on ThomasD)
The JIRA for AS5 needs further work and cleaning up
http://jira.jboss.com/jira/browse/JBAS
Blockers and Criticals are the important ones, so make sure you mark as such what must
make
it into a release, and preferably start working on it.
For important issues we need to track in this status report, please send me an email.
Thanks
/Dimitris
3:32 p.m.
New subject: AS5 Beta3 status - Sep/13th
From my side:
a) I resolved the EJB3 security assimilation JIRA issue (JBAS-4423) and
the pending minor issue associated has been moved to EJBTHREE-1047. Any
more EJB3 security issues need to be added as new JIRA issues.
b) JBoss-jaspi-api has been uploaded to maven and svn repos as
1.0-BETA1. It will be tagged along with the master jboss-javaee project
(whoever is doing that will handle that).
c) jboss-common-core currently needs an upgrade to 2.2.2.snapshot in AS5
(I will do this along with my security lib upgrades). Dimitris, are you
going to be doing a tagged release of common-core tomorrow?
d) Security libs will be tagged as 2.0.1-BETA1. I am doing AS5 testing
of them today.
Dimitris Andreadis wrote:
Tomorrow (After Sep/14th) is the target date for completing component
updates in jboss trunk, in preparation for AS5 Beta3. After this round
of updates is complete we should avoid making API changes, rather
concentrate on bug fixes and implementation of missing features.
I've send out mails to individual components owner about the pending
updates below, but you may update the corresponding JIRA tasks
starting from:
http://jira.jboss.com/jira/browse/JBAS-4562
For tracking updates for the next AS5 CRx please use:
http://jira.jboss.com/jira/browse/JBAS-4647
A summary of the current status:
The snapshot list is the same like last week
<componentref name="jboss/jboss-ejb3-cache"
version="0.11-SNAPSHOT"/>
<componentref name="jboss/jboss-jaspi-api"
version="1.0-SNAPSHOT"/>
<componentref name="jboss/jboss-security-spi"
version="2.0.1-SNAPSHOT"/>
<componentref name="jboss/jbosssx" version="2.0.1-SNAPSHOT"/>
<componentref name="jboss/jbosssx-client"
version="2.0.1-SNAPSHOT"/>
- Security libs are waiting on Anil, he will tag tomorrow.
- The jboss-ejb3-cache tag (Carlo) is waiting on jboss-javaee. Some
tagging issues there:
http://jira.jboss.com/jira/browse/JBAS-4533
http://jira.jboss.com/jira/browse/JBAS-4687
- AOP 2.0.0.beta + Javassist 3.6.0.GA is on track (Kabir/Chiba).
- JBoss Transactions, Jonathan almost there for producing an updated
to a 4.3.x version.
- JBoss Messaging, waiting for the final 1.4.0.GA release. Will have
to wait for next week.
- JGroups. Need to move to v.2.5 ASAP
- Hibernate Validator, we'll be adding this, as it is now an
independent package.
- JBoss Common needs updating, initially at snapshot (Anil?)
----------------------------------------------------------------------
Testsuites
http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-testsuite-sun-1.5
The CC runs are unstable due to a server minimal shutdown issue
http://jira.jboss.com/jira/browse/JBAS-4587
The hudson noip builds also got a little worse due to ongoing
clustering test refactoring
http://hudson.jboss.org/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15-noip/
A large part of our testsuite is failing due to the deployer changes.
If you work on the AS testsuite, record your work/findings here:
http://jira.jboss.com/jira/browse/JBAS-4636
Other
-----
The AppClient deployer needs refactoring as ejb-refs resolved from 1.4
appclients have no connection to ejb3 deployment types.
http://jira.jboss.com/jira/browse/JBCTS-654
http://jira.jboss.com/jira/browse/JBAS-4707
Some important EJB3 dependencies:
http://jira.jboss.com/jira/browse/EJBTHREE-1026 (done?)
http://jira.jboss.com/jira/browse/JBAS-4423 (work on-going)
http://jira.jboss.com/jira/browse/JBAS-4679 (waiting on ThomasD)
The JIRA for AS5 needs further work and cleaning up
http://jira.jboss.com/jira/browse/JBAS
Blockers and Criticals are the important ones, so make sure you mark
as such what must make it into a release, and preferably start working
on it.
For important issues we need to track in this status report, please
send me an email.
Thanks
/Dimitris
__________
4:04 p.m.
New subject: AS5 Beta3 status - Sep/13th
Anil Saldhana wrote:
c) jboss-common-core currently needs an upgrade to 2.2.2.snapshot in
AS5
(I will do this along with my security lib upgrades). Dimitris, are you
going to be doing a tagged release of common-core tomorrow?
I'll do that.
4:12 p.m.
New subject: AS5 Beta3 status - Sep/13th
I'm going to redo the jboss-javaee Beta3 release with build numbers on
the subprojects, and their current version. It will include the security
api update from Anil.
Dimitris Andreadis wrote:
Tomorrow (After Sep/14th) is the target date for completing
component
updates in jboss trunk, in preparation for AS5 Beta3. After this round
of updates is complete we should avoid making API changes, rather
concentrate on bug fixes and implementation of missing features.
I've send out mails to individual components owner about the pending
updates below, but you may update the corresponding JIRA tasks starting
from:
http://jira.jboss.com/jira/browse/JBAS-4562
For tracking updates for the next AS5 CRx please use:
http://jira.jboss.com/jira/browse/JBAS-4647
A summary of the current status:
The snapshot list is the same like last week
<componentref name="jboss/jboss-ejb3-cache"
version="0.11-SNAPSHOT"/>
<componentref name="jboss/jboss-jaspi-api"
version="1.0-SNAPSHOT"/>
<componentref name="jboss/jboss-security-spi"
version="2.0.1-SNAPSHOT"/>
<componentref name="jboss/jbosssx" version="2.0.1-SNAPSHOT"/>
<componentref name="jboss/jbosssx-client"
version="2.0.1-SNAPSHOT"/>
- Security libs are waiting on Anil, he will tag tomorrow.
- The jboss-ejb3-cache tag (Carlo) is waiting on jboss-javaee. Some
tagging issues there:
http://jira.jboss.com/jira/browse/JBAS-4533
http://jira.jboss.com/jira/browse/JBAS-4687
- AOP 2.0.0.beta + Javassist 3.6.0.GA is on track (Kabir/Chiba).
- JBoss Transactions, Jonathan almost there for producing an updated to
a 4.3.x version.
- JBoss Messaging, waiting for the final 1.4.0.GA release. Will have to
wait for next week.
- JGroups. Need to move to v.2.5 ASAP
- Hibernate Validator, we'll be adding this, as it is now an independent
package.
- JBoss Common needs updating, initially at snapshot (Anil?)
----------------------------------------------------------------------
Testsuites
http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-testsuite-sun-1.5
The CC runs are unstable due to a server minimal shutdown issue
http://jira.jboss.com/jira/browse/JBAS-4587
The hudson noip builds also got a little worse due to ongoing clustering
test refactoring
http://hudson.jboss.org/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15-noip/
A large part of our testsuite is failing due to the deployer changes.
If you work on the AS testsuite, record your work/findings here:
http://jira.jboss.com/jira/browse/JBAS-4636
Other
-----
The AppClient deployer needs refactoring as ejb-refs resolved from 1.4
appclients have no connection to ejb3 deployment types.
http://jira.jboss.com/jira/browse/JBCTS-654
http://jira.jboss.com/jira/browse/JBAS-4707
Some important EJB3 dependencies:
http://jira.jboss.com/jira/browse/EJBTHREE-1026 (done?)
http://jira.jboss.com/jira/browse/JBAS-4423 (work on-going)
http://jira.jboss.com/jira/browse/JBAS-4679 (waiting on ThomasD)
The JIRA for AS5 needs further work and cleaning up
http://jira.jboss.com/jira/browse/JBAS
Blockers and Criticals are the important ones, so make sure you mark as
such what must make it into a release, and preferably start working on it.
For important issues we need to track in this status report, please send
me an email.
Thanks
/Dimitris
7:39 p.m.
New subject: AS5 Beta3 status - Sep/13th
JBAS-4533 for the jboss-javaee release is resolved.
Dimitris Andreadis wrote:
Tomorrow (After Sep/14th) is the target date for completing
component
updates in jboss trunk, in preparation for AS5 Beta3. After this round
of updates is complete we should avoid making API changes, rather
concentrate on bug fixes and implementation of missing features.
I've send out mails to individual components owner about the pending
updates below, but you may update the corresponding JIRA tasks starting
from:
http://jira.jboss.com/jira/browse/JBAS-4562
For tracking updates for the next AS5 CRx please use:
http://jira.jboss.com/jira/browse/JBAS-4647
A summary of the current status:
The snapshot list is the same like last week
<componentref name="jboss/jboss-ejb3-cache"
version="0.11-SNAPSHOT"/>
<componentref name="jboss/jboss-jaspi-api"
version="1.0-SNAPSHOT"/>
<componentref name="jboss/jboss-security-spi"
version="2.0.1-SNAPSHOT"/>
<componentref name="jboss/jbosssx" version="2.0.1-SNAPSHOT"/>
<componentref name="jboss/jbosssx-client"
version="2.0.1-SNAPSHOT"/>
- Security libs are waiting on Anil, he will tag tomorrow.
- The jboss-ejb3-cache tag (Carlo) is waiting on jboss-javaee. Some
tagging issues there:
http://jira.jboss.com/jira/browse/JBAS-4533
http://jira.jboss.com/jira/browse/JBAS-4687
- AOP 2.0.0.beta + Javassist 3.6.0.GA is on track (Kabir/Chiba).
- JBoss Transactions, Jonathan almost there for producing an updated to
a 4.3.x version.
- JBoss Messaging, waiting for the final 1.4.0.GA release. Will have to
wait for next week.
- JGroups. Need to move to v.2.5 ASAP
- Hibernate Validator, we'll be adding this, as it is now an independent
package.
- JBoss Common needs updating, initially at snapshot (Anil?)
----------------------------------------------------------------------
Testsuites
http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-testsuite-sun-1.5
The CC runs are unstable due to a server minimal shutdown issue
http://jira.jboss.com/jira/browse/JBAS-4587
The hudson noip builds also got a little worse due to ongoing clustering
test refactoring
http://hudson.jboss.org/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15-noip/
A large part of our testsuite is failing due to the deployer changes.
If you work on the AS testsuite, record your work/findings here:
http://jira.jboss.com/jira/browse/JBAS-4636
Other
-----
The AppClient deployer needs refactoring as ejb-refs resolved from 1.4
appclients have no connection to ejb3 deployment types.
http://jira.jboss.com/jira/browse/JBCTS-654
http://jira.jboss.com/jira/browse/JBAS-4707
Some important EJB3 dependencies:
http://jira.jboss.com/jira/browse/EJBTHREE-1026 (done?)
http://jira.jboss.com/jira/browse/JBAS-4423 (work on-going)
http://jira.jboss.com/jira/browse/JBAS-4679 (waiting on ThomasD)
The JIRA for AS5 needs further work and cleaning up
http://jira.jboss.com/jira/browse/JBAS
Blockers and Criticals are the important ones, so make sure you mark as
such what must make it into a release, and preferably start working on it.
For important issues we need to track in this status report, please send
me an email.
Thanks
/Dimitris
10:19 p.m.
New subject: AS5 Beta3 status - Sep/13th
Scott, your numbering scheme does not work anymore with "mvn deploy".
It deployed
http://snapshots.jboss.org/maven2/org/jboss/javaee/jboss-jaspi-api/1.0.0....
I use "mvn deploy" so that it gives me the artifacts for the svn rep.
Scott M Stark wrote:
JBAS-4533 for the jboss-javaee release is resolved.
Dimitris Andreadis wrote:
> Tomorrow (After Sep/14th) is the target date for completing component
> updates in jboss trunk, in preparation for AS5 Beta3. After this round
> of updates is complete we should avoid making API changes, rather
> concentrate on bug fixes and implementation of missing features.
>
> I've send out mails to individual components owner about the pending
> updates below, but you may update the corresponding JIRA tasks starting
> from:
> http://jira.jboss.com/jira/browse/JBAS-4562
>
> For tracking updates for the next AS5 CRx please use:
> http://jira.jboss.com/jira/browse/JBAS-4647
>
> A summary of the current status:
>
> The snapshot list is the same like last week
> <componentref name="jboss/jboss-ejb3-cache"
version="0.11-SNAPSHOT"/>
> <componentref name="jboss/jboss-jaspi-api"
version="1.0-SNAPSHOT"/>
> <componentref name="jboss/jboss-security-spi"
version="2.0.1-SNAPSHOT"/>
> <componentref name="jboss/jbosssx"
version="2.0.1-SNAPSHOT"/>
> <componentref name="jboss/jbosssx-client"
version="2.0.1-SNAPSHOT"/>
>
> - Security libs are waiting on Anil, he will tag tomorrow.
>
> - The jboss-ejb3-cache tag (Carlo) is waiting on jboss-javaee. Some
> tagging issues there:
> http://jira.jboss.com/jira/browse/JBAS-4533
> http://jira.jboss.com/jira/browse/JBAS-4687
>
> - AOP 2.0.0.beta + Javassist 3.6.0.GA is on track (Kabir/Chiba).
>
> - JBoss Transactions, Jonathan almost there for producing an updated to
> a 4.3.x version.
>
> - JBoss Messaging, waiting for the final 1.4.0.GA release. Will have to
> wait for next week.
>
> - JGroups. Need to move to v.2.5 ASAP
>
> - Hibernate Validator, we'll be adding this, as it is now an independent
> package.
>
> - JBoss Common needs updating, initially at snapshot (Anil?)
>
> ----------------------------------------------------------------------
>
> Testsuites
>
> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-testsuite-sun-1.5
>
> The CC runs are unstable due to a server minimal shutdown issue
> http://jira.jboss.com/jira/browse/JBAS-4587
>
> The hudson noip builds also got a little worse due to ongoing clustering
> test refactoring
> http://hudson.jboss.org/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15-noip/
>
> A large part of our testsuite is failing due to the deployer changes.
>
> If you work on the AS testsuite, record your work/findings here:
> http://jira.jboss.com/jira/browse/JBAS-4636
>
> Other
> -----
> The AppClient deployer needs refactoring as ejb-refs resolved from 1.4
> appclients have no connection to ejb3 deployment types.
> http://jira.jboss.com/jira/browse/JBCTS-654
> http://jira.jboss.com/jira/browse/JBAS-4707
>
> Some important EJB3 dependencies:
> http://jira.jboss.com/jira/browse/EJBTHREE-1026 (done?)
> http://jira.jboss.com/jira/browse/JBAS-4423 (work on-going)
> http://jira.jboss.com/jira/browse/JBAS-4679 (waiting on ThomasD)
>
> The JIRA for AS5 needs further work and cleaning up
> http://jira.jboss.com/jira/browse/JBAS
>
> Blockers and Criticals are the important ones, so make sure you mark as
> such what must make it into a release, and preferably start working on it.
>
> For important issues we need to track in this status report, please send
> me an email.
>
> Thanks
> /Dimitris
>
>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
Anil Saldhana
Project/Technical Lead,
JBoss Security & Identity Management
JBoss, A division of Red Hat Inc.
http://labs.jboss.com/portal/jbosssecurity/
11:21 p.m.
New subject: AS5 Beta3 status - Sep/13th
Then the version.jboss-jaspi-api needs to be updated to just
1.0.0.${build.id} in trunk I guess.
Anil Saldhana wrote:
Scott, your numbering scheme does not work anymore with "mvn
deploy".
It deployed
http://snapshots.jboss.org/maven2/org/jboss/javaee/jboss-jaspi-api/1.0.0....
I use "mvn deploy" so that it gives me the artifacts for the svn rep.
7:02 p.m.
New subject: AS5 Beta3 status - Sep/20th
=====================================================================================
PROGRESS
=====================================================================================
- MC and AOP work for Beta3 is finished, thanks to both teams!
Component Updates
-----------------
- JBossTS upgraded to 4.3.0.BETA1 - thanks Jonathan
- Moved to JGroups 2.5 - watch for problems especially with JBM 1.4.0, thanks Brian
- Remoting 2.2.2.SP1 - thanks Ron
- Security libs tagged at 2.0.1.BETA1, JASPI api at 1.0-Beta12, thanks Anil.
- Included Hibernate Validator with the server libs
- JBoss Common-core, currently on snapshot
Key JBAS Issues
http://jira.jboss.com/jira/browse/JBAS-4423 (Anil)
http://jira.jboss.com/jira/browse/JBAS-4679 (ThomasD)
A lot of refactoring work by Brian.
CTS
---
- Stefan has patched JacORB for CSIv2 tests! Need to produce in brew and test the patched
version.
=====================================================================================
ON GOING WORK
=====================================================================================
Component Updates
-----------------
http://jira.jboss.com/jira/browse/JBAS-4562
For tracking updates for the next AS5 CRx please use:
http://jira.jboss.com/jira/browse/JBAS-4647
The snapshot list is the same like last week:
<componentref name="jboss/common-core"
version="2.2.2.snapshot"/>
<componentref name="jboss/jboss-ejb3-cache"
version="0.11-SNAPSHOT"/>
- The jboss-ejb3-cache tag (Carlo) was waiting on jboss-javaee but this is now resolved so
Carlo could proceed with it:
http://jira.jboss.com/jira/browse/JBAS-4687
- JBoss Common, use a tagged release (dimitris)
- JBoss Messaging, waiting for the final 1.4.0.GA release. (next week?)
- Hibernate 3.3, needed by JBoss Cache. If it cannot be delivered by soon, target AS5
CR1.
Brian: "The current Hibernate core release is not compatible with JBoss Cache 2.0
(JBC API
is very different.) This breaks using JBC as a Hibernate 2nd level cache. For EJB3
entity
caching I've written a CacheProvider impl that deals with JBC 2.0, so that use case
is
handled. But if people want to use Hibernate+JBC outside of EJB3, that will be a problem.
A
workaround to this would be to write an equivalent to what I did for EJB3 and include it
in
the hibernate-int module. I'm currently working with Steve on a *much* improved
Hibernate/JBC integration for Hibernate 3.3. It would certainly be nicer to have AS 5 use
that."
Steve: No way I'll have anything other than alphas/betas of 3.3 before 9/14.
- JGroups 2.6 for AS5 CR1. Bela just released a 2.6.Beta1 and a 2.5.1 so maybe we can
choose
one of the two for Beta3 (now at 2.5)
JBAS JIRA
---------
The JIRA for AS5 needs further work and cleaning up
http://jira.jboss.com/jira/browse/JBAS
Blockers and Criticals are the important ones, so make sure you mark as
such what must make it into a release, and preferably start working on it.
Key Issues
http://jira.jboss.com/jira/browse/JBAS-4720 - Weston
http://jira.jboss.com/jira/browse/EJBTHREE-1026 - Carlo
http://jira.jboss.com/jira/browse/EJBTHREE-1047 - waiting on ejb3 regressions (Anil)
http://jira.jboss.com/jira/browse/JBAS-3415 - Weston
http://jira.jboss.com/jira/browse/JBAS-3412 - Scott
http://jira.jboss.com/jira/browse/JBAS-4506 - Scott
http://jira.jboss.com/jira/browse/JBAS-4620 - Anil
CTS 5.0
-------
http://jira.jboss.com/jira/browse/JBCTS-636 - Weston
http://jira.jboss.com/jira/browse/JBCTS-654 - Scott
http://jira.jboss.com/jira/browse/JBCTS-595, 651 - Alexey
http://jira.jboss.com/jira/browse/JBCTS-547, 652, 653 - Carlo
http://jira.jboss.com/jira/browse/JBCTS-593 - Jean Frederic/Carlo
http://jira.jboss.com/jira/browse/JBCTS-586 - Heiko
Testsuites
----------
Due to the large number of changes all of our testsuites are in a bad shape so we really
need to make an effort and stabilize them:
http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-testsuite-sun-1.5
There is this weird shutdown issue when run in VMWare:
http://jira.jboss.com/jira/browse/JBAS-4587
http://hudson.jboss.org/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15-noip/
If you work on the AS testsuite, record your work/findings here:
http://jira.jboss.com/jira/browse/JBAS-4636
Discussions
-----------
Various topics raised by Sacha
- Easier/condensed config options (a la -ds.xml)
- Downloadable prepackaged optional bundles
- MC/classloader based patch management with scripting capabilities.
Unified Metadata
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=118600&a...
Other
-----
The AppClient deployer is undergoing refactoring as ejb-refs resolved from 1.4
appclients have no connection to ejb3 deployment types.
http://jira.jboss.com/jira/browse/JBCTS-654
http://jira.jboss.com/jira/browse/JBAS-4707
For important issues I have missed and we need to track in this status report, please
send
me an email.
Thanks
/Dimitris
1:27 p.m.
New subject: AS5 Beta3 status
As a general comment, we got sidetracked last week by key people away in meetings (TBoD),
and an imminent AS 4.2.2 release with last minutes updates/fixes and our EJB3/WS teams
working on those.
Beta3 is already delayed, so please let's focus to add the missing pieces and
stabilize the
testsuites/tck. There are so many things going on at the same time, so please refrain from
unnecessary refactorings and new features at this point. We need to bring the open issues
down to a small manageable set, otherwise we'll keep fighting against moving targets.
Pending Component Updates
-------------------------
http://jira.jboss.com/jira/browse/JBAS-4687 - jboss-ejb3-cache (Carlo)
http://jira.jboss.com/jira/browse/JBAS-4688 - jbossts 4.3.0.BETA2/jboss-integration
(Jonathan)
http://jira.jboss.com/jira/browse/JBAS-4716 - common-core to 2.2.2.GA (Dimitris)
http://jira.jboss.com/jira/browse/JBAS-4744 - JBossXB 2.0.0.CR5 (Alexey)
http://jira.jboss.com/jira/browse/JBAS-4745 - Metadata (Scott)
http://jira.jboss.com/jira/browse/JBAS-4746 - MC 2.0.0.Beta5 (Scott)
Blockers/Critical
-----------------
JIRA could use some cleanup of the actual work done, see below:
http://jira.jboss.com/jira/browse/JBAS
Deployer refactoring
http://jira.jboss.com/jira/browse/JBAS-3410
http://jira.jboss.com/jira/browse/JBAS-3412 - client deployer/javaee5 support (Scott)
http://jira.jboss.com/jira/browse/JBAS-3415 - rar deployer (Weston)
Metadata Unification
http://jira.jboss.com/jira/browse/JBAS-4506
http://jira.jboss.com/jira/browse/JBAS-4707 - Client deployer (Scott)
http://jira.jboss.com/jira/browse/EJBTHREE-811 - new ejb3 deployers (BillB?)
http://jira.jboss.com/jira/browse/EJBTHREE-718 - appclient deployer (Carlo?)
Other
http://jira.jboss.com/jira/browse/JBAS-4720 - security-domain/jca deployer - (Weston)
http://jira.jboss.com/jira/browse/EJBTHREE-1026 - extended persistence context (Carlo)
http://jira.jboss.com/jira/browse/EJBTHREE-1047 - waiting on ejb3 regressions fixed
(Anil)
CTS 5.0
-------
We had a big improvement last week, then we just got hurt by a regression in the ejb/ejb3
modules (-1.5% overall)
http://jira.jboss.com/jira/browse/JBCTS-369, 663 - Jonathan
http://jira.jboss.com/jira/browse/JBCTS-636 - Weston
http://jira.jboss.com/jira/browse/JBCTS-654 - Scott
http://jira.jboss.com/jira/browse/JBCTS-595, 651 660, - Alexey
http://jira.jboss.com/jira/browse/JBCTS-547, 652, 653 - Carlo
http://jira.jboss.com/jira/browse/JBCTS-593 - Jean Frederic/Carlo
http://jira.jboss.com/jira/browse/JBCTS-586 - Heiko
Testsuites
----------
Our testsuites are in a really bad shape, so please help. There are plenty of failures to
choose from:
http://dev45.qa.atl.jboss.com:8585/hudson/view/JBoss%20AS/job/JBoss-AS-5....
There is this weird shutdown issue when run in VMWare:
http://jira.jboss.com/jira/browse/JBAS-4587
If you work on the AS testsuite, record your work/findings here:
http://jira.jboss.com/jira/browse/JBAS-4636
Discussions
-----------
Various topics raised by Sacha
- Easier/condensed config options (a la -ds.xml)
- Downloadable prepackaged optional bundles
- MC/classloader based patch management with scripting capabilities.
Unified Metadata
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=118600&a...
Other
-----
The AppClient deployer is undergoing refactoring as ejb-refs resolved
from 1.4 appclients have no connection to ejb3 deployment types.
http://jira.jboss.com/jira/browse/JBCTS-654
http://jira.jboss.com/jira/browse/JBAS-4707
For important issues I have missed and we need to track in this status report, please
send
me an email.
Thanks
/Dimitris
5:07 p.m.
New subject: AS5 Beta3 status
On 10/5/07, Dimitris Andreadis <dandread(a)redhat.com> wrote:
Pending Component Updates
-------------------------
http://jira.jboss.com/jira/browse/JBAS-4687 - jboss-ejb3-cache (Carlo)
http://jira.jboss.com/jira/browse/JBAS-4688 - jbossts 4.3.0.BETA2/jboss-integration
(Jonathan)
http://jira.jboss.com/jira/browse/JBAS-4716 - common-core to 2.2.2.GA (Dimitris)
http://jira.jboss.com/jira/browse/JBAS-4744 - JBossXB 2.0.0.CR5 (Alexey)
http://jira.jboss.com/jira/browse/JBAS-4745 - Metadata (Scott)
http://jira.jboss.com/jira/browse/JBAS-4746 - MC 2.0.0.Beta5 (Scott)
I would like to update the JBoss Web CR with a bugfix CR. Is that possible ?
Rémy
5:10 p.m.
New subject: AS5 Beta3 status
Go ahead.
Rémy Maucherat wrote:
On 10/5/07, Dimitris Andreadis <dandread(a)redhat.com> wrote:
> Pending Component Updates
> -------------------------
> http://jira.jboss.com/jira/browse/JBAS-4687 - jboss-ejb3-cache (Carlo)
> http://jira.jboss.com/jira/browse/JBAS-4688 - jbossts 4.3.0.BETA2/jboss-integration
(Jonathan)
> http://jira.jboss.com/jira/browse/JBAS-4716 - common-core to 2.2.2.GA (Dimitris)
> http://jira.jboss.com/jira/browse/JBAS-4744 - JBossXB 2.0.0.CR5 (Alexey)
> http://jira.jboss.com/jira/browse/JBAS-4745 - Metadata (Scott)
> http://jira.jboss.com/jira/browse/JBAS-4746 - MC 2.0.0.Beta5 (Scott)
I would like to update the JBoss Web CR with a bugfix CR. Is that possible ?
Rémy
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
1:15 p.m.
New subject: AS5 Beta3 status - Nov/5th
The release criteria for AS5 Beta3 include:
- API stability for MC, metadate, XB
- EJB3 refactoring and Deployer stability
- A satisfying CTS pass rate (96%+)
- Profile service
- Stability of the regular testsuite runs
- Blocker/Critical AS JIRAs
Pending Component Updates
-------------------------
Currently at SNAPSHOT
http://jira.jboss.com/jira/browse/JBAS-4687 - jboss-ejb3-cache (Carlo)
http://jira.jboss.com/jira/browse/JBAS-4567 - jbossws (ThomasD)
http://jira.jboss.com/jira/browse/JBAS-4744 - JBossXB 2.0.0.CR5 (Alexey)
http://jira.jboss.com/jira/browse/JBAS-4745 - Metadata (Scott)
Blockers/Critical
-----------------
Remember that all open non blocker or critical issues will be rescheduled, so make sure
they
are marked as such:
Deployer refactoring
http://jira.jboss.com/jira/browse/JBAS-3410
http://jira.jboss.com/jira/browse/JBAS-3412 - client deployer/javaee5 support (Scott)
http://jira.jboss.com/jira/browse/JBAS-3415 - rar deployer (was Weston, can Adrian help?)
Metadata Unification
http://jira.jboss.com/jira/browse/JBAS-4506
http://jira.jboss.com/jira/browse/JBAS-4707 - Client deployer (Scott)
http://jira.jboss.com/jira/browse/EJBTHREE-811 - new ejb3 deployers (Carlo?)
http://jira.jboss.com/jira/browse/EJBTHREE-718 - appclient deployer (Carlo?)
Deployers implement ManagedObjectCreator
http://jira.jboss.com/jira/browse/JBAS-4376
http://jira.jboss.com/jira/browse/JBAS-4671 - Adrian
http://jira.jboss.com/jira/browse/JBAS-4672 - Dimitris
http://jira.jboss.com/jira/browse/JBAS-4658 - Dimitris
Some JIRA filters for Beta3:
Issues reported by you (current user)
http://jira.jboss.com/jira/secure/IssueNavigator.jspa?mode=hide&reque...
Issues assigned to you (current user)
http://jira.jboss.com/jira/secure/IssueNavigator.jspa?mode=hide&reque...
Unassigned tasks
http://jira.jboss.com/jira/secure/IssueNavigator.jspa?mode=hide&reque...
CTS 5.0
-------
The metadata refactorings got us from 96.44% down to 18.16% and back up to 38.52%. We
obviously need to bring the percentage back to a pre-metadata refactoring level and
higher.
The overall status of the refactoring here:
http://jira.jboss.com/jira/browse/JBCTS-673
Open subtasks:
http://jira.jboss.com/jira/browse/JBCTS-692 - Scott
http://jira.jboss.com/jira/browse/JBCTS-682, 686, 690, Alexey
http://jira.jboss.com/jira/browse/JBCTS-687 - Remy
Other CTS tasks:
http://jira.jboss.com/jira/browse/JBCTS-663 - Jonathan (resolved?)
http://jira.jboss.com/jira/browse/JBCTS-664 - Carlo
http://jira.jboss.com/jira/browse/JBCTS-665 - Shelly
http://jira.jboss.com/jira/browse/JBCTS-666 - Carlo
http://jira.jboss.com/jira/browse/JBCTS-369 - Weston -> Shelly
http://jira.jboss.com/jira/browse/JBCTS-654 - Scott
http://jira.jboss.com/jira/browse/JBCTS-595 - Alexey
http://jira.jboss.com/jira/browse/JBCTS-660 - Stefan
http://jira.jboss.com/jira/browse/JBCTS-547 - Carlo
http://jira.jboss.com/jira/browse/JBCTS-652 - Emmannel / Shelly
http://jira.jboss.com/jira/browse/JBCTS-593 - Jean Frederic/Carlo (resolved?)
Testsuites
----------
We have issues with our testsuite runs as they are not running to completion due to server
start/stop issues:
http://jira.jboss.com/jira/browse/JBAS-4939 - JBoss-AS-5.0.x-TestSuite-sun15-noip
http://jira.jboss.com/jira/browse/JBAS-4937 - EJB3
If you work on the AS testsuite, you can record your work/findings here:
http://jira.jboss.com/jira/browse/JBAS-4636
---
For important issues I have missed and we need to track in this status report, please send
me an email.
Thanks
/Dimitris
5:45 p.m.
New subject: AS5 Beta3 status - Nov/14th
We are starting to see significant improvements after the beginning of the metadata
refactoring effort. TCK up to 77% from 38% and AS5 testsuite down to 832 failures from
~1300
last week (72% pass).
Many tck/testsuite problems are caused by deployment issues so this remains the main area
to
work on.
The release criteria for AS5 Beta3 include:
- EJB3 refactoring and Deployer stability
- API stability for MC, metadate, XB
- A satisfying CTS pass rate (96%+)
- Stability of the regular testsuite runs
- Blocker/Critical AS JIRAs
- Profile service
Pending Component Updates
-------------------------
Currently at SNAPSHOT. We should try to move out of those snapshot releases. This is
mostly
a matter of finalizing the metadata refactoring work as XB and WS depend on it.
http://jira.jboss.com/jira/browse/JBAS-4687 - jboss-ejb3-cache (PaulG/Carlo)
http://jira.jboss.com/jira/browse/JBAS-4567 - jbossws (ThomasD)
http://jira.jboss.com/jira/browse/JBAS-4744 - JBossXB 2.0.0.CR5 (Alexey)
http://jira.jboss.com/jira/browse/JBAS-4745 - Metadata (Scott)
Other
http://jira.jboss.com/jira/browse/JBAS-4714 - 2.2.2.SP3 for remoting? (Ron)
Blockers/Critical
-----------------
We are interested in blocker and critical issues. Beyond that 4 out of 5 issues are
sitting
there without progress for a long time so please review your issues and decide what can be
resolved or deferred:
Some JIRA filters for Beta3:
Issues reported by you (current user)
http://jira.jboss.com/jira/secure/IssueNavigator.jspa?mode=hide&reque...
Issues assigned to you (current user)
http://jira.jboss.com/jira/secure/IssueNavigator.jspa?mode=hide&reque...
Unassigned tasks
http://jira.jboss.com/jira/secure/IssueNavigator.jspa?mode=hide&reque...
Deployer refactoring
http://jira.jboss.com/jira/browse/JBAS-3410
http://jira.jboss.com/jira/browse/JBAS-3412 - client deployer/javaee5 support (Scott)
http://jira.jboss.com/jira/browse/JBAS-3415 - rar deployer (was Weston, can Adrian help?)
Metadata Unification
http://jira.jboss.com/jira/browse/JBAS-4506
http://jira.jboss.com/jira/browse/JBAS-4707 - Client deployer (Scott)
http://jira.jboss.com/jira/browse/EJBTHREE-811 - new ejb3 deployers (Carlo?)
http://jira.jboss.com/jira/browse/EJBTHREE-718 - appclient deployer (Carlo?)
Deployers implement ManagedObjectCreator
http://jira.jboss.com/jira/browse/JBAS-4376
http://jira.jboss.com/jira/browse/JBAS-4671 - Adrian
http://jira.jboss.com/jira/browse/JBAS-4672 - Dimitris
WS Release depends on
http://jira.jboss.com/jira/browse/JBAS-4931
http://jira.jboss.com/jira/browse/JBAS-4956
CTS 5.0
-------
The metadata refactorings got us from 96.44% down to 18.16% and back up to 77%.
We need to bring the percentage back to a pre-metadata refactoring level and higher.
The overall status of the refactoring here:
http://jira.jboss.com/jira/browse/JBCTS-673
Open subtasks:
http://jira.jboss.com/jira/browse/JBCTS-692 - Scott
Other CTS tasks:
http://jira.jboss.com/jira/browse/JBCTS-547, 549, 593, 664, 666, 696 - Carlo
http://jira.jboss.com/jira/browse/JBCTS-654, 691 - Scott
http://jira.jboss.com/jira/browse/JBCTS-663 - Jonathan (resolved?)
http://jira.jboss.com/jira/browse/JBCTS-665, 369, 305 - Shelly
http://jira.jboss.com/jira/browse/JBCTS-660 - Stefan
http://jira.jboss.com/jira/browse/JBCTS-652 - Emmanuel / Shelly
http://jira.jboss.com/jira/browse/JBCTS-593 - Jean Frederic/Carlo
http://jira.jboss.com/jira/browse/JBCTS-698, 699 - Anil
http://jira.jboss.com/jira/browse/JBCTS-695 - Andrew
http://jira.jboss.com/jira/browse/JBCTS-671 - Dimitris
Testsuites
----------
We are focusing on the JBoss-AS-5.0.x-TestSuite-sun15 that performs the clustering tests
by
binding to separate IPs (not localhost):
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
JBoss-AS-5.0.x-TestSuite-sun15-noip can be ignored.
If you work on the AS testsuite, you can record your work/findings here:
http://jira.jboss.com/jira/browse/JBAS-4636
The ejb3 testsuite still doesn't run to completion
http://hudson.qa.jboss.com/hudson/view/EJB3/job/ejb3-head-testsuite/
http://jira.jboss.com/jira/browse/JBAS-4937 - EJB3
Maybe we should bind to non-localhost IPs, too?
---
For important issues I have missed and we need to track in this status
report, please send me an email.
Thanks
/Dimitris
6001
days inactive
6069
days old
jboss-development@lists.jboss.org
30 comments
8 participants
participants (8)
-
Anil Saldhana -
Bela Ban -
Brian Stansberry -
Dimitris Andreadis -
Rémy Maucherat -
Scott M Stark -
Steve Ebersole -
Tim Fox