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

[Gary Feldman <g1list_1a@marsdome.com>] Release note suggestions

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2004-11-12 04:37:58 CET

This from the users@ list just now. Some good suggestions.

attached mail follows:

Having just upgraded to 1.1.1, I have two recommendations to make for
the release notes:

1. Make them available from the Download page, and maybe the home page.
     It took me quite a while to find them.

2. Include a compatibility section. The first question I was asked
when I scheduled the upgrade was whether users would have to upgrade
their clients immediately. I couldn't find an answer to this (but since
the upgrade on Windows was more or less painless, I just did the upgrade
anyway - since other developers had been asking for it for some time).

I'm not asking for all clients to be listed, just a section indicating
the oldest svn command line client that will work with the new server,
and the oldest server that will work with the new command line client.
Even when the answer is trivial (i.e. they all work), it should be
explicitly stated.

Come to think of it, it should probably also indicate the oldest version
that doesn't require the database to be dumped. I know I found a
statement to that effect somewhere (but it was technically wrong, since
it just gave a blanket "unnecessary" without allowing for the
possibility that someone might be upgrading from 0.3 to 1.1.1). I can't
find that statement now, which just reinforces my desire for point 1 above.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Nov 12 04:40:59 2004

This is an archived mail posted to the Subversion Dev mailing list.

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