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 more like an organizational issue. The testers want to know when some new release is ready for testing. Right now seems, that only way to check if something is changed is to run same tests and hope to get different results.
I propose that server code should put into GitHub and information about software deployments should put there too.
The text was updated successfully, but these errors were encountered:
Ok, I will put the code on the github next week, when I move a bit further with issue-fixing and when we make shibbolized version of the backend compliant wit the new schema.
For the time being I will be commenting on the backend-issues: if it is fixed and on which server is the fixed version deployed. There are three servers: my laptop localhost for fixing issue by issue, then the testing server lux16 (I deploy when after I fixing some reasonable amount of issues), and lux17 where the backend version of lux16 is deployed by a sysadmin after successfull testing. You have access only to lux17.
This is more like an organizational issue. The testers want to know when some new release is ready for testing. Right now seems, that only way to check if something is changed is to run same tests and hope to get different results.
I propose that server code should put into GitHub and information about software deployments should put there too.
The text was updated successfully, but these errors were encountered: