add some news to the website
This commit is contained in:
parent
3eb2d86d8c
commit
bf4a2ad648
|
@ -0,0 +1,9 @@
|
|||
---
|
||||
layout: post
|
||||
title: Continuous Integration improvements
|
||||
---
|
||||
{% include JB/setup %}
|
||||
|
||||
Release process has been drastically automated, thanks to the powerful tools from github, travis and appveyor. Making a release is now (almost) as easy as tagging the right branch in the github repo: it automatically creates the releases and upload the binaries. So OpenJPEG will eventually have a release cycle that’s worth its name: every 3 months at max, I’ll tag the repo to trigger a new release.
|
||||
|
||||
And, among the bunch of tests that are automatically done for each commit, the results of the API/ABI compliance check is now directly uploaded on the OpenJPEG website: http://www.openjpeg.org/abi-check/timeline/openjpeg/, so that we can follow the compliance from one commit to another.
|
|
@ -0,0 +1,10 @@
|
|||
---
|
||||
layout: post
|
||||
title: OpenJPEG 2.1.0 released
|
||||
---
|
||||
{% include JB/setup %}
|
||||
|
||||
Well, miracles happen, [OpenJPEG 2.1.1](https://github.com/uclouvain/openjpeg/releases/tag/v2.1.1) is released today.
|
||||
|
||||
No fancy additional features, no API/ABI break compared to OpenJPEG 2.1 … Mostly a release with the *huge* amount of critical bug fixes brought to the library since 2 years. A release that will therefore mostly interest linux distributions package maintainers.
|
||||
See full change log [here](https://github.com/uclouvain/openjpeg/blob/openjpeg-2.1/CHANGELOG.md).
|
Loading…
Reference in New Issue