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.

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

Release v4.4.0 #706

Closed
dbarnett opened this issue Aug 25, 2024 · 13 comments · Fixed by #720
Closed

Release v4.4.0 #706

dbarnett opened this issue Aug 25, 2024 · 13 comments · Fixed by #720
Assignees
Labels
development Internal issues that mostly affect maintainers vs. end users
Milestone

Comments

@dbarnett
Copy link
Collaborator

Process bug for preparing 4.4.0 release.

Mostly just here to serve as a comment thread for discussing the release...

@dbarnett dbarnett added the development Internal issues that mostly affect maintainers vs. end users label Aug 25, 2024
@dbarnett dbarnett added this to the 4.4 milestone Aug 25, 2024
@dbarnett dbarnett self-assigned this Aug 25, 2024
@dbarnett
Copy link
Collaborator Author

dbarnett commented Aug 25, 2024

@dbarnett
Copy link
Collaborator Author

I've finished all the tasks I'd planned for the 4.4 release except for any straightforward auth improvements (and getting more PRs merged). @mdengler could you look through my 2 PRs I sent you #694 and #700?

Then @insanum @jcrowgey we'll need permission to push an update to PyPI. Is it doable to grant me access to that?

And then my focus for remaining changes will be revisiting auth, #692. I'll be digging in to investigate how it's currently set up and possible directions, but I could use more eyes on that discussion.

@dbarnett dbarnett pinned this issue Aug 27, 2024
@dbarnett
Copy link
Collaborator Author

I've now landed all the changes I was hoping to get into a 4.4 release!

Just figuring out publishing logistics now...

@dbarnett
Copy link
Collaborator Author

@jcrowgey can you grant me access to push gcalcli to testpypi and pypi? Looks like you and @tresni are the only ones with access. Some details at https://pypi.org/help/#project-name.

@jcrowgey
Copy link
Collaborator

jcrowgey commented Aug 27, 2024 via email

@jcrowgey
Copy link
Collaborator

jcrowgey commented Aug 28, 2024 via email

@dbarnett
Copy link
Collaborator Author

@dbarnett
Copy link
Collaborator Author

Release is live on PyPI! https://pypi.org/project/gcalcli/4.4.0/

Now to get to work on the real fun in the next milestone, 4.5: https://github.com/insanum/gcalcli/milestone/10

@dbarnett dbarnett unpinned this issue Aug 29, 2024
@michaelmhoffman
Copy link
Collaborator

Hi @dbarnett, I have not been able to look at this until now. Two things of note that I added earlier are:

I have some scripts I could post somewhere to demonstrate how to use these, but they were designed entirely for my own use and do not meet the usual standard for gcalcli code (that is not sarcasm—despite frequent complaints in the issue tracker, I use gcalcli daily, and it works quite well for me), so probably don't belong in the main repo.

@michaelmhoffman
Copy link
Collaborator

Also, please accept my personal thanks for taking on the leadership of this project. Very much appreciated.

@insanum
Copy link
Owner

insanum commented Sep 16, 2024 via email

@dbarnett
Copy link
Collaborator Author

Aww, thank you! It's been really cool being able to jump into the gcalcli project you've built and revitalize things. ❤️

@michaelmhoffman happy to help get your agendaupdate changes moving again. I'm still trying to get my head around the changes there and current status. Shall I follow up on #550 with general questions/clarifications, or is there a different place to discuss that'd work better?

@michaelmhoffman
Copy link
Collaborator

I am much more responsive over email. My GitHub notifications are overwhelming, frankly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
development Internal issues that mostly affect maintainers vs. end users
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants