-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upcoming changes for the next release #562
Comments
@gllmflndn @nbeliy @ChristophePhillips @robertoostenveld @HenkMutsaerts Pinging people who I think should know about this. Will update the top message if there is push-back or more suggestions on this. |
If understand, the As TODO, one think that could be added it's saving/loading/updating bids-matlab structure the initialization of dataset is quite slow, and it can be beneficial to initialize one and then load it from memory, but it can break the path reconstructions (depending how they are constructed). If needed, I can make a separate issue/suggestion. |
Yes. If you want the latest changes you just pull from main. If you want something "stable" then you have to pull a specific tag. If user run into a bug on a stable version then we could:
I think this is issue #320. So we can elaborate there. This has definitely been needed for a while though the ability to index only some subjects or sessions of a dataset can speed things up for some pipelines as you can index only those you will process. In any case I can add this issue to the milestone for the next release but as most of the things listed there I would consider more as nice to have, if we get something together in time rather than something blocking a release. |
Forgot to tag @CPernet. If you think of anyone else please tag them. |
+1 on branch renaming and simpler workflow. |
main and releases is easier to maintain than zillions of branches (although making releases it not fun) +1 |
Adding another change to the TODO:
|
A new BIDS release is on the way for the end of the week. So I will make the changes listed in this issue after and make a new BIDS matlab release after this. |
👍 for the change of license from GPL to MIT. Thank you @Remi-Gau for all the effort you've put into the upcoming release. |
sure, MIT is fine - our US friends need that, thx Remi |
To rename your local master to main git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a |
OK all of those are done so I am closing. Will mop up one thing or 2 and make a github release: should be picked up and released the file exchange too |
The next release will happen shortly after the release of BIDS 1.9.
Planned changes
Note that the change of branches name and workflow may break some users code if they were used to checking out the
dev
branch rather thanmaster
.Renaming of the default branch
Will be changed from
master
tomain
.TODO
Changes from a git-flow to a more typical CI/CD
dev
branch will deleted.main
Reason:
TODO
Release schedule
Minimum will be to have a new version out for each new version of the BIDS specification to allow for a support of new BIDS datatypes or features. This should at least give a "clear" answer on how to organize releases.
The text was updated successfully, but these errors were encountered: