- openzaak-discuss - nextcloud-publiccode.maadix.org

by Sergei Maertens

Hi folks, Today we released Open Zaak 1.8.0. The big features/improvements are: - Upgraded to Zaken API 1.2.0 - Upgraded to Documenten API 1.1.0 - Added assured delivery for notification publishing - Improved support for managing external API references (e.g. using an external Documents API with Open Zaak) - Performance improvements. This brings us almost up to par with the latest and greatest API standards published by VNG, containing some highly-requested features. We have also worked on reliability and performance of the zaak-create endpoint, with benchmarks showing more than 140,000 cases created per hour by concurrent clients with a 0% error rate! This release also (as usual) contains a number of bugfixes and project maintenance related improvements. The full changelog is available on readthedocs <https://open-zaak.readthedocs.io/en/stable/development/changelog.html#id1>. *Note that upgrading to this release requires some infrastructure changes, so please carefully review the release notes.* The container image is available on Docker Hub and bug reports can be filed on Github. Best, Sergei

4 months, 3 weeks

1
0
0 0

Open Zaak technical steering group meeting on wedensday 7th september

by Tahir Malik

Hi All, There are some points to be discusses and an invite has been send for the 7th September at 14 pm. If you're not invited and part of the Technical team, let me know via mail or slack. Hackmd file with coming notes, agenda points can be added here ==> https://hackmd.io/d8j8ub9_SxqSEDoxDfD2Gw Met vriendelijke groet, [cid:image001.png@01D8B24B.052F8000] Tahir Shazad Malik email tahir.malik(a)contezza.nl<mailto:tahir.malik@contezza.nl> mobile +31 (0)6 14 77 50 82 office +31 (0)848 68 89 02 website www.contezza.nl<http://www.contezza.nl/> [linkedIn]<https://www.linkedin.com/in/tsmalik/> [Twitter]<http://twitter.com/tahirshazad/> Afwezig: vrijdag

9 months, 2 weeks

1
0
0 0

Open Zaak 1.7.0 released (and Open Notificaties 1.4)

by Sergei Maertens

Hi folks, Open Zaak 1.7.0 was just released and Open Notificaties 1.4 was released a couple weeks ago. The new version of Open Zaak implements Zaken API 1.1 and Catalogi API 1.1 - a step towards implementing all the latest versions of the API's from the standard. We've also made a number of improvements to the Catalogi Admin environment which will be welcomed by your admins designing "zaaktypen" :-) Finally, we managed to also fix a number of bugs in Open Zaak again. The full changelog is available on the documentation website <https://open-zaak.readthedocs.io/en/stable/development/changelog.html#id1%3E> . Open Notificaties 1.4 implements some controls to ensure delivery of notifications to subscribers, meaning it will keep retrying a number of times before giving up. The full details and how you can configure this are also specified in the documentation <https://open-notificaties.readthedocs.io/en/stable/changelog.html#id1%3E.>. Once the build has completed, all images will be available on Docker Hub again. Issues and bugs can still be reported to Github. Best, Sergei

10 months, 4 weeks

1
0
0 0

Potential Security incident - no action required

by Sergei Maertens

Hi everyone - this is a notice for the sake of transparency with regard to a potential security vulnerability. The Django team released security fixes related to potential SQL injections. We've audited the Open Zaak code and found no vulnerable code paths that make this exploitable. Updating to new patch versions is tracked on Github: https://github.com/open-zaak/open-zaak/issues/1207

11 months

1
0
0 0

Potential Security incident - no action required

by Sergei Maertens

Hi everyone - this is a notice for the sake of transparency with regard to a potential security vulnerability. The Django team released security fixes related to potential SQL injections. We've audited the Open Zaak code and found no vulnerable code paths that make this exploitable. To track this and prevent it in the future, I've created a Github issue: https://github.com/open-zaak/open-zaak/issues/1136

1 year, 1 month

1
0
0 0

Progress and ambitions for OpenZaak towards the Standard for Public Code

by Jan Ainali

Hello, We're delighted to see that OpenZaak now meet 12 out of 15 criteria of the Standard for Public Code: https://github.com/open-zaak/open-zaak/blob/main/docs/introduction/open-s... Of the remaining criteria, some may already be covered and only need re-review and discussion, whereas others, like "Use plain English" would require investing in improving the codebase and documentation. We would like to hear what ambitions the community has this year to get movement on meeting the Standard for Public Code. Best regards, Jan Ainali, Codebase Steward jan(a)publiccode.net | +46762122776 | @jan_ainali Foundation for Public Code https://publiccode.net

1 year, 1 month

1
0
0 0

Open Zaak 1.6 and Open Notificaties 1.3 released

by Sergei Maertens

Hi everyone! Open Zaak 1.6.0 and Open Notificaties 1.3.0 have just been released. Both releases focused on upgrading our dependencies to keep receiving security fixes from the underlying framework. Users are advised to update as soon as possible to keep receiving future security updates and keep the upgrade path as smooth as possible. Additionally, the container images have been updated to use smaller base images, both reducing the potential attack surface and resulting image sizes. Finally, a number of bugs in Open Zaak were fixed and some periodic project maintenance performed. For the full list of changes and required manual interventions while upgrading, please review the Open Zaak changelog <https://open-zaak.readthedocs.io/en/stable/development/changelog.html#id1> and the Open Notificaties release notes <https://open-notificaties.readthedocs.io/en/stable/changelog.html#id1>. As usual, the container images have been published to Docker Hub <https://hub.docker.com/u/openzaak>.

1 year, 2 months

1
0
0 0

Funding/structural support needed to support Helm Charts as first class citizen

by Sergei Maertens

Hi everyone, I'd like to draw attention to this Github issue about funding: https://github.com/open-zaak/open-zaak/issues/1104 I would like to have this put on an agenda somewhere with people who make the budget-kind decisions. Some more context: recently there has been some questions about the Helm Charts and container images of Open Zaak. In parallel of that, the documentation of deploying on Kubernetes has been rewritten which references these Helm charts. While processing the feedback, a budget issue was raised on Github by me, pointing out the structural need to keep supporting the infrastructure aspect of the community.

1 year, 3 months

1
0
0 0

Community videos and goodbye

by Alba Roza

Hi Open Zaak community, Some personal news as I'm leaving the Foundation for Public Code to start another job in January. I will no longer belong to the organization although I'll still be an enthusiastic public code supporter. I didn't want to leave without sharing the Open Zaak videos I've worked on. Here you can find the (still hidden) playlist <https://youtube.com/playlist?list=PL_5ziu2gADmCnEhBPf2KXXjGqaAdI3epJ> that will be published on Monday. It's been an interesting time where I got to learn a lot about open collaboration and got to know some of you better. I wish you all the best in the future, Alba -- Alba Roza | Codebase Steward Communities & Product alba(a)publiccode.net | @alba_roza Foundation for Public Code | https://publiccode.net

1 year, 5 months

1
0
0 0

🚀 Open Zaak 1.5.0 and Open Notificaties 1.2.1 released

by Sergei Maertens

We are proud to announce the release of Open Zaak 1.5.0! We have introduced a number of new features, such as rootless container images, generic OpenID Connect integration, performance improvements and a number of bugfixes. Additionally, we have also updated the various deployment toolsets. BEFORE upgrading, please make sure to read the release notes ( https://open-zaak.readthedocs.io/en/stable/development/changelog.html#id1) and detailed upgrade instructions, as 1.5.0 requires some special attention. You can read these here: https://open-zaak.readthedocs.io/en/stable/installation/reference/1-5_upg... Additionally, Open Notificaties 1.2.1 has been released for a while without any spotlight shining on it. The 1.2.x line also has container image best practices applied. The changelog is available on https://open-notificaties.readthedocs.io/en/stable/changelog.html. Please note that Open Notificaties no longer supports RabbitMQ as celery result backend. This should not be a problem if you deploy using our Ansible collection or Helm charts, but if you're running your own tooling, you have to switch to Redis for this. You can review the Ansible roles or Helm charts as a reference, they have been updated. We recommend everyone to upgrade to these new versions, if only for the better practices applied in the container images. As a final note and announced earlier in this mailing list, we also want to point out that you can sign up to the "Release Early Notice List" on https://odoo.publiccode.net/survey/start/086e0627-8bc0-4b65-8aa9-f6872aba.... The Open Zaak technical steering team provides these notifications for some releases because system administrators need time to schedule an update, which can be especially important if a security vulnerability was resolved in the update.

1 year, 6 months

1
0
0 0

2023

2022

2021

2020

openzaak-discuss