... | ... | @@ -45,9 +45,9 @@ Stable releases are what you would expect: stable, released infrequently, withou |
|
|
|
|
|
Development releases can be easily identified by an odd major version number: for example, 1.9.0 is a development release. We will continue our development work with 1.9.1, then 1.9.2, and so on.
|
|
|
|
|
|
Our goal is to make the development release available on the last Wednesday of each month. There may be exceptions (such as during holidays), but that's the general plan.
|
|
|
Our goal is to make the development release available on the last Wednesday of each month. There may be exceptions (such as during holidays), but that's the general plan.
|
|
|
|
|
|
We encourage users to test the development releases and report back their findings.
|
|
|
We encourage users to test the development releases and report back their findings.
|
|
|
|
|
|
For more details on the plan, see ISC's Software Support Policy at https://kb.isc.org/docs/aa-00896.
|
|
|
|
... | ... | @@ -195,6 +195,6 @@ The following summarizes changes and important upgrade notes since the previous |
|
|
(Gitlab #1418)
|
|
|
```
|
|
|
|
|
|
Thank you again to everyone who assisted us in making this release possible.
|
|
|
Thank you again to everyone who assisted us in making this release possible.
|
|
|
|
|
|
We look forward to receiving your feedback. |
|
|
\ No newline at end of file |
|
|
We look forward to receiving your feedback. |