Brian,
thank you for the explanation. I realize that I have to submit the patch
through JIRA and wait for someone to have a look at the code. In fact I
have done this, and before I move on and submit more patches I (and any
other contributor) love to hear and to get feed back about the patches
they submit (I am speaking for my self but IMO this is the general case).
As you know, there might be developers who contribute for none profit,
and there are developers who might be sponsored by one of the
organizations. Those who contributes becuase they love to, will loose
movitation when the life cycle is too long. I understand that there is a
definite need for commetters to screen the code and make sure it's
working, however, I find it discouraging when I have to wait few months
before I see my code getting any attention.
You have stated that it will take a committer few weeks. I am little bit
uncertain about "few weeks". Two or three weeks are few. Seven or eight
weeks are few weeks as well.
So, is there a way to have someone to look at the patch in a relatively
short period of time (2-4 weeks may be) ?
Brian Minchau wrote:
The life cyle for a patch is this:
1) Open a JIRA issue at http://issues.apache.org/jira/secure/Dashboard.jspa
against the appropriate project (XalanJ2 or XalanC)
2) Besides describing the problem, also attach the patch, be sure to check
the box that gives Apache the license rights, or else we are dead in the
water on using it.
3) A Xalan committer (someone with write access to the code base) needs to
review/approve the patch and adds such comments to the issue, and a
commiter (probably the same person) would commit the changes to the code
base.
4) The changes are available via extraction of the main branch in SVN and
you can build the binaries yourself, or you can wait for the next release.
If your patch gets some attention the life cycle would be a few weeks. Of
course the time to a new release is longer than that (6 months? A year?)
On step 3, you may be wondering when one would attach a file and not give
Apache the rights. This may be a testcase, which would help in finding a
fix to a problem, yet not be code that you want Apache to include or use in
other ways.
- Brian
- - - - - - - - - - - - - - - - - - - -
Brian Minchau
Mansour
<[EMAIL PROTECTED]
com> To
xalan-dev@xml.apache.org
02/09/2008 01:15 cc
PM
Subject
Accepting a patch
Please respond to
[EMAIL PROTECTED]
che.org
What is the life cycle for accepting a patch. Is there a feed back about
the submitted code ?
How long the whole process will it take?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
