Hi Malcolm, It's great that you are going to contribute! Please make your patches against trunk.
2.2 is fairly old at this point. It hasn't been the focus of development in more than a year. We don't use github or pull requests. Check the section on http://wiki.apache.org/hadoop/HowToContribute that talks about "Contributing your work". Excerpt: "Finally, patches should be attached to an issue report in Jira via the Attach File link on the issue's Jira. Please add a comment that asks for a code review following our code review checklist. Please note that the attachment should be granted license to ASF for inclusion in ASF works (as per the Apache License ยง5)." As this says, you attach the patch file to a JIRA that you have created, and then hit "submit patch." I don't think a branch is required for this work since it is just build fixes, right? best, Colin On Mon, Dec 8, 2014 at 3:30 AM, malcolm <malcolm.kaval...@oracle.com> wrote: > I have ported Hadoop native libraries to Solaris 11 (both Sparc and Intel ) > Oracle have agreed to release my changes to the community so that Solaris > platforms can benefit. > Reading the HowToContribute and GitandHadoop documents, I am not 100% clear > on how to get my changes into the main tree. I am also a Git(hub) newbie, > and was using svn previously. > > Please let me know if I am going the correct path: > > 1. I forked Hadoop on Github and downloaded a clone to my development > machine. > > 2. The changes I made were to 2.2.0, can I still add changes to this branch, > and hopefully get them accepted or must I migrate my changes to 2.6 ? (On > the main Hadoop download page, 2.2 is still listed as the GA version ) > > 3. I understand that I should create a new branch for my changes, and then > generate pull requests after uploading them to Github. > > 4. I also registered at Jira in the understanding that I need to generate a > Jira number for my changes, and to name my branch accordingly ? > > Does all this make sense ? > > Thanks, > Malcolm > >
