These are chat archives for openworm/ChannelWorm
A repository to integrate data, information, scripts, and models of ion channels in C. elegans
As we've discussed before, the data model at this stage is constantly in flux. For this reason, it's hard to write adapters that connect the data model of ChannelWorm (a moving target) with data models from PyOpenWorm (a more stable target).
The reason for PyOpenWorm's stability right now is because of the way we isolate changes to the codebase in a
dev branch. We only push to
master when these features/patches are complete, and everyone agrees that it's time to push.
I propose that we adopt a similar scheme for ChannelWorm, and push all of our changes from patching branches to a
dev branch first, then merge
master when we agree that the changes are significant enough to merit updating the web-app (which reads from master).
This will mean
master is updated less frequently, so the web-app will be updated less frequently as well, which means it will also be more stable.
If you guys agree, we can start merging all our changes into the
dev branch I created; I've already merged some of my own changes in there!
Ok, postponing the adapters you mean? That makes sense.
And yes, I think since we're in a rapid development phase right now, agreeing during a meeting to push to master is more than enough.
Even just creating the
master PR when one thinks the changes in
dev are good to merge would be sufficient, and we can discuss whether to merge inside the PR comments.