Closed DirkEilander closed 5 years ago
fine with me but shouldn't we wait until all developments are finished, ie before final submission?
are there other current branches which need to be merged into the master at this stage before we release v2? if not I think this might actually be a good time restructure the folders
can the use-native branch be deleted as it was already merged into master? if so, then i will delete it and make the GLOFRIM 2.0 release from the master branch.
I just deleted use-native. I think we should wait with the actual release until we actually submit the supporting paper.
ps. should we bring the slack channel to live again for this kind of conversations?
I'd like to remove the glofrim-py folder which I think is obsolete from the folder structure and move all its content one folder up. This way it will be more like a regular python package. We should investigate if this has any impact, for instance on the sphinx documentation.