Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Release plan for 0.11.0 #3929

Closed
eitsupi opened this issue Dec 13, 2023 · 10 comments
Closed

Release plan for 0.11.0 #3929

eitsupi opened this issue Dec 13, 2023 · 10 comments
Labels
planning
Milestone
0.11

Comments

@eitsupi
Copy link
Member

eitsupi commented Dec 13, 2023

Considering that some great new (breaking) features have been added recently, I'm wondering if it's time to release the next version.
@eitsupi eitsupi added this to the 0.11 milestone Dec 13, 2023
@max-sixty
Copy link
Member

Yes! I can do this this week. Does anyone want to get anything in or shall we go for it?

@aljazerzen
Copy link
Member

I don't have anything that will be landing soon and would be a feature.

@max-sixty
Copy link
Member

Do we want to rename the string module to text? Re discussion at #3913 (comment)

@max-sixty
Copy link
Member

@vanillajonathan do you want to add any of your work to the changelog? You had lots of great changes — e.g. Vite, Lezer, maybe even a rust PR?

max-sixty added a commit to max-sixty/prql that referenced this issue Dec 19, 2023
@max-sixty
0.11.0 changelog
1d4c69d 
Towards PRQL#3929
@max-sixty max-sixty mentioned this issue Dec 19, 2023
Merged
@vanillajonathan
Copy link
Collaborator

vanillajonathan commented Dec 19, 2023 •
edited
Loading

Okay, I filed #3967.

@PrettyWood
Copy link
Collaborator

PrettyWood commented Dec 19, 2023 •
edited
Loading

I would like to merge #3955 and probably plan to rename to text
EDIT: done in df6b59b

@richb-hanover richb-hanover mentioned this issue Dec 19, 2023
Closed
2 tasks
@PrettyWood
Copy link
Collaborator

Last suggestion: #3971
I felt like having proper doc was important and it didn't cost much.
My only question is: should we rename the string module into text? I know @aljazerzen didn't want a module with the same name as the type but maybe the type, which is technical could be string and the module text ? 🤔

@max-sixty
Copy link
Member

My only question is: should we rename the string module into text? I know @aljazerzen didn't want a module with the same name as the type but maybe the type, which is technical could be string and the module text ? 🤔

+1 from me...

@PrettyWood
Copy link
Collaborator

Ok I'll submit another PR for that. And on my part everything should be consistent and documented

max-sixty added a commit to max-sixty/prql that referenced this issue Dec 20, 2023
@max-sixty
0.11.0 changelog
ea6cd11 
Towards PRQL#3929

Merge branch 'main' into changelog

build: Bump versions to 0.11.1

Also update the Readme with a refreshed current status (more modifications welcome there...)
@max-sixty max-sixty mentioned this issue Dec 20, 2023
Merged
@max-sixty
Copy link
Member

Released: https://github.com/PRQL/prql/releases/tag/0.11.0 !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
planning
Projects
None yet
Milestone
0.11
Development

No branches or pull requests
5 participants
@max-sixty @vanillajonathan @aljazerzen @PrettyWood @eitsupi