You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is still blocked by open issues in the 24.12 milestone.
If we want to get it out on time we need to do it this week, because next week is Christmas.
release version
24.12 -> moved to 25.01
Preparations
switch to master branch
git pull
npm install --include=dev && npm update
cp js/config/config.dist.ts js/config/config.ts
change the version number in package.json and js/browser/init.json to the new release
Upgrade major dependency versions.
npx npm-upgrade && npm install
upgrade all packages that do not break anything
GitHub
close all open issues in the milestone or move them to another one
close the milestone
Unit Tests
npm run test
Linting
npm run lint
Some errors can be fixed automatically via npm run fix.
Typechecking
npm run typecheck
Manual Tests
clone a fresh copy of SNIK Graph into a temporary folder, see code preparations above
run it in different browsers
the most important test: it needs to load without errors. Make sure to open the console groups. npm run dev may fail to load the submenu indicator image but that should work with npm run build && npm run preview.
clear the cache and local storage and try to load again (press F5)
open a new tab
copy some nodes in the main tab
paste them in the new tab
go back to the main tab
test all the filters (by turning them on and off, some subontology filters like meta may have no effect if they aren't set to load in the config)
hide inter-ontology relations
press recalculate layout
all subontologies must be separate now if meta isn't loaded
show inter-ontology relations again and recalculate
test the day mode (options)
test all links (under Services and Help), Developer Documentation won't work locally
check if the mouseover tooltips are shown when hovering over menu entries (not all entries have tooltips)
"About SNIK Graph" must be correct
test the zoom elements
try if the language switches from English to German and back to English
the language switch must apply both to the menu and to many BB classes
search for "3lgm2 mentity type"
3LGM² Entity Type from the blue book must be highlighted with a yellow color now.
search for "Logical Tool Layer" as well, it must also be highlighted with a yellow color now.
select 3LGM² Entity Type
click and hold the secondary mouse button on "Logical Tool Layer" and choose path, release the mouse button
check if the path is displayed and the labels (on nodes and edges) are existing (scroll to zoom in)
reset view
choose any two not directly connected nodes and test spiderworm, doublestar and starpath in that order (see the manual for what they should do)
reset view again
select any node and test star and circlestar
reset view yet again
hide at least one node and one edge using the contextmenu and del-button
check if the description and the other entries in the contextmenu are working
Publish the release
add, commit and push the release commit
git tag YY.MM && git push origin YY.MM, (replace YY.MM), this will auto create the release on GitHub
ssh into the server
check out the gh-pages branch
The text was updated successfully, but these errors were encountered:
This is still blocked by open issues in the 24.12 milestone.
If we want to get it out on time we need to do it this week, because next week is Christmas.
release version
24.12 -> moved to 25.01
Preparations
npm install --include=dev && npm update
cp js/config/config.dist.ts js/config/config.ts
package.json
andjs/browser/init.json
to the new releaseUpgrade major dependency versions.
npx npm-upgrade && npm install
GitHub
Unit Tests
npm run test
Linting
npm run lint
npm run fix
.Typechecking
npm run typecheck
Manual Tests
npm run dev
may fail to load the submenu indicator image but that should work withnpm run build && npm run preview
.Publish the release
git tag YY.MM && git push origin YY.MM
, (replace YY.MM), this will auto create the release on GitHubThe text was updated successfully, but these errors were encountered: