Prepare next release (v0.15.0)

[joshuagl]

• Allow Blake (blake2s and blake2b) hashing algorithms (Add blake hashing algorithms to HASHALGORITHMS_SCHEMA #218)
• new features
  • Add nistp384 signature verification support (Add nistp384 signature verification support #228)
  • Allow callers to provide a default keyid in format_metadata_to_key, rather
    than using the default keyid value of a hash of the canonical JSON of the
    key metadata (Add default keyid to format_metadata_to_key #225)
  • Implement files and directories abstraction as an abstract base class;
    StorageBackendInterface, with a concrete implementation for local
    filesystems; FilesystemBackend (Implement filesystem abstraction #232). This enables users, such as tuf,
    to support non-local/non-traditional filesystems, so long as they provide
    an object implementing securesystemslib.storage.StorageBackendInterface.
    All functions which take a StorageBackendInterface default to creating a
    FilesystemBackend object for local filesystem interaction when an object
    isn't provided. This means that behaviour remains the same as in prior
    (0.14.x) releases of securesystemslib, only instead of throwing exceptions
    from the Python standard library a custom, generic, error is thrown:
    securesystemslib.exceptions.StorageError
• removed features
  • Remove support for gzipped files in load_json_file (Remove support for gzipped files in load_json_file #230)

[coveralls]

Coverage remained the same at 98.941% when pulling 69fcc35 on joshuagl:joshuagl/next-release into 1c470b8 on secure-systems-lab:master.

[SantiagoTorres]

so I think we've fell behind a little bit, but I wonder if we want to update the debian metadata in this PR or we'd like to do this on a separate one...

[joshuagl]

I'm not familiar with expectations around the Debian metadata. Are we building/publishing Debian packages somewhere? Or trying to get securesystemslib and friends into Debian?

We have an open PR for Debian packaging #198, perhaps we can handle this separately by updating that PR for 0.15.0?

[SantiagoTorres]

Yeah, I think we could do a separate PR. Let me go ahead and prepare this release