Anyone is able to open a ticket in the Bigtop Jira here . You will need
to sign up for a username as as on the wiki.
The rule of thumb here is to make an attempt to check if a similar ticket
is already open before opening new tickets.
You can make the changes to the Bigtop trunk code and generate a patch as
//make a new branch
git checkout -b $ISSUE_NUMBER
//make local changes and commit them
git format-patch master --stdout > $ISSUE_NUMBER.patch
Apply your patch to the issue you created in Jira. Folks can then apply
your patch and run with it.
I would like for some Bigtop PMC's to jump in here as maybe a feature
branch for every patch is a bit of an overkill.
On Fri, Jul 19, 2013 at 8:51 AM, Jay Vyas <[EMAIL PROTECTED]> wrote:
> How can we apply this patch? I had some other updates for the readme as
> well.. Sorry for the ignorance.
> On Fri, Jul 19, 2013 at 11:14 AM, Lewis John Mcgibbney <
> [EMAIL PROTECTED]> wrote:
>> Hi Martin,
>> Do you use bigtop trunk?
>> If so are you able to patch bigtop and file a Jira ticket?
>> On Friday, July 19, 2013, Martin Bukatovic <[EMAIL PROTECTED]> wrote:
>> > Dear all,
>> > I have noticed that in README file inside bigtop repository, the text
>> uses old
>> > and deprecated filepaths:
>> >> * install package testing iTest artifacts locally:
>> >> cd test/src/smokes/package/ && mvn install -DskipTests
>> -DskipITs -DperformRelease
>> >> * use those locally installed iTest package testing artifacts to run a
>> >> cd test/suites/package/ && mvn clean verify
>> > The repo was restructured quite time ago, and I guess that the
>> > should eg. read bigtop-tests/test-execution/smokes instead of
>> > test/src/smokes/package and test/suites/package (but I'm not sure about
>> > second one).
>> > Please review the README and possibly fix it.
>> > Also there are correct instructions on the wiki, so maybe it may be
>> merged or
>> > referenced instead:
>> > Thank you
>> > Martin Bukatovic
> Jay Vyas