This process should be written up on our website. Things to note and could be added to this documentation: - The pull request should compare against the Apache VXQuery master branch. - The code must pass the VXQuery test suite and the previously passing XQTS tests. (We have pages to document these procedures.) - If the code improves the XQTS test suite performance, we can update our local list of passing tests. (Also on our website.)
On Sun, Jun 28, 2015 at 2:05 AM, Efi Kaltirimidou <[email protected]> wrote: > Yes I will do a pull request today after I make sure all the edited and new > file has the correct format. > > Efi > On Jun 28, 2015 2:10 AM, "Till Westmann" <[email protected]> wrote: > > > Hi, > > > > I’ve started to work on > https://issues.apache.org/jira/browse/VXQUERY-159 > > <https://issues.apache.org/jira/browse/VXQUERY-159> and I’d like to use > > this to understand out GitHub workflow (and potentially add it to the > > website). > > Could you tell me how you are using this so far (who branches what from > > where, where and how the review happens, and how the changes get merged > > back into the ASF repository)? > > > > Thanks, > > Till >
