-
Notifications
You must be signed in to change notification settings - Fork 95
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
Can we publish a new release? #144
Comments
@lingster I have been having trouble finding time to continue pushing releases out. Any help would be greatly appreciated. |
@avelis : more than happy to help. If you can set me up with (maintainer) rights to publish, I can take a look in the next day or so, I can also add some release notes to simplify deployment next time too. my pypi account is: "lingster" |
@avelis on pypi you are setup as a maintainer of drf-tracking: https://pypi.org/project/drf-tracking/ |
@aschn : could you kindly help to add me as maintainer to assist with the upkeep of this project? |
+1 |
@avelis : could you kindly permission me to deploy onto pypi? If not may I suggest that we fork this project+rename so that a new version could be published on pypi? |
@lingster Yes. Just fork it, rename it, and redirect people to it. I will even accept a README.md update to say that. |
@avelis : ok so I have forked the repo and renamed as follows: https://github.com/lingster/drf-api-tracking. Currently in the process of getting all the CI working so it can be ready to accept PRs etc |
@avelis : I have completed the fork and there is a new version 1.6.0 of drf-api-tracking which contains all changes so far. Could you kindly update the README and point people to the new repo? |
@lingster Ok. Change made. Godspeed! |
For anyone else who lands here work as continued on in a fork now named drf-api-tracking. |
@avelis : thanks very much! And I guess we can close this issue now! |
Hi,
The last release was more than a year ago. Since then, there were many fixes and updates in the library.
Can we please release a new stable version?
The text was updated successfully, but these errors were encountered: