Closed jbohren closed 2 years ago
Great -- thanks for following up on this.
I support this change, but I don't have time to take this pull request on, sorry. Maybe @timonegk can give it a review and merge.
@timonegk
Currently, the configuration yaml file also contains the blacklist/whitelist terms. In
metadata.py
, there is a function to migrate metadata. The migration to the new terms should be added there.
Yeah that's a good point. See migration in 46126ce
Also, the CI is currently failing. Could you look into that?
Sorry, I don't have the bandwidth for that.
Okay, then I will continue to work on the things that I commented. Do you mind giving me push access to your branch so that I could keep it in this pull request?
Thanks!
On the same note, I also changed the name of the base branch from master
to main
.
@wjwwood I just tagged a new release (0.8.3)
@wjwwood @timonegk thanks for following through on this!
I didn't see it on PyPi, so I pushed it there too.
Debs should be available in a few minutes.
Oh yes, I forgot about PyPi. Thanks for both!
This has now been released as 0.8.3
, but this a breaking change. So this should have been a major release. ðŸ˜
Nothing here is a breaking change.
It is for plugins. For example catkin_tools_document
. As it accesses the black/whitelist
attributes of Context
, see https://github.com/mikepurvis/catkin_tools_document/pull/25/
Ah yes, that's true... Sorry 😕
It is also a breaking change because it auto-migrates config files to the new terms... so after you use the new version once, old versions of catkin will no longer build your project.
Okay, then I would do the following to mitigate the issues:
black/whitlist
attributes of Context
, migrates config files back to the old terms and can deal with both types of arguments. That should add back all breaking changes.Context
class.What do you think of this plan? Did I forget anything?
Overview:
@allenh1 I appreciate you putting the time in to address the poorly chosen terminology present in catkin_tools. This PR adds terminology which I think is clearer and better-suited for this application than "allow" and "deny". Since you made the initial PR, I added you as a coauthor to the main commit in this PR. Let me know if you want me to remove you from that commit.
Note the asciinema videos in the documentation still display the old terminology.
This should supersede: