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

RE: [TSVN] TortoiseSVN FAQ

From: Peter Mounce <petermounce_at_iml.co.uk>
Date: 2005-06-23 10:33:17 CEST

> -----Original Message-----
> From: SteveKing [mailto:steveking@gmx.ch]

> But you monitor the mailing list. So you know what's changed
> and what not. Besides, uploading the docs on a daily basis is
> not that easy (well, it's easy, but the docs are 19MB big!).

I do, but there are (might be, hah!) probably people that think along
the same lines as me, that might want to look before they leap. We
wouldn't know, if they don't read the list, of course. That's why I
think nightly, multi-page-html docs on the website (clearly marked,
obviously) would be a good thing. It depends whether you agree with me
when I say that it takes more effort to compose an email and subscribe
to a mailing list (and arrange a new mail client folder, and filter) to
ask about a new feature or change, than it does to do a quick skimmed
comparison of the release docs vs head docs. And of course whether
people do that at all!

If the docs can be transferred via scp, the process could be added to
the nightly build script, potentially...? Not that you'd want a
cleartext login in it - but isn't it possible to use a
not-password-based method of authentication (some kind of encrypted
tokens?) with ssh/scp...? I don't remember.

> > On a more serious note, reading details and seeing
> screenshots about
> > cool upcoming features might induce me to get a nightly and
> install it
> > to try it out.
>
> Most features aren't 'visible', so screenshots won't help.
> For example, the new cache isn't visible, speed improvements
> aren't visible, ...

Sorry, I meant process screenshots like of dialogs, where they're
included to illustrate the text of the docs - but they can also be used
to see how the interface has changed between release and head versions.
Obviously not everything's visible, but for those things that are (there
were lots of UI changes from 1.1.x to 1.2.0).

> > Speaking of the next release, any idea when it might be? The
> > changelog looks almost as long as the 1.2.0 one!
>
> I'll release 1.2.1 as soon as Subversion 1.2.1 is out. Which
> will be some time this week, don't know when exactly.

Cool :)

> About the changelog: yes, it seems bigger. But the changelog
> for 1.2 is far from complete, and most changes (which
> required a *lot* of work) aren't in there because they're
> mentioned in the Subversion changelog (e.g. locking, new API's, ...).
> Also, most changes for 1.2 are explained in one sentence, but
> took weeks to implement, test and get them working. So that's
> why the changelog for
> 1.2 isn't that big.

Ah, ok.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Jun 23 10:35:42 2005

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

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