Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 28 million developers.Sign up
New Features in FOSSology 3.2
The FOSSology development community is pleased to release 3.2. This release information includes changes for release candidate 1 of this release.
Key features in FOSSology 3.2 are:
- Import of SDPX files and showing license result along with browse UI of the upload files and folders
- Word processor document output (for e.g. LibreOffice, OpenOffice) document summarizing analysis information
- Management of obligations a.k.d. license to-dos for licenses
- Brought the package builder infrastructure to work again
After the second release candidate of 3.2, the majority of contributions are therefore in the correction ares (see "fix") and the cleanup of the files and infrastructure (see "chore"). Some statistics:
- What happened since the release candidate for 3.2? The community has merged about 32 pull requests between 3.2 release candidate 1 and this release.
- From release 3.1, a total number of 128 pull requests merged: 56 feature pull requests, 52 pull requests providing corrections, and 20 pull requests improving infrastructure, documentation and testing.
Looking into the git commit history shows you all the users who have contributed to this release since 3.1, the git user names:
99254a5feat(unifiedreport): update phpword from v0.12.0 to v0.13.*
2aab236feat(copyright-testcases): test for getallcopyrightentries for report
7dd9ac9feat(unifiedReport): add user findings of copyright and ecc from files with non-agent finding
f0f484ffeat(treeView): add remove option for deletion of applied irrelevant decisions through file tree edit
ce78359feat(schema): add new combined indexes to database tables copyright, author, ecc, clearing_decision, license_file, uploadtree_a
edaa1adfeat(unifiedreport): add upload history url to title table add groupname next to username correct warnings in obligation
3d0c016feat(report): report assessment summary checkbox selection
62580c8fix(delagent): Delete-Folder without deleting duplicate upload/s in other folders
85ae4bafix(lib): container.php access fix from cache
1a7fcdefix(spdx): make SPDX-rdf and SPDX-tv templates consistend
19a4919fix(unifiedreport): rearrange common and additional obligation text for word report
4deb48cfix(deploy): Fix TimeZone computation when links are used
72ce275fix(common-agents): add check for empty array and false
85ae4bafix(lib): container.php access fix from cache
33d5c2bfix(ui): checkbox param call more adaptable with php 5.4
c48cc64fix(www): change var name to not be used in RegisterMenus
dee3aa2fix(bulk): separate td for each image and add width for select
283352afix(lib): decision for future occurrence of files
439c496fix(treeView): removed license through edit, still exists
56b47eafix(candidateLicense): add a scrollbar to list of files in popup if exceeds 200px
b9d595ffix(obligation): select obligation type and classification by default
a9003b1fix(dep5): add missing endif for deb5 document
a9606e9fix(copyright): fix edit and undo of copyright and ecc
90fd1d8refactor(delagent) use template
9b00ca2Revert "chore(changelog): update to commitlint"
Improvements on Infrastructure, Packaging and Testing
402ae25fix(pb): general correction to enable rpm-based packages
9995f56fix(rpm): Fix VERSION delivery under /etc/fossology
e431594fix(rpm): Copy the correct VERSION file in /etc/fossology for spec
3b73c0ffix(pb): smaller corrections to enable build on master
15e8645chore(make): Remove declaration of COMPOSER_PHAR variable
33431fachore(pb): corrections on the project builder rpm build
bf814ffchore(pb): Provides a working build infrastructure
How to Install 3.2
Please refer to the github release page for the files available:
Unfortunately, the package building infrastructure is moving currently and we do not seem to be stable on the package generation right now.
Fossology uses PHP and Postgresql. Depending on your systems capabilities, you might want to adjust PHP memory settings and Postgresql deployment settings. Please have a look at:
How to Upgrade to 3.2 from 2.5/2.6
Please upgrade from 2.5/2.6 to 3.0 and then try to update to 3.2: Successful migration from 2.5 / 2.6 was one of the topics we have put a lot of care for when looking at 3.0. But from then on, no issue with migrations of previous versions were reported. From a source point of view, we have no doubts that it works.
Unfortunately, the package building infrastructure is moving currently. The works on the release were independent from the moving of the server and thus the release is ready, but the package building server is not. News regarding the new package build infrastructure will be on the mailing list.
As is to be expected, with any release, there are known bugs that users may run into with this release. The ones we know about at this point (and some of the workarounds), are documented here so you don't need to spend time reporting these bugs again.
An overview about current bugs can be seen at: https://github.com/fossology/fossology/issues?q=is%3Aopen+is%3Aissue+label%3Abug
As a general issue, the package building infrastructure is not present at the current time. Therefore, installation from the following methods:
- Provided Debian 8 packages: https://github.com/fossology/fossology/releases/tag/3.2.0
- Using a vagrant script (such as the one provided in the project root structure)
- Using the docker-based deployment, see the project Readme file
- Install from source: https://github.com/fossology/fossology/wiki/Install-from-Source
- We are transitioning to a new build system, so prebuilt images are still being created.
- Did we mention that PHP and Postgresql likely requires adjustments? Please have a look at http://www.fossology.org/projects/fossology/wiki/SysConfig
- none known at this time
- Some licenses have been added to Nomos, as such, old scanner findings could be updated.
- Developers use Firefox and Chrome, sometimes Safari. Maybe, with other browsers, there could be UI issues.
Participate in FOSSology
If you are a developer and want to submit code, start by discussing what you want to do on our developer mailing list firstname.lastname@example.org. Developer documentation can be found at
Your comments, bug reports, patches and suggestions will help fix bugs and improve the quality of future releases. Please report bugs using the issue tracker of the project:
More about FOSSology
To sign up for future FOSSology release announcements, please subscribe to FOSSology's general list at: