heading and added subheadings for the various
aspects.
So long as there are no objections, I can apply the changes tomorrow
and regenerate the site.
snip/
Thanks for doing this.
s/Buzilla/Bugzilla/ (Submitting Patches, 3rd para, 1st sentence).
I'll pick it up if you miss it ;-)
Thanks
a blog
where he says that he followed the guidelines in:
http://jakarta.apache.org/site/source.html#Patches
which do indeed suggest sending patches to the developer mailing list.
I'd like to suggest a change, so that the preferred method of
submitting patches is via Bugzilla or JIRA.
In the case
such a patch on JMeter - the poster helpfully has a blog
where he says that he followed the guidelines in:
http://jakarta.apache.org/site/source.html#Patches
which do indeed suggest sending patches to the developer mailing list.
I'd like to suggest a change, so that the preferred method of
submitting
he says that he followed the guidelines in:
http://jakarta.apache.org/site/source.html#Patches
which do indeed suggest sending patches to the developer mailing list.
I'd like to suggest a change, so that the preferred method of
submitting patches is via Bugzilla or JIRA.
In the case
://jakarta.apache.org/site/source.html#Patches
which do indeed suggest sending patches to the developer mailing list.
I'd like to suggest a change, so that the preferred method of
submitting patches is via Bugzilla or JIRA.
In the case of projects using JIRA, I believe that asks
+1.
I like having one place, Bugzilla, as the 'repository' for patches as
opposed to email lists.
Gary
-Original Message-
From: sebb [mailto:[EMAIL PROTECTED]
Sent: Sunday, March 26, 2006 3:42 AM
To: Jakarta General List
Subject: Submitting patches
Generally I find that patches
method of
submitting patches is via Bugzilla or JIRA.
In the case of projects using JIRA, I believe that asks for a software
grant, so it's important that code is submitted that way.
[Actually, I'm not sure when emailed patches are appropriate...]
I'd also like to split the patch section
sending patches to the developer mailing list.
I'd like to suggest a change, so that the preferred method of
submitting patches is via Bugzilla or JIRA.
In the case of projects using JIRA, I believe that asks for a software
grant, so it's important that code is submitted that way
the guidelines in:
http://jakarta.apache.org/site/source.html#Patches
which do indeed suggest sending patches to the developer mailing list.
I'd like to suggest a change, so that the preferred method of
submitting patches is via Bugzilla or JIRA.
In the case of projects using JIRA
as there are no objections, I can apply the changes tomorrow
and regenerate the site.
snip/
Thanks for doing this.
s/Buzilla/Bugzilla/ (Submitting Patches, 3rd para, 1st sentence).
I'll pick it up if you miss it ;-)
-Rahul
S.
snap
10 matches
Mail list logo