**bump**
On 1/12/06, Chris Scott <[EMAIL PROTECTED]> wrote:
> Hey Adam,
>
> We're looking good I think. Remoting is very very close, and I think
> we just need to tackle FactoryBeans. Off the top of my head I don't
> know what else... Maybe I should check the issue tracker! But
> seriously, Dave says end of January, sounds good to me!
>
> -Chris
>
> On Jan 12, 2006, at 3:30 PM, Adrocknaphobia wrote:
>
> > *bump*
> >
> > I figure I'll ask at least once a month until we have a timeframe.
> >
> > When can we expect a 1.0 release?
> >
> > -Adam
> >
> > On 11/2/05, Dave Ross <[EMAIL PROTECTED]> wrote:
> >> On 11/2/05, Adrocknaphobia <[EMAIL PROTECTED]> wrote:
> >>> That's exactly why I'm asking. I was just curious if there is like a
> >>> feature cut-off.
> >>
> >> Not at all... what 1.0 means to me is that any existing APIs have
> >> been
> >> hardened to the point where they will only change with restrictions
> >> (http://apr.apache.org/versioning.html). For the core BeanFactory,
> >> the
> >> API is already what I consider "solid", AOP is getting there, so
> >> really we aren't that far from 1.0. There's nothing that say features
> >> can't be added post-1.0, either.
> >>
> >> One of the things I stress about ColdSpring (and this carries over
> >> from Spring's mentality) is that whenever possible, new packages are
> >> implemented such that they don't depend on the core framework, and
> >> the
> >> core framework doesn't depend on them. Spring is distributed as
> >> several jars, and while I won't do that with ColdSpring, the same
> >> idea
> >> applies.
> >>
> >> -Dave
> >>
> >>
> >
>
>
>
