# Stork 1.5.0, July 13th, 2022, Release Notes Welcome to Stork 1.5.0, another development release. Due to a shorter release cycle than usual, the set of changes is modest this time. The changes introduced in this version are: **Host reservations**: The work on managing host reservations continues. This release adds the ability to add reservations with DHCP options [#725]. Also, it is now possible to delete existing reservations if they're stored in a database and Kea's `host_cmds` hook is available [#785]. Several UI improvements were implemented: the address prefix range is shown as a hint when making new IP reservations; in case of a mistake, the specific error is shown rather than just a red outline; it's now possible to refresh the host reservations list on demand and without waiting until the periodic update completes [#728]. The Stork ARM has been updated with descriptions of the recent HR changes [#794]. **Demo script**: The Stork demo can be now run with a single script, `stork-demo.sh`. The previous way of running the demo using Rake (`rake demo:up`) is still supported [#761]. **Bug fixes**: Earlier Stork versions had a problem that some statistics were doubled when monitoring two High Availability (HA) servers. This has now been fixed [#710]. A problem with menu items which were not visible on small or low-resolution displays has been fixed [#698]. The build date is now shown properly when hovering over the Stork logo [#744]. The password strength indicator is no longer always gray and now shows the actual strength [#740]. **Testing and build improvements**: A four-month-long effort to rebuild the system tests along with the whole build system has been merged. Although this is not something that's immediately visible to end users, the implications are substantial and will be seen in the long term. With this change, the development team can now reliably run system tests, and can depend on the tests to fail only when a real problem occurs (and not randomly). What's more, the dev team now feels the tests are easier to write and they're useful enough that the return on investment is substantial. This will translate into higher code quality in the long term [#709]. The Docker files have been effectively rewritten as part of the system tests' rebuild [#704]. The Golang version has been upgraded to 1.18 [#788]. The Ruby dependencies have been frozen [#781]. Earlier Stork packages had overly permissive systemd scripts; those permissions have been restricted [#783]. Several dependencies have been updated to secure versions [#805]. System tests now handle old packages more gracefully during upgrades [#526]. **Documentation**: The Stork ARM style has been changed: the highlighting for literal text is now black rather than red. After much deliberation, we feel that this will make the text more readable [#782]. Please see this link for known issues: https://gitlab.isc.org/isc-projects/stork/-/wikis/Known-issues. ## Incompatible Changes None. ## Release Model Stork has monthly development releases, with some exceptions. There is no Stork release planned in August 2022. We encourage users to test the development releases and report back their findings on the stork-users mailing list, available at https://lists.isc.org/mailman/listinfo/stork-users. This text references issue numbers. For more details, visit the Stork GitLab page at https://gitlab.isc.org/isc-projects/stork/issues. ## License Stork is released under the Mozilla Public License, version 2.0. https://www.mozilla.org/en-US/MPL/2.0 ## Download The easiest way to install the software is to use native deb or RPM packages. They can be downloaded from: https://cloudsmith.io/~isc/repos/stork/ 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: https://www.isc.org/pgpkey ISC provides documentation in the Stork Administrator Reference Manual (ARM). It is available on ReadTheDocs.io at https://stork.readthedocs.io/en/latest/, and in source form in [the doc/ directory](https://gitlab.isc.org/isc-projects/stork/-/tree/master/doc). 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. ## Support Free best-effort support is provided by our user community via a mailing list. Information on all public email lists is available at https://www.isc.org/mailinglists/. If you have any comments or questions about working with Stork, please share them to the stork-users list (https://lists.isc.org/mailman/listinfo/stork-users). Bugs and feature requests may be submitted via GitLab at https://gitlab.isc.org/isc-projects/stork/issues. ## Changes The following summarizes changes and important upgrades since the Stork 1.4.0 release. Thank you again to everyone who assisted us in making this release possible. We look forward to receiving your feedback.