Hi Markus,

On 12/7/21 10:42 AM, Markus Dubois wrote:
when can we expect the next release which is available for the community?

The code has been released on github.com/bareos for everyone.

We're planning ofc Bareos 21, no commited ETA though, only safe answer currently: when it's done.


Thanks.


best,

Frank


frank....@bareos.com schrieb am Montag, 29. November 2021 um 18:13:00 UTC+1:

    Dear Users, Customers and Partners,

    we are happy to announce Bareos 20.0.4 release with some important
    new
    features and fixes available for download in our subscription
    repository
    https://download.bareos.com/bareos/release/20/
    <https://download.bareos.com/bareos/release/20/>. As usual all
    sources are
    available via our GitHub repository github.com/bareos
    <http://github.com/bareos>.

    We're introducing OS support for SUSE Linux Enterprise 15.3 and
    OpenSUSE
    15.3.

    The new Bareos release updates python DIR and SD plugin base
    classes to
    modernized python plugin API. We've fixed occasional volume handling
    bug, when a blocked drive is unloading when non busy. For FreeBSD
    we've
    added checks for file flags in cmake.

    Once again all changes and its details can be found in our most
    current
    changelog
    https://github.com/bareos/bareos/blob/bareos-20/CHANGELOG.md
    <https://github.com/bareos/bareos/blob/bareos-20/CHANGELOG.md>

    We recommend to update your environment to Bareos 20.0.4.

--
Frank Kohler
Bareos GmbH & Co. KG
Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer: Stephan Dühr, M. Außendorf, J. Steffens, P. Storz

--
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to bareos-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/9d7e71af-5cae-7e6f-b386-4997890b266d%40bareos.com.

Reply via email to