pGina, Github, Branches, and You!

[Nate Yocom]

Hello all! This email has been a bit delayed, so I apologize, however
- I've neglected to pass along some information for those of you who
develop/work with the pGina code base directly (Oooska, I'm looking at
you!). As of our official 3.0 release of pGina, we decided to branch
the code into a "stable" and a "development" set of branches.
Specifically, the "master" git branch serves as the feature
development branch and may wobble between "highly stable" and "run for
your lives" at any point in time. The "v3.0" branch exists for
merging important bug/security fixes if necessary only, in the event
that we need to release a minor update to 3.0. Most importantly, this
branch is *feature frozen* - no new features go here. At some
indeterminate point in the future, the "master" branch will again
branch to "v3.1" and we'll start focusing on stability there and leave
the v3.0 branch for historical comparison and continue this trend in
the future.

What this means for you?

- If you are addressing a bug - fix it and issue a pull request
against master, along with a note that it should be merged to v3.0
- If you are adding functionality/features/plugins - put it in
master and issue a pull request

Short version: work against master branch :)

Hope this makes sense, please do let me know if you have any questions!

Thanks,
Nate