Skip to content

Changes

Page history
Content/grammar edits authored by Suzanne Goldlust's avatar Suzanne Goldlust
Show whitespace changes
Inline Side-by-side
Releases/Release-notes-0.11.md
View page @ 9f489870
......@@ -2,20 +2,19 @@
Welcome to the Stork 0.11.0 release. This is a development release of the Stork dashboard for Kea.
This is somewhat smaller release than usual. Part of the team enjoyed their vacation and those that were in the office, focused on pushing a major release of Kea 1.8.0 out the door. With the holiday period coming to close and full team back in the office, we expect the next Stork release to be a bit bigger.
This is somewhat smaller release than usual. Some team members enjoyed a well-earned vacation this month, and those that were in the office focused on pushing a major release of Kea 1.8.0 out the door. With the summer holiday period coming to a close and the full team back in the office, we expect the next Stork release to be a bit bigger.
The changes introduced in this version are:
1. **Security improvements**. For the last couple months, Stork has been getting new features frequently. This time, we are focusing on security improvements. Many dependencies have been updated to their latest versions without any known vulnerabilities #362, the credentials are now passed in more secure way that's not susceptible to data leakage in proxy logs #375, the sanity checks for log viewer capability is now vastly improved #348.
1. **Security improvements**. For the last couple of months, Stork has been adding many new features in each release. This time, we are focusing on security improvements. Many dependencies have been updated to their latest versions without any known vulnerabilities (#362), the credentials are now passed in a more secure way that is not susceptible to data leakage in proxy logs (#375), and the sanity checks for the log viewer capability are now vastly improved (#348).
2. **UI improvements**. The daemons status of BIND 9 is now displayed correctly #379, the tables are displayed better on low res (720p) devices (#295).
2. **UI improvements**. The status of BIND 9 daemons is now displayed correctly (#379), and the tables are displayed better on low-resolution (720p) devices (#295).
3. **Documentation**. The section explaining how to use Stork agent as Prometheus exporter for BIND 9 was expanded #382.
3. **Documentation**. The section explaining how to use the Stork agent as a Prometheus exporter for BIND 9 was expanded (#382).
4. **Bug fixes**. Stork no longer gets confused when the database access password uses capital letters #361, the daemon status is now presented correctly after recovering from a connection breakdown #384.
4. **Bug fixes**. Stork no longer gets confused when the database access password uses uppercase letters (#361), and the daemon status is now presented correctly after recovering from a connection breakdown (#384).
Please see this link for known issues: for https://gitlab.isc.org/isc-projects/stork/-/wikis/Known-issues
Please see this link for known issues: https://gitlab.isc.org/isc-projects/stork/-/wikis/Known-issues
## Release Model
......@@ -40,11 +39,11 @@ The Stork source and PGP signature for this release may be downloaded from:
https://downloads.isc.org/isc/stork
The signature was generated with the ISC code signing key which is available at:
The signature was generated with the ISC code-signing key which is available at:
https://www.isc.org/pgpkey
ISC provides documentation in the Stork Administrator Reference Manual. It is available on ReadTheDocs.io at https://readthedocs.org/projects/stork/, and in source form in the docs/ directory.
ISC provides documentation in the Stork Administrator Reference Manual. It is available on ReadTheDocs.io at https://stork.readthedocs.io/en/latest/, and in source form in the docs/ directory.
We ask users of this software to please let us know how it worked for you and what operating system you tested on. Feel free to share your feedback on the stork-users mailing list (https://lists.isc.org/mailman/listinfo/stork-users). We would also like to hear whether the documentation is adequate and accurate. Please open tickets in the Stork GitLab project for bugs, documentation omissions and errors, and enhancement requests. We want to hear from you even if everything worked.
......