-
Notifications
You must be signed in to change notification settings - Fork 68
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
Make new release? #225
Comments
Bumping this. This is even more important than before considering further fixes and improvements, for me mostly but not limited to Lua 5.3 integers support. |
Another bump... It's been 3 years already. @pavouk? |
Okay, by this point we probably should make another lgi luarocks package if old one is no longer maintained or contact Luarocks staff to take over old one. It have been WAY too long without release. |
many thanks for your generosity and the invitation. I should have no permissions to make a new release (after all, I’m not even a collaborator [only a contributor]). Besides, I have no proper programming knowledge (very basic Lua scripts with only very basic variables and functions). All I know from that project is that it contains the Lua bindings for GTK+. It would be simply crazy that I released a new version. Many thanks for your help. |
I'm only member at the LGI organization. (I think even my PR's approvals doesn't weight that much (at least, they haven't this green background like yours 🤔)) I guess I can still update the README changelog section and push a new tag 🤷 |
@Aire-One, it seems that now you are the only member in LGI devs (https://github.com/orgs/lgi-devs/people). I think that a new release would help a lot to have more current code as latest released version. |
@psychon @pavouk, I can confirm I don't have the sufficient privilege elevation to push a new tag. I have updated the README History in https://github.com/Aire-One/lgi/tree/prepare-0.10.0 based on the result of
Nahh, don't worry... I'm the only public member, but there are other. |
@Aire-One, from what I read in #225 (comment), @psychon wouldn’t have rights to release a new version either. Only as an average user (not as a coder) and seeing things from the outside, I wonder whether it really makes sense to release a new version. Please, bear with me. Forking the project (and asking @pavouk to transfer ownership of this repo in the meantime) , only makes sense when someone wants to assume the role as its maintainer. The awesome WM depends on this project (as far as I can see). It might be a good reason not to abandon this project. This is my personal opinion (as the rest of this comment), but if this project (LGI) has reached its end, it might be better to let it rest in peace. Many thanks for your help and your contributions. |
Obviously I am not a contributor, nor have any membership in the LGI organization here or GitHub or otherwise but I thought it might be worthwhile to point out that while there has not been a new release in a while there is no reason to consider the project abandoned or even stalled, just the victim of people going AWOL without assigning to others a sufficient amount of permissions to actually create new releases (alternatively they could have assigned such permissions to no one else and forced the development to continue in the form of forks, which in some cases works well enough but in most cases leads to the project dying like "Way Cooler"). Some projects that are still used, such as the But don't doubt yourself, if it is important to you to have it available via Luarocks, you are probably in the best place to maintain the package via releases and can pull any additional developments in this repo to your fork easily enough. You don't need an advanced degree in computer science to do that sort of thing, honestly with how scatter brained the people with those degrees are you might actually be in a better place without the thing. What makes you a true As for a name for a potential fork, my advise would be to use Hope This Finds You All WellThanks for the Hard Work on the Project to All Involved |
luajit download server to tarballs stopped to work, which is expected, since it was advised by the team in https://luajit.org/download.html: "Please do not use obsolete versions from older tarballs or zip files. Please remove any outdated links to these downloads — these links will cease to work soon." --- lua-lgi, on the other hand, is mostly abandonware right now, so it's safe to use latest master. See: lgi-devs/lgi#225
luajit download server to tarballs stopped to work, which is expected, since it was advised by the team in https://luajit.org/download.html: "Please do not use obsolete versions from older tarballs or zip files. Please remove any outdated links to these downloads — these links will cease to work soon." --- lua-lgi, on the other hand, is mostly abandonware right now, so it's safe to use latest master. See: lgi-devs/lgi#225
luajit download server to tarballs stopped to work, which is expected, since it was advised by the team in https://luajit.org/download.html: "Please do not use obsolete versions from older tarballs or zip files. Please remove any outdated links to these downloads — these links will cease to work soon." --- lua-lgi, on the other hand, is mostly abandonware right now, so it's safe to use latest master. See: lgi-devs/lgi#225
It's been a while since last release (about 1.5 years) and lgi got some improvements meanwhile.
Can you, please, consider making new release and uploading it to luarocks? Thank you!
The text was updated successfully, but these errors were encountered: