[Nevernote-announce] NixNote 2.0 Is Out

[General A. a. N. <nev...@li...>]

In the immortal words of Homer J. Simpson, "WOOHOO!" NixNote 2.0 is up on
SourceForge.

After about 5 years I'm finally crazy enough to declare it out of beta.
There are still issues (there will always be issues) but I think this is
"close enough". Thanks to everyone who has contributed to this project!

This is mainly a bug-fix from the last beta. I didn't want to indroduce a
lot of instability, but there are two new features.

- A new Material Light them is provided (thanks to Daniel Maurer).
- The default notebook can be changed by right clicking & selecting the
"Properties" menu option.
- A Ctrl+S will do an immediate save of a note. Prior to this a note was
only saved when the editor lost focus. This is just for people who want
extra assurance that a note was saved.
- A new feature has been added to export a note (or notes) to a PDF. I
wasn't going to indroduce this until 2.0.1, but I had a need for it sooner
so I figured I might as well make it available. This is pretty basic and
just prints the note title & contents. Tags, notebooks, & non of the other
attributes are printed. It also has a limitation that if you have a note
with a colored background, that color is applied to every note in that
export. It is pretty basic, but it comes in handy.

There is also a new Windows release on SourceForge. This will still be
considered beta (beta 12). There are a lot of things that I haven't had the
time to test on Windows and I don't want to hold up the Linux release, so
the Windows release will be beta for a while yet.

As always, if you encounter issues or if I messed up the builds please open
a ticket on GitHub.

Now, on to new business...

For those of you who watch the GitHub repository, there is going to be a
change that I want to make you aware of. Going forward, there will be three
branches: master, development, & experimental. If you are using anything
other than the the master branch and you submit a problem ticket, PLEASE
let me know so I don't waste time trying to debug a problem that may not
exist in that branch.

These different branches will be used like this:

Master branch:
Right now this is the only branch and I've been using it to introduce new
features as well as correct bugs. Going forward it will just be updated
with critical patches to the production release. Don't expect large changes
or new features in this branch. If a critical bug is found it will be
implemented here, but the intent is to make this branch as stable as
possible between releases.

Development branch:
This will be the foundation for the next 2.0.x release. I plan on using
this to introduce minor bug fixes & new features that people have
requested. When this is stable it will be merged into the master branch for
a general release. You are welcome to build against this branch, but be
aware that you could easily run into problems.

Experimental branch:
This will be the fun branch. You can consider this branch my playground and
you can expect it to be more unstable. I'll post more information & ask for
testing volunteers as things progress, but for now I'd recommend avoiding
it.

That's about all. Thanks again for everyone's help! Now, go grab the latest
build on SourceForge & let me know what I've broken or forgotten. I'm going
to relax, and wait for the bug reports to start rolling in!

Randy