-
Notifications
You must be signed in to change notification settings - Fork 27
switch to BaseX #452
Copy link
Copy link
Open
Labels
BaseXIssues concerning the BaseX forkIssues concerning the BaseX forkbackbone:DBIssues related to the database that the SIS is running uponIssues related to the database that the SIS is running upon
Milestone
Description
It's funny, @margaretha , that we haven't had an issue for that, yet :-)
Here's an idea: when we switch, let us leave the master branch as it is, and use 'main' as the branch for Bx development. We'll reset the defaults to that branch. And the master is going to stay locked, receiving only potential recommendation updates (redundantly until end-point switch), and then it's just going to, well, stay there, as part of the project history, while we keep working with dev, formats, and main.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
BaseXIssues concerning the BaseX forkIssues concerning the BaseX forkbackbone:DBIssues related to the database that the SIS is running uponIssues related to the database that the SIS is running upon