-
Notifications
You must be signed in to change notification settings - Fork 99
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
Move RadioGroup from incubation to release #598
Conversation
83245c0
to
eab6eb9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
commit 2: fixed the versions and organization within releng |
08019dc
to
59555ca
Compare
In general it's preferred to keep a PR to a single commit which you can do by amending and force pushing changes as described here: |
In any case, this looks improved... Let's see how the build goes... |
59555ca
to
434d55d
Compare
squashed & force pushed the commits |
Thank you! ❤️ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have built this locally and it looks good to me.
It's not my decision to make what's promoted to non-incubating, but in terms of releng, the structure and changes look fine.
Hi For me it's ok to move from Incubation to release. @wimjongman is it ok for you too ? |
Yes. |
Since everyone agrees, I will merge. |
This is in a latest nightly build: |
@merks @lcaron @wimjongman thank you! :) |
It's open source great? ❤️ |
Hello and thank you for maintaining Nebula!
Would it be possible to add RadioGroup to release? A project I am maintaining is using it since ~2012.
Please let me know here in case there are any additional requirement regarding the transition.
linked issue: #515 (FormattedText to release)