Steve,
Do you think there is enough material / bug fix to cut another beta for inclusion in AS 6
M2?
Something like a 2 weeks target.
On my side that would make sense to push the discrete but new mapping / bug fixes out for
trial. It also helps Hibernate Search development (on Core snapshot ATM).
Emmanuel
Begin forwarded message:
From: Brian Stansberry <brian.stansberry(a)redhat.com>
Date: 6 janvier 2010 17:38:37 HNEC
To: jboss-development(a)lists.jboss.org
Subject: Re: [jboss-dev] Further profling: Where should I focus?
Reply-To: "JBoss.org development list"
<jboss-development(a)lists.jboss.org>
>
>
> Any ETA on VFS3 being done and integrated with AS 6?
>
My guesstimate is very early in the M3 cycle (i.e. as soon as we open
trunk to commits after M2). So mid-February.
It's tempting to try for M2, but there's only 3.5 weeks left before
component integration freeze, this is a big disruptive change and there
are a couple issues to resolve:
1) Detecting modifications of exploded deployments:
http://community.jboss.org/thread/146098
2) This caching discussion, which IMHO should continue. It's legit to
think again about what the intended use cases are for VFS and see if its
API can be adjusted to more effectively handle those use cases.
The MC team is going to be putting out a 2.2 alpha release soon; while
that's being integrated in the AS and issues resolved over the next week
it makes little sense to try and start pushing in VFS3. So let's use
that time to resolve the modification detection issue and discuss a bit
more about caching. By the end of next week we should have a clearer
picture as to whether trying for M2 is feasible.
--
Brian Stansberry
Lead, AS Clustering
JBoss by Red Hat
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development