sos
sos copied to clipboard
vatlab
Can sos be marked as "production" now?
SoS has been in beta for a few years and indeed we have changed features of SoS from time to time, including the latest work on remote executions.
I am just wondering how we can lift SoS out of beta status.
I have been thinking about it. We have not added new features for a while -- that's a good sign for lifting beta status. But there are 52 open tickets. We can go through them and decide which are critical ones that makes "production" difficult or impossible. For example, #1424 .
"Production" in the old days means robustness and backward compatibility, but I have seen the latter being tossed around with less emphases. I tend to say we can declare production as long as there are no major bugs and no planned breaking features.
#1424 is annoying but it is strictly speaking not a bug, rather a performance regression (even a necessary regression for the fix of a bug). I had some idea how to fix it but was dragged into something else recently.
From the other ticket:
Oh, local .sos has been removed.
Then this is a change not backwards compatible. But hopefully after we go through all tickets it will stabilize.
Actually, whether or not DSC works could be a good indicator for the production level of SoS -- currently for large benchmarks the experience is still not very smooth. If we want to be stringent about "production" we should perhaps use DSC as a stress test (we have been doing that in the past but still there are rough edges here and there).
Oh, local .sos has been removed.
./.sos was not something documented and users were not encouraged to explore it. With the removal of sos pack/unpack .sos was better stay out of sight of users.
Not sure about other users, but I often find myself deleting .sos folders for specific projects to clean things up. I think snakemake also saves cache in separate folders. .sos folders can indeed be an eye sore particularly when it ends up in Dropbox, Google Drive or github. I suppose users should not have to worry about ~/.sos folder if our engineering is good enough.
Had a quick look at the issue list and they are
- features that could be nice to have, but too complicated to implement now.
- bugs that cannot be reproduced easily or at all
- discussions on details of some features
#1424 looks like the only real issue that should and can be fixed soon(ish).