You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Andy Whitcroft <ap...@shadowen.org> on 2004/07/16 19:14:05 UTC
[PATCH] add PROPOSAL email to HACKING
It seems that there is little advice as to the route for a non-commiter
when wishing to propose a revision or issue be ported to a branch.
It makes sense to use the dev@ list and a similar process to [PATCH];
something like [PROPOSAL]. Below is a first take at documenting
this method.
-apw
=== 8< ===
Index: HACKING
===================================================================
--- HACKING (revision 10334)
+++ HACKING (working copy)
@@ -1634,8 +1634,15 @@
meant to be brief summaries to help a reader get oriented; please
don't use the STATUS file for actual discussion, use dev@ instead.
-Here's an example, probably as complex as an entry would ever get:
+Where a non-committer wishes to propose a change for inclusion they
+should email a proposal to `dev@subversion.tigris.org', with a subject
+line that contains the word "PROPOSAL" in all uppercase, for example:
+ Subject: [PROPOSAL] port something cool issue#12345 to branch 1.1.x
+
+Here's an example of a STATUS file entry, probably as complex as an
+entry would ever get:
+
* r98765 (issue #56789)
Make commit editor take a closure object for future mindreading.
Justification: API stability, as prep for future enhancement.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] add PROPOSAL email to HACKING
Posted by Ben Reser <be...@reser.org>.
On Mon, Jul 19, 2004 at 10:20:55AM -0500, kfogel@collab.net wrote:
> Andy Whitcroft <ap...@shadowen.org> writes:
> > Hmmm. Well I wasn't sure. Patch submission seems to be documented in this
> > way so it seems consistent. But realistically its your call. Most
> > proposals are going to come from the committer community anyhow. So
> > perhaps not.
>
> Oh, actually we get a lot of proposals from non-developers (which is
> great). I guess it's hard to know about the proposals that never get
> sent :-), but my instinct is that the people who would be in doubt as
> to how to send in a proposal aren't reading HACKING anyway.
I agree with Karl here. I think trying to document a proposal for
backport procedure is unnecessary. Many non-committers have made such
proposals. Ultimately, to get something backported you have to convince
a committer to nominate and vote for it. I don't think it really
matters how they do it.
--
Ben Reser <be...@reser.org>
http://ben.reser.org
"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] add PROPOSAL email to HACKING
Posted by kf...@collab.net.
Andy Whitcroft <ap...@shadowen.org> writes:
> Hmmm. Well I wasn't sure. Patch submission seems to be documented in this
> way so it seems consistent. But realistically its your call. Most
> proposals are going to come from the committer community anyhow. So
> perhaps not.
Oh, actually we get a lot of proposals from non-developers (which is
great). I guess it's hard to know about the proposals that never get
sent :-), but my instinct is that the people who would be in doubt as
to how to send in a proposal aren't reading HACKING anyway.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] add PROPOSAL email to HACKING
Posted by Andy Whitcroft <ap...@shadowen.org>.
--On 19 July 2004 09:10 -0500 kfogel@collab.net wrote:
> Andy Whitcroft <ap...@shadowen.org> writes:
>> It seems that there is little advice as to the route for a non-commiter
>> when wishing to propose a revision or issue be ported to a branch.
>> It makes sense to use the dev@ list and a similar process to [PATCH];
>> something like [PROPOSAL]. Below is a first take at documenting
>> this method.
>
> Do we really need to document this? Everything else about the project
> says to mail users@ or dev@ (and if someone mails users@ with
> something that really belongs on dev@, they usually get steered to
> dev@ pretty quickly).
Hmmm. Well I wasn't sure. Patch submission seems to be documented in this
way so it seems consistent. But realistically its your call. Most
proposals are going to come from the committer community anyhow. So
perhaps not.
-apw
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [PATCH] add PROPOSAL email to HACKING
Posted by kf...@collab.net.
Andy Whitcroft <ap...@shadowen.org> writes:
> It seems that there is little advice as to the route for a non-commiter
> when wishing to propose a revision or issue be ported to a branch.
> It makes sense to use the dev@ list and a similar process to [PATCH];
> something like [PROPOSAL]. Below is a first take at documenting
> this method.
Do we really need to document this? Everything else about the project
says to mail users@ or dev@ (and if someone mails users@ with
something that really belongs on dev@, they usually get steered to
dev@ pretty quickly).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org