Closed PhilippvK closed 9 months ago
Not to be snarky, but pointing downstream projects to any development branch head of an upstream dependency usually calls for trouble, especially with in-development projects ;).
We can add a new tag once the new additions in #109 and #106 have been tested enough (i.e. no-one complains about errors related to them for two weeks).
I don't personally consider packaging pre-built releases that worthwhile, especially as you have to be very careful about library versions and similar things. With #106, the build process of ETISS has become quite a bit more streamlined and should not pose too many problems. I see a docker image loaded with ETISS, some bare minimum ETISS-VP setup, a RISC-V cross-compiler and similar tools as more useful than only packaging ETISS alone.
The new (and very nice) features recently added in #109 and #106 can break downstream projects which used to pull the
master
branch of the ETISS repository and build thebare_etiss_processor
manually.As the latest tag in the repository is already quite old, I would like to propose updating the current version to a new minor release. To fix the aforementioned issue, we could also create one tag before and one tag after these changes. What do you think?
We could also consider packaging a pre-build release and publishing it on GitHub.
Another minor point: GitHub nowadays defaults to
main
as the default branch name. Shall we keep usingmaster
or would a rename make sense here?