Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] HEAD open for 4.0 development?

On Fri, Jun 19, 2009 at 1:40 PM, Scott Lewis<slewis@xxxxxxxxxxxxxxxxx> wrote:
> 1) We have been asked by the RT PMC to consider slowing down our major
> release cycles (i.e. going to minor releases rather than yearly major
> releases).

I don't remember this. Was this posted to ecf-dev?

> AFAIK, nothing
> like this has been done with EF projects, and so I don't think there is any
> precedent for it...although that doesn't mean that it's necessarily
> impossible.  Anyone have thoughts about this?

I suppose it all comes down to communicating with the public. If we
call the next release 3.1 but breaking API changes were introduced in
some subset of bundles, how will the community know about this?

I've always been of the opinion that we're moving too fast.
Personally, I don't think the changes that have occurred in the past
two years have warranted a major version change. I think the only
reason this has been done is because of API breakage. Nonetheless,
when I realized we were going to release 2.0, I was somewhat
surprised. And when I realized the next one was going to be 3.0, I was
even more surprised. When a major release is made, I think the
assumption is that drastic changes have been introduced. However,
since 1.0, I think the only "big" things that have happened is the
evolution of the filetransfer and discovery APIs and providers and the
introduction of Cola.

A major version change causes a certain amount of hype and if
expectations are not met, these version numbers may lose their real
meaning of API evolution and feature enhancements and turn into
marketing numbers.

Regards,
Remy


Back to the top