You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by Jaspreet Singh <Ja...@quark.co.in> on 2004/02/26 08:34:44 UTC

how to send a patch

Hi

i would like to know the process of sending a patch for Axis.

Also, i am working on a standalone app that uses axis for xml-rpc. so the
socket transport layer is modified along with some other changes. what is
the chance that it will be accepted?


Regards
Jaspreet

Re: how to send a patch

Posted by Sam Lang <sl...@mcs.anl.gov>.
On Fri, 2004-02-27 at 20:36, Sanjiva Weerawarana wrote:
> "Sam Lang" <sl...@mcs.anl.gov> writes:
> > 
> > On a side note I'm curious about the AxisC++ process of accepting bugs. 
> > Who gets what and assigns them to the appropriate people?
> > 
> > -Sam 
> 
> As an open-source project there is no one person "in charge" who
> assigns bug fixing or other work to specific developers. Bugs are
> picked up by developers who want to work on those bugs; it may 
> seem too damned chaotic to work but it does work. Yes, it often
> does take longer than if the project were fully managed under 
> the cathedral model but that's not how open source works.
> 
> When a release time comes up the release manager does play the
> role of the "one guy in charge", at least for the duration of
> that release. During the release planning process the specific
> bugs to be fixed are identified (and recorded in the release plan
> document) and then once that's committed the release does not
> go thru until those bugs are fixed. The release manager uses all
> the techniques he can to get the bugs fixed .. and since the 
> release is occurring because the developers want it released (and
> because the release manager is also a developer) the bugs do indeed
> get fixed.

Do release happen after a stated period of time or is it up to the
release manager to decide when enough bugs have been fixed or new
features been added?

> 
> Sanjiva.
> 
> 


Re: how to send a patch

Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
"Sam Lang" <sl...@mcs.anl.gov> writes:
> 
> On a side note I'm curious about the AxisC++ process of accepting bugs. 
> Who gets what and assigns them to the appropriate people?
> 
> -Sam 

As an open-source project there is no one person "in charge" who
assigns bug fixing or other work to specific developers. Bugs are
picked up by developers who want to work on those bugs; it may 
seem too damned chaotic to work but it does work. Yes, it often
does take longer than if the project were fully managed under 
the cathedral model but that's not how open source works.

When a release time comes up the release manager does play the
role of the "one guy in charge", at least for the duration of
that release. During the release planning process the specific
bugs to be fixed are identified (and recorded in the release plan
document) and then once that's committed the release does not
go thru until those bugs are fixed. The release manager uses all
the techniques he can to get the bugs fixed .. and since the 
release is occurring because the developers want it released (and
because the release manager is also a developer) the bugs do indeed
get fixed.

Sanjiva.



Re: how to send a patch

Posted by Sam Lang <sl...@mcs.anl.gov>.
Even better create a bug/feature request at
http://nagoya.apache.org/bugzilla and submit the patch there.  Bugzilla
contains an interface for adding patches to a bug.  This allows you to
keep track of the progress of the patch - and allows other developers to
take responsibility (or not) for merging the patches into CVS.

On a side note I'm curious about the AxisC++ process of accepting bugs. 
Who gets what and assigns them to the appropriate people?

-Sam 

On Thu, 2004-02-26 at 02:22, Sanjiva Weerawarana wrote:
> "Jaspreet Singh" <Ja...@quark.co.in> writes:
> > 
> > i would like to know the process of sending a patch for Axis.
> 
> Update your copy to the latest CVS HEAD version, do a diff (using
> diff -u) and attach the result to an email and send it here.
> 
> > Also, i am working on a standalone app that uses axis for xml-rpc. so the
> > socket transport layer is modified along with some other changes. what is
> > the chance that it will be accepted?
> 
> I'm not sure whether I understand what you've changed; do you actually
> support the XML-RPC protocol? If so then committing that here doesn't
> make sense - look into committing it into the Apache XML-RPC project.
> If you mean that you've improved the "standalone-ness" then please do
> submit the patch with an explanation of what you've done ..
> 
> Sanjiva.
> 


Re: how to send a patch

Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
"Jaspreet Singh" <Ja...@quark.co.in> writes:
> 
> i would like to know the process of sending a patch for Axis.

Update your copy to the latest CVS HEAD version, do a diff (using
diff -u) and attach the result to an email and send it here.

> Also, i am working on a standalone app that uses axis for xml-rpc. so the
> socket transport layer is modified along with some other changes. what is
> the chance that it will be accepted?

I'm not sure whether I understand what you've changed; do you actually
support the XML-RPC protocol? If so then committing that here doesn't
make sense - look into committing it into the Apache XML-RPC project.
If you mean that you've improved the "standalone-ness" then please do
submit the patch with an explanation of what you've done ..

Sanjiva.