Closed dondi closed 3 years ago
I made sure that the features generator had all of the current features in GRNsight beta. I then regenerated the client side testing document, and tested the beta branch. I then updated the client side testing document wiki with the current document iteration.
There is a bug on master. The expression sheet database will load forever, and the nodes look like the picture below when you try and change the bottom data set to something from the database. On beta this occurs temporarily, but resolves once the database expression sheet data loads. The picture also shows the error shown in the web console.
All done, but BioJS status is currently unknown.
This page summarizes the steps that need to be taken when performing the next major GRNsight release. Steps are manual for now, but documenting them is the first step toward facilitating automation in the future.
The list is coded up using checkboxes, so that its source can be copied into a GitHub issue as a starting point for preparing a new release.
beta
branch)beta
) intomaster
master
as neededv#.#.#
(all three numbers are required, even if0
; see npm step below)git push origin <tag-name>
master
clone on grnsight.cs.lmu.edugh-pages
master
withbeta
, especially if hotfixes/merges were made onmaster
gh-pages
beta
clone on grnsight.cs.lmu.edunpm publish
).0
s in the semantic versioncurl -X PURGE https://camo.githubusercontent.com/
camo-GitHub-id in order to update the badge image)