Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [sw360-dev] Planning Eclipse SW360 Release 20.2.0 (Target: November 6th)

Hi,

Thanks for the update. Following the bulk-deletion rollback fix in #4632, I noticed a related failure path worth checking for 20.2.0.

In BulkDeleteUtil, attachment content and usage records are deleted before the parent/component updates are attempted. If a subsequent update encounters a CouchDB revision conflict and the affected releases are retained, could those releases be left pointing to attachment content that has already been deleted?

The regression tests added in #4632 cover retained release records and relationships, but their fixtures have no attachments. I suggest extending the existing CouchDB conflict cases with attachment content and usage records, then verifying that these survive for releases whose deletion fails. I haven’t reproduced this attachment case yet.

Would this be useful to include in the stabilization checks before November 6th? If it confirms data loss, I’d suggest assessing it as a potential release blocker. I’m happy to take on the focused regression test and share the results here.

Best,
Agastya

On Mon, 12 Oct 2026 at 13:10, Gaurav Mishra via sw360-dev <sw360-dev@xxxxxxxxxxx> wrote:
Hi everyone,

I am planning the release of Eclipse SW360 version 20.2.0, targeting November 6th.

Following our 20.1.0 release on July 29th, the project has seen active development with 224 commits to main. Similarly, our frontend has accumulated 198 commits to main, providing a good opportunity to officially tag Frontend version 1.1.0 alongside this release.

The primary focus of 20.2.0 is backend stabilization and functional parity. We are locking down core backend functionalities - such as validation rules and permission boundaries - to match the trusted semantics of version 18. Achieving this baseline stability is a critical milestone before we begin the architectural work of removing the Apache Thrift layer from the backend. Additionally, translation management has been transitioned to Weblate to facilitate community localization efforts.

You can view the full release plan and milestones here: https://projects.eclipse.org/projects/technology.sw360/releases/20.2.0

Please review the plan and reach out with any feedback or questions ahead of the target date.

Best regards,
Gaurav Mishra
_______________________________________________
sw360-dev mailing list
sw360-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sw360-dev

Back to the top