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

Re: Patch Manager Questions.

From: Gavin Baumanis <gavinb_at_thespidernet.com>
Date: Fri, 15 May 2009 11:50:39 +1000

My intent wasn't so much about any particular "thing".

More a case of for my own documentation as the current PM and for the
next person who comes after me...

it'd be nice to know - as opposed to guessing...

"What do I do as PM - when the dev list receives a patch for XXX. "
Perhaps even a list of (for want of a better word - though I know its
technically wrong) "root" directories...

So a patch for HACKING under the PM role might be something like;


The following paths are Subversion Project managed.

Patch submissions that have not received a response should;
* Be pinged on the dev mailing list.
* Added to the issue tracker after (xxx) days of further silence.

The following paths are not managed by the Subversion Project.
/PathA : managed by ProjectA/ListA - Contactme_at_projectA
/PathB : managed by ProjectB/ListB - Contactme_at_projectB
* When pinging the dev list ensure that you CC the "owner" too.
* these patches do / do not (I don't know which) get added the issue


Just about everyone on the dev list has this knowledge inherently
because you work in the code, you know what belongs where and who to
speak with if you need extra assistance.

A non-committer will not have this information. I currently do not
have this knowledge either.
As paths are added / removed / changed, HACKING can be amended to stay
up to date.

Someone might be able to fill in the gaps for me, but what happens if
I resign my role?
The New PM has to start from scratch again... the Dev list gets the
same questions all over again.
 From my point of view - it would be nice to have a "place" to go to
that has this information - so that I can get on with doing my tasks
as PM as inconspicuously as possible - so the processes just work.


On 14/05/2009, at 11:22 PM, Peter Samuelson wrote:

> [Daniel Shahaf]
>>> i.e., I'm sure there are things to document --- I'm just not sure
>>> that
>>> "svnmerge has its own list" is one of them.
> [Greg Stein]
>> I didn't know that. I'd say "document it"
> On the other hand, if we are distancing ourselves from the 'contrib'
> section (although I don't remember if it was decided to just stop
> shipping it, or to also stop hosting it), this factoid becomes
> somewhat
> less relevant.
> --
> Peter Samuelson | org-tld!p12n!peter | http://p12n.org/

Received on 2009-05-15 03:51:29 CEST

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