attach patches (created the same way as with cvs under eclipse or i guess all other tooling that you use) to our jira.
johan On Sat, May 3, 2008 at 2:05 PM, Doug Donohoe <[EMAIL PROTECTED]> wrote: > > I'm looking to start contributing some ideas for enhancements to wicket. > I > have some small enhancements I'd like to contribute first. > > The only page I found for developers is this page > http://wicket.apache.org/building-from-svn.html. Is there another one > which > gives more insight into the Wicket development process. In particular, > I'm > looking for the following: > > A) 1.4 roadmap. What are various developers working on? > > B) Best way to submit a patch - obviously I need to earn commit privileges > first, and I understand the path to that is submitting patches. How does > the team prefer patches to be submitted? I have some very basic questions > about how to submit a patch. I'm interested in details such as: > > a) svn command to generate patch files (this may be an obvious thing, > but > I'm primarily versed in CVS) > b) how to submit patches to multiple files - issue (a) from the top of > the trunk or does it have to be file by file? best way to group multiple > file patches (e.g., jar) > c) where to post patches > > C) Coding standards (other than following what's been done already) > > Thanks and cheers, > > -Doug > -- > View this message in context: > http://www.nabble.com/how-to-contribute---wicket-1.4-plans-tp17034501p17034501.html > Sent from the Wicket - Dev mailing list archive at Nabble.com. > >
