[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svnClientAdapter - Release Strategy?

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-06-29 18:54:00 CEST

Gareth Bryan <gareth.bryan@gmail.com> wrote on 06/29/2005 12:11:25 PM:

> Was wondering if anyone lurking on this list is in a position to give
> me some info on the release strategy of the svnClientAdapter piece of
> the project.
>
> The last release of this was done in October 2004, yet there have been
> much more recent releases of subclipse and svnAnt which presumably
> depend on svnClientAdapter.
>
> Moving forward, are there plans to make releases of svnClientAdapter,
> or just subclipse & svnAnt?
>
> Also, are there any plans to bring the API up to date with subversion
> 1.2.0? In fact, in general, what is the policy re keeping up-to-date
> with subversion? Is the requirement to do so driven by subclipse and
> svnAnt?
>
> Much appreciate any pointers. Am thinking of using svnClientAdapter
> directly in my own project and would like to be able to provide
> management with answers to some of these questions.

svnClientAdapter was updated to Subversion 1.2 before it was even GA. We
actually released a compatible Subclipse version on the same day.

I do the Subclipse releases and we now have someone doing svnAnt releases.
 I have not done any specific svnClientAdapter releases, nor do I plan to.
 My assumption is that anyone that wants to build something based on
svnClientAdapter can produce their own build or extract it from Subclipse.

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Thu Jun 30 02:54:00 2005

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.