Many of our users don't follow the development of TortoiseSVN about what's
going on, what's planned for the next release and what's already
implemented. So I thought I write a little summary to keep you updated.
what we are currently working on:
Subversion has recently merged two big new features from their branches to
the main trunk. Those new features are 'sparse
directories<http://svn.collab.net/repos/svn/trunk/notes/sparse-directories.txt>'
and 'merge tracking <http://subversion.tigris.org/merge-tracking/index.html>'.
This means for us that we have to make good use of those features, implement
them in TortoiseSVN and give them a nice GUI.
While we've already implemented most of the new APIs, there's still a lot to
be done. And of course we have to try the new features and help the
Subversion guys to find as many bugs as possible. After all, we all want the
new features to be as stable as possible.
If you want to know more about those two new features, you can read about
the concepts in the Subversion source
tree<http://svn.collab.net/repos/svn/trunk/notes/>.
There doesn't exist much documentation yet for these, as they're brand new.
And as you may know from experience, the documentation is always way behind
the development itself.
Besides that, we're of course always working on smaller issues not worth
mentioning here, or fixing bugs. Whenever we feel we could get bored, a new
bug surfaces which keeps us busy.
What needs to be done before 1.5.0:
As already mentioned, the new features Subversion will have finished for
their 1.5.0 release are not fully implemented in TortoiseSVN yet. That will
take most of our time.
Of course, there are some outstanding issues left in our issue
tracker<http://issues.tortoisesvn.net/>,
which still have a chance to make it into 1.5.0.
We are not sure if we can get the log message
caching<http://issues.tortoisesvn.net/?do=details&task_id=45>done for
the
1.5.0 release. But even if we don't get it ready, we won't drop the idea.
Besides that, we like to not plan too much. It doesn't help if we make a
plan with too many features in it, only to discover that we can't possibly
do all what we've planned.
What is already implemented:
It's already been some time since we released version 1.4.0 and created the
branch for the 1.4.x stable releases. And since that time, we've been adding
new features on trunk. Features of which you might not have heard yet.
Some of those features are:
- Client-side hook scripts
TortoiseSVN can execute scripts before and after certain operations
like update or commit. You can use this to run e.g. a validation
script to make sure all your files conform to some coding guidelines. See
issue #137 <http://issues.tortoisesvn.net/?do=details&task_id=137> and
#322 <http://issues.tortoisesvn.net/?do=details&task_id=322> for
details.
- If you're using refactoring tools which rename/move files around,
you're usually stuck with a broken working copy because the refactoring tool
doesn't rename/move the files with the appropriate Subversion command. Which
means the rename/move left you with the original file marked as 'missing',
and the new file marked as 'unversioned'.
TortoiseSVN can fix this
now<http://issues.tortoisesvn.net/?do=details&task_id=273>.
In the commit dialog you can select the two files (the 'missing' one and the
corresponding unversioned one', right-click and execute the "repair
move/rename" command.
- TortoiseMerge got an UNDO function, and can finally read files with
inconsistent newlines without problems.
- Another new feature in Subversion 1.5.0 are so called change
sets<http://svn.collab.net/repos/svn/trunk/notes/changelist-design.txt>.
A change set is useful if you're working on different issues at the same
time, and don't want to accidentally commit a file which 'belongs' to
another issue. You can assign each file to a change set, and then later
commit only the files which belong to a certain change set.
To help you deal with change sets, TortoiseSVN shows you the files
grouped together in the commit dialog, similar to how the XP explorer can
group files.
- The repository browser was rewritten from scratch. It now uses two
panes (like e.g. the windows explorer) with a tree view on the left,
and a list view on the right side. It's also a lot faster when browsing big
directories.
These are only the bigger things that are already implemented. If you want
to see a more detailed list, have a look at our
changelog<http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/src/Changelog.txt>(login:
'guest', leave password empty) and our issue
tracker<http://issues.tortoisesvn.net/index.php?string=&project=1&search_name=&due%255B%255D=14&reported%255B%255D=&cat%255B%255D=&status%255B%255D=&opened=&dev=&closed=>
.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on Fri Apr 13 13:32:05 2007