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

Re: [Subclipse-users] 1.2.x version of Subclipse

From: Johnathan Gifford <jgifford_at_wernervas.com>
Date: 2006-11-21 19:35:34 CET

I would have everyone use 1.1.8, but our company is bit picky about
using 'beta' code for production use. They don't mind a few people
'evaluating' or 'testing' a beta. But they don't want everyone using
'beta' software.


>>> On Tue, Nov 21, 2006 at 10:07 AM, in message
<45632437.1090707@gmail.com>, Mark
Phippard <markphip@gmail.com> wrote:
> Johnathan Gifford wrote:
>> With the release of SVNKit last week. Does anyone know when the
>> version of Subclipse will be released? We've been holding off on
>> upgrading our Subversion servers because 95% of our developers use
>> Subclipse as their primary way of accessing Subversion repositories.

>> Yes, I know we can upgrade our servers now, but I'm very hesitant
>> because of the 1.4.x and 1.3.x Subversion working copies are not
>> compatible. I also would like for our developers to experience a
>> performance boost with the working copy upgrade and a leaner
>> size at the same time.
> It would be next week at the absolute earliest. That being said I
> a lot of patches to review and there is not much reason to do a
> when I have patches outstanding. More likely it will be a couple of

> weeks. Also, Alex asked me to hold off doing a release because he
> found some bugs in his 1.1.0 release that he wants to fix.
> Why not just use 1.1.8? I also do not see any reason to not upgrade
> servers. That should not effect your developers.
> Mark
> To unsubscribe, e- mail: users- unsubscribe@subclipse.tigris.org
> For additional commands, e- mail: users- help@subclipse.tigris.org

To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Nov 21 19:36:57 2006

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.