GRNsight
GRNsight copied to clipboard
dondi
Comment on this issue when beta is refreshed.
I'm opening this issue so that you can post a comment here when the GRNsight beta server is refreshed, so that @kdahlquist (and others) will get an e-mail notification.
The beta has been refreshed with the fix for issue #408. It also includes the tweaks from #397 and #395.
For anyone who refreshes beta in the future, keep in mind that the node apps are now being run from the top directory, not the server and web-client directories. The apps are called using server/app.js and web-client/app.js. This is a direct result of the npm start implementation. npm start can't be used on the beta server itself because of the additional requirements, so running the apps on the parent directory is now required.
Beta was refreshed with the new pull request just before the meeting. It included the fixes for #395, #396, and #399.
Did you increment the version number? Shouldn't we be on 2.0.3 now? I will look at it and post comments on the relevant issues.
My bad -- it did not. I need to review how to refresh beta, I haven't actually done a refresh myself yet.
Since you @anuvarsh, @NAnguiano, and @mihirsamdarshi seem to be working right now, will somebody refresh beta from PR #460 so it is up to date with the beta branch? Thanks.
@kdahlquist @eileenchoe I updated it about 10 mins ago, so it should be up to date now!
@eileenchoe I made a quick guide on the wiki to refresh the server right here. There's a more detailed guide on the wiki if you want to read it as well. :)
While the main beta line is in a pause as @NAnguiano finishes up, I figured it wouldn't hurt to upload the temporary normalization branch from @anuvarsh. This version, bumping to 2.0.17, includes the latest normalization implementation, including restoration of the previously lost functionality.
This version was branched from beta so all of the features from that branch as of May the 4th (be with you) should still be available anyway.
Beta points back to the beta branch now so it is at 2.0.16. If this branch is updated and changed, we should skip to 2.0.18 because normalization was inserted in between.
@kdahlquist When updating version number for beta, noticed that master is at v2.0.20, shouldn't it be v2.0.0?
No, we decided that we would increment it from the last functioning beta. So all betas and masters get unique version numbers. It seemed odd to increment the middle number (like to 2.1.0) since we had never had an official release of 2.0.x, so we went with 2.0.20, which does have a nice ring to it :)
We should target having a master release by June 3 to update with all the stuff you guys are working on now. At that point, we'll go to 2.1.x.
If we have to make any hot fixes on master, we would go to 2.0.21 on master, but that seems unlikely right now.
Make sense?
