252 - Subversion 1.6
What is the enhancement in mind? How should it look and feel?
Please provide any additional information below.
1.6 was released, can we upgrade the repo?
| User | When | Change |
|---|---|---|
| Kaelten | Thu, 30 Sep 2010 21:07:49 | Changed status from New to Fixed |
| sylvanaar | Sun, 21 Jun 2009 04:07:20 | Changed name from Subversion 1.5 to Subversion 1.6 Changed description: Please provide any additional information below. - 1.5 was released, though some 'nix binaries are still 1.4, gcc ftw + 1.6 was released, can we upgrade the repo? |
| Ackis | Tue, 21 Apr 2009 15:08:13 | Changed component from None to Component #18 |
Facts
- Last updated on
- 30 Sep 2010
- Reported on
- 12 Jun 2008
- Status
- Fixed - Developer made requested changes. QA should verify.
- Type
- Enhancement - A change which is intended to better the project in some way
- Priority
- Medium - Normal priority.
- Reply
- #11
sylvanaar Sun, 21 Jun 2009 04:07:20Just keeping this ticket current
- Reply
- #10
sylvanaar Mon, 13 Oct 2008 16:07:16bump
- Reply
- #9
Kaelten Tue, 12 Aug 2008 15:54:26ya pretty much. There is an ubuntu package for it in intrepid but a backport doesn't exist yet
WowAce.com & CurseForge.com Adminstrator
Check out my new addon, OneChoice, it helps you pick quest rewards faster.
Developer of Ace3, OneBag3, and many other addons and libraries
Project lead and Mac developer for the Curse Client
- Reply
- #8
Nevcairiel Tue, 12 Aug 2008 13:10:44Last i heard, Kaelten wants to wait for officially supported Debian/Ubuntu Binaries (or at least backports) for 1.5 before upgrading, we'll see when that happens.
- Reply
- #7
sylvanaar Mon, 14 Jul 2008 03:03:30Updated description
Changed component from 'None' to 'Repositories'
- Reply
- #6
Dashkal Wed, 25 Jun 2008 20:32:29Regarding blocking 1.4 clients from committing. I agree that it's a bad idea to do this site-wide, but it may be a good idea to have an optional commit hook that does so that is turned on or off on a per-project basis. In this manner a project maintainer can mandate a 1.5 (merge tracking) client without cutting off commit access to those who don't care about the new features.
As a social benefit, a commit hook rejection will cause much less drama than revocation of commit access to those who resist upgrading.
- Reply
- #5
sylvanaar Sun, 22 Jun 2008 14:32:40Its released now. (I'm sure you know that)
http://www.tigris.org/servlets/NewsItemView?newsItemID=2132
and tortoise 1.5 has been released
http://tortoisesvn.net/downloads
- Reply
- #4
ckknight Mon, 16 Jun 2008 14:34:24But they've had _11_ RCs. I'm pretty sure that some of those weren't real release candidates. ;-)
- Reply
- #3
sylvanaar Sat, 14 Jun 2008 08:34:12I agree, I did suggest "as soon as its released", which seems like it may be soon
- Reply
- #2
ckknight Fri, 13 Jun 2008 19:07:37I don't really think this is a good idea until Subversion 1.5 actually releases.