Minor release with new unit tests, integration tests, and copy to clipboard

Breaking changes in 1.5.0 from 1.4.0:

• webpaste/open-in-browser has changed name to
  webpaste-open-in-browser
• webpaste/paste-confirmation has changed name to
  webpaste-paste-confirmation

Provider news since 1.4.0:

• Added paste.pound-python.org as a provider
• We have integration tests for all providers that will run
  automatically once a week on travis and as well when someone needs to
  test them locally after making changes.

New options since 1.4.0:

• webpaste-add-to-killring -- You can configure to put the link in
  the kill-ring or not. It's still default to put it there but it can
  be changed.
• webpaste-copy-to-clipboard -- Enable this to copy to clipboard
  using https://github.com/rolandwalker/simpleclip as an optional
  dependency.

Project news since 1.4.0:

• 43 commits by two contributors and documentation updates.
• Changed all the unit tests.
• Added integration tests for the actual providers and not just mock
  data.
• Stricter in following of elisp code style guidelines.

Minor release with more code highlighting, confirmation dialog and open in browser

Breaking changes in 1.4.0 from 1.3.0:

• None known.

Provider news since 1.3.0:

• All providers now supports code highlighting. Before it was just
  dpaste.com, dpaste.de and gist.github.com.

New options since 1.3.0:

• You can configure to have a confirmation dialog before pasting is
  executed to avoid pasting by misstake.
• You can configure to open a created paste in an external browser.

Project news since 1.3.0:

• 15 commits by two contributors and documentation updates.

Minor release that features code highlight for certain providers

Breaking changes in 1.3.0 from 1.2.2:

• None.

Provider news since 1.2.2:

• dpaste.com, dpaste.de and gist.github.com now supports code
  highlighting. The other providers doesn't do this yet due to the very
  different nature of how the providers handle this.

Project news since 1.2.2:

• Eight commits by one contributor, some documentation updates.

Patch release that makes way for more flexible creation of post-data

Breaking changes in 1.2.2 from 1.2.1:

• None.

Provider news since 1.2.1:

• gist.github.com is now available as provider, it's not default so
  you problably have to configure which providers you want if you want
  it as the default one.

Project news since 1.2.1:

• We have made changes of how post-data are built before sent to
  providers - this allows us to make providers with other data than
  just regular post-data. For example, github wanted json. This wasn't
  possible before but now it is.

Patch release that removes no-failover that was recently added

Breaking changes in 1.2.1 from 1.2.0:

• :no-failover for a provider got a short life, now we have pluggable
  error-handlers instead so you choose an error-handler that doesn't
  failover. Then you won't have any failover.

Project news since 1.2.0:

• This change made it possible to have ert testing of all components of
  webpaste so we can ensure consistenty in the future. We have some
  changes planned that's needed to support a wider range of paste
  providers and this was the first step to make it easy to build this.

Second minor update of webpaste

Breaking changes in 1.2.0 from 1.1.0:

• When defining a provider, you previously entered the success-lambda
  as :success, it is now named :success-lambda. This was done in the
  process to make shared lambdas between providers as well as change
  naming to be more describing.
• When defining a provider, you previously entered :domain, which
  wasn't a domain name. It was an URI. So it's now named :uri.

Non-breaking changes in 1.2.0 from 1.1.0:

• When defining a provider, you no longer have to send in :parser
  since it defaults to 'buffer-string, but if you want another parser
  you can still provide that.
• When defining a provider, you can now make that provider not doing
  failovers, the usecase for this is if you have corporate setups with
  private pastebins and want to paste to it using webpaste without
  risking pasting to another provider. But as always, free software, no
  guarantees included with the license. With this we also added
  function to do pastes to a specific provider named
  webpaste-paste-text-to-provider that takes the arguments "text" and
  "provider-name". With this you can make your own paste wrappers for
  specific providers.

Project news since 1.1.0

• In 1.1.0 we added ERT-tests and travis building for automatic tests
  of the code. Since 1.1.0 we also added undercover to get coverage
  reports of the tests on coveralls. Links to this is in the readme
  where you can look at the code coverage. It is not a 100% yet, but
  we're getting there with some more refactoring.
• We have had 25 commits done by a total of 3 contributor since 1.1.0
  that was released on 23rd of Mars (about a month ago).
• General cleanup and lisp fixing to better code style has been done
  after suggestions from others.
• We also do test builds with Emacs 25.2 since it's been released.

First minor update of webpaste

Possibly breaking changes in 1.1.0 from 1.0.0:

• We changed how providers are defined from a macro to a
  function. The function has the same name and takes the same arguments
  as the macro did. So it shouldn't break. This change was done to
  avoid using eval.

Project news:

• We have regression testing in place with ERT and running it for
  every commit through Travis for automatic testing of Emacs with the
  following versions: 24.4, 24.5, 25.1 and snapshot. From this release
  no other versions are properly tested and newer versions will be
  added when they are released.

• We have had 25 commits done by a total of 3 contributors since
  1.0.0 that was back in October.

• New provider as default provider. I recently added ptpb.pw which
  behaves very much like ix.io but with one major difference. They
  support https so I decided to add them and set them as the first
  provider because of that reason.

First stable release

I think the architecture is kinda compete at the moment, so I think this is a good mark for 1.0.0.