Re: [PATCH] notes/releases.txt

In a message dated: 15 Jul 2003 14:56:26 CDT
kfogel@collab.net said:

>> Thoughts/comments?
>
>I think this is backwards.

Hmmm, yup. That's a thought :)

>The real issue here is the assumption that one can be "just" a release
>maintainer, without being familiar with building testing Subversion.

Well, I think there's a difference between 'building' Subversion, and
constantly maintaining a 'build environment'.

I've certainly built Subversion, but not as often as someone who's
constantly developing/hacking on it.

I was looking at this from my experience. I came in to this thinking
I understood what was needed. Mostly, there was nothing required to
perform the job of release manager I didn't understand, it was more a
matter of being able to find the correct information. Which I did,
but after searching in two or three locations. This is what I was
hoping to streamline.

>Sure, if some of those background documents are badly located or
>reduntant anyway, then they can be tweaked until better. But that's
>an independent issue, it has nothing to do with releases. There
>shouldn't be _any_ release-manager-specific tweaks necessary.

I can agree with that. How about I start taking a stab at these
diffent docs to get everything in line with each other?

I'd like to propose:

        mv notes/releases.txt trunk/RELEASING
        mv subversion/tests/clients/cmdline/README trunk/TESTING
        
and adding a DEPENDENCIES listing just external packages,
version numbers, and URLs. This document would then be reference by
all other docs where necessary. It would also be the only place
where version numbers are mentioned.
to start.

Next, I'd like to begin modifying HACKING, README, and INSTALL to
properly cross-reference where necessary.

And, I'll submit a patch for everything for approval :)

Is that reasonable/acceptable?

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