<commit_before>## Building for all platforms

If you're lucky and already have all the needed software installed you can just run

```
make
```

If that fails for you (it probably will the first time), don't worry. Follow the OS-specific instructions below and try again. 
If you still run into problems, see the relevant READMEs in the sub directories.

You are definitely going to need [GNU Bison](http://www.gnu.org/software/bison/) 2.7 or newer to build any platform library (except for the JavaScript library).

If you don't already have Bison 2.7 installed then the top level `Makefile` will install it into `./bison-2.7`.

### OS X

OS X ships with an old Bison we can't use. If you prefer to install Bison 2.7 with [Homebrew](http://mxcl.github.com/homebrew/) instead of under `./bison-2.7`,
then you must first install [Homebrew-Dupes](https://github.com/Homebrew/homebrew-dupes) 
before you can install Bison and the other requirements:

```
brew tap homebrew/dupes
brew install bison flex wget node
```

### Ubuntu

Ubuntu users can install the needed software with:

```
sudo apt-get install bison flex wget node mingw32
```

At the time of this writing, `apt-get` will install Bison 2.5, which is too old, so the `Makefile` will install `./bison-2.7` anyway.
When `apt-get` installs Bison 2.7 some day in the future this step will be skipped.

### Fedora

Fedora 18 can install the needed software with:

```
yum install bison flex wget node mingw32-gcc
```

## Making a release

Bump the version in `VERSION` and run `make version`. This updates the version in the package descriptors for all platforms.
<commit_msg>added github process and tips to Developers.md<commit_after>## Building for all platforms

If you're lucky and already have all the needed software installed you can just run

```
make
```

If that fails for you (it probably will the first time), don't worry. Follow the OS-specific instructions below and try again. 
If you still run into problems, see the relevant READMEs in the sub directories.

You are definitely going to need [GNU Bison](http://www.gnu.org/software/bison/) 2.7 or newer to build any platform library (except for the JavaScript library).

If you don't already have Bison 2.7 installed then the top level `Makefile` will install it into `./bison-2.7`.

### OS X

OS X ships with an old Bison we can't use. If you prefer to install Bison 2.7 with [Homebrew](http://mxcl.github.com/homebrew/) instead of under `./bison-2.7`,
then you must first install [Homebrew-Dupes](https://github.com/Homebrew/homebrew-dupes) 
before you can install Bison and the other requirements:

```
brew tap homebrew/dupes
brew install bison flex wget node
```

### Ubuntu

Ubuntu users can install the needed software with:

```
sudo apt-get install bison flex wget node mingw32
```

At the time of this writing, `apt-get` will install Bison 2.5, which is too old, so the `Makefile` will install `./bison-2.7` anyway.
When `apt-get` installs Bison 2.7 some day in the future this step will be skipped.

### Fedora

Fedora 18 can install the needed software with:

```
yum install bison flex wget node mingw32-gcc
```

## Making a release

Bump the version in `VERSION` and run `make version`. This updates the version in the package descriptors for all platforms.

 ## The Github Process

 The process for using git/github as we all start collaborating on bool and other Cucumber projects. This process is similar to the [Github-Flow](http://scottchacon.com/2011/08/31/github-flow.html)

 1. **Anything** in the master branch is good enough to release
 2. Working on new features
     + Create a descriptively named branch off of master (ie: new-oauth2-scopes)
     + Commit to that branch locally and regularly
     + Push your work to the same named branch on the server
     + Regularly rebase this branch from master to keep it up to date.
 3. Open a pull request
     + When you need feedback or help
     + You think the branch is ready for merging (I do this using the [hub](https://github.com/defunkt/hub#git-pull-request) command-line tool -- @mattwynne)
 4. After someone else has reviewed and agreed on the change, you can merge it into master
 Here is an [Example](https://github.com/cucumber/bool/pull/12) of this process in action

 ### Tips for good commits

 1. Read up on [Github Flavored Markdown](https://help.github.com/articles/github-flavored-markdown)
      + especially links and syntax highlighting. GFM can be used in tickets as well as commit messages (e.g. put "#4" somewhere in a commit message to link ticket 4 to that commit.
 2. Close tickets with commits if you can.
     + Add "Closes #5, #9" somewhere in the commit message to both link and close. See [Issues 2.0 the Next Generation](https://github.com/blog/831-issues-2-0-the-next-generation) for details.
 3. Tag issues so we can do better triage and assignment.
     + People tend to gravitate towards areas of expertise and tags makes it easier to give a ticket to the right person.
 4. Update History.md
     + When you fix a bug or add a feature.
     + See gherkin's [History.md](https://github.com/cucumber/gherkin/blob/master/History.md) as a template.
     + Add release dates
 5.  Subscribe to ticket feeds so you stay in the loop and get a chance to provide feedback on tickets.
 6. The code standard is the existing code.
     + Use the same indentation, spacing, line ending and UTF-8 everywhere.
 7. Use git diff (or git diff --cached if you have staged) before every commit.
     + This helps you avoid committing changes you didn't mean to.
 8. Travis continously builds the master branch and any branch that starts with ticket or fix. See [.travis.yml](https://github.com/cucumber/bool/blob/master/.travis.yml)
 This is a good reminder for everyone to give branches descriptive names.
{'fraction_non_alphanumeric': 0.08182912154031288, 'fraction_numerical': 0.0135808836169847, 'mean_word_length': 3.7610474631751227, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 8, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '563841', 'n_tokens_mistral': 1751, 'n_tokens_neox': 1629, 'n_words': 834}