Re: li'l help on contributing
Once a patch is logged against the bug, it waits until a committer has time to take it on and apply it. This patch will most likely be applied after 1.1, and before 1.2. OT: Solnet thrown you into another Struts project?... At least you don't have to play with RHE's Struts fork we used at Zurich. :) Arron. > This is prolly, blaringly obvious to those that have done this before, > but, after I have created a patch and attached it to the ticket, what > is the process for fixes? > > btw, thanx for the heads up David. > > cheers > Ben > > - Original Message - > From: David Graham <[EMAIL PROTECTED]> > Date: Thursday, June 12, 2003 1:00 pm > Subject: Re: li'l help on contributing > > > Create a patch in cvs diff -u format and attach it to the bugzilla > > ticket. > > David > > > > > > >Hey guys, > > > > > >This is my first (small) foray into the world of open source > > >contributions, so bear with me. I have fixed the code for the > > >enhancement raised in Bugzilla (item 19944). I was wondering what the > > >procedure is for checking these changes in? Does it first need > > approval>(a vote) from the committers? are there any ant targets I > > need to > > >run/show to prove that these changes don't break the existing code. > > > > > >Any help would be greatly appreciated. > > > > > >cheers > > >Ben > > > > > > > > >-- > > --- > > >To unsubscribe, e-mail: [EMAIL PROTECTED] > > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > _ > > Help STOP SPAM with the new MSN 8 and get 2 months FREE* > > http://join.msn.com/?page=features/junkmail > > > > > > --- > > -- > > 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]
Re: li'l help on contributing
This should help you understand the process: http://jakarta.apache.org/struts/faqs/helping.html -- Martin Cooper "Ben Sion" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > This is prolly, blaringly obvious to those that have done this before, > but, after I have created a patch and attached it to the ticket, what > is the process for fixes? > > btw, thanx for the heads up David. > > cheers > Ben > > - Original Message - > From: David Graham <[EMAIL PROTECTED]> > Date: Thursday, June 12, 2003 1:00 pm > Subject: Re: li'l help on contributing > > > Create a patch in cvs diff -u format and attach it to the bugzilla > > ticket. > > David > > > > > > >Hey guys, > > > > > >This is my first (small) foray into the world of open source > > >contributions, so bear with me. I have fixed the code for the > > >enhancement raised in Bugzilla (item 19944). I was wondering what the > > >procedure is for checking these changes in? Does it first need > > approval>(a vote) from the committers? are there any ant targets I > > need to > > >run/show to prove that these changes don't break the existing code. > > > > > >Any help would be greatly appreciated. > > > > > >cheers > > >Ben > > > > > > > > >-- > > --- > > >To unsubscribe, e-mail: [EMAIL PROTECTED] > > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > _ > > Help STOP SPAM with the new MSN 8 and get 2 months FREE* > > http://join.msn.com/?page=features/junkmail > > > > > > --- > > -- > > 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]
Re: li'l help on contributing
This is prolly, blaringly obvious to those that have done this before, but, after I have created a patch and attached it to the ticket, what is the process for fixes? btw, thanx for the heads up David. cheers Ben - Original Message - From: David Graham <[EMAIL PROTECTED]> Date: Thursday, June 12, 2003 1:00 pm Subject: Re: li'l help on contributing > Create a patch in cvs diff -u format and attach it to the bugzilla > ticket. > David > > > >Hey guys, > > > >This is my first (small) foray into the world of open source > >contributions, so bear with me. I have fixed the code for the > >enhancement raised in Bugzilla (item 19944). I was wondering what the > >procedure is for checking these changes in? Does it first need > approval>(a vote) from the committers? are there any ant targets I > need to > >run/show to prove that these changes don't break the existing code. > > > >Any help would be greatly appreciated. > > > >cheers > >Ben > > > > > >-- > --- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > _ > Help STOP SPAM with the new MSN 8 and get 2 months FREE* > http://join.msn.com/?page=features/junkmail > > > --- > -- > 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]
Re: li'l help on contributing
Create a patch in cvs diff -u format and attach it to the bugzilla ticket. David Hey guys, This is my first (small) foray into the world of open source contributions, so bear with me. I have fixed the code for the enhancement raised in Bugzilla (item 19944). I was wondering what the procedure is for checking these changes in? Does it first need approval (a vote) from the committers? are there any ant targets I need to run/show to prove that these changes don't break the existing code. Any help would be greatly appreciated. cheers Ben - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
li'l help on contributing
Hey guys, This is my first (small) foray into the world of open source contributions, so bear with me. I have fixed the code for the enhancement raised in Bugzilla (item 19944). I was wondering what the procedure is for checking these changes in? Does it first need approval (a vote) from the committers? are there any ant targets I need to run/show to prove that these changes don't break the existing code. Any help would be greatly appreciated. cheers Ben - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
