kmradke_at_rockwellcollins.com wrote on Fri, 8 Aug 2008 at 10:03 -0500:
> Stefan Sperling <stsp_at_elego.de> wrote on 08/08/2008 09:46:49 AM:
> > > I guess I'd like more details on when Collabnet wants/needs
> > > a release with new functionality. I'm making an assumption
> > > that the changes they want/need require API and or WC format
> > > changes, which is why 1.6 is being discussed...
> >
> > The changes under discussion are related to client-side authentication
> > features, and do not require WC format changes.
> >
> > Some new client-side public API has been added. But as usual,
> > the APIs are backward-compatible, so if a client compiled against
> > stock 1.5 libraries does not run with the modified ones, there's
> > a bug.
> >
> > The most user-visible change is that the client configuration files
> > understand some new options. Old clients will just ignore these
> > options. Subversion 1.6 will be able to use them.
>
> Do these changes require a minor version number bump, or can
> this just be something like 1.5.2 (beta), just like the
> original 1.5.0 (beta) versions released by collabnet?
>
Our policy is that minor release lines (e.g. 1.5.x) get only bugfixes.
The changes CollabNet wants to include are new features that involve
non-trivial amounts of code and new APIs. Therefore, they can't be
released before 1.6.0.
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-08-08 17:07:43 CEST