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

No release for over 2 years. #95

Open
hummel-32 opened this issue Nov 8, 2023 · 9 comments
Open

No release for over 2 years. #95

hummel-32 opened this issue Nov 8, 2023 · 9 comments

Comments

@hummel-32
Copy link

Hi,

I have recently updated my lvgl tools and it occurred to me that lv_font_conv hasn't seen any releases for the last two years. Is there a reason why releases have stopped? Are you waiting to complete some milestone before doing the next release?

I think the changes since the last release come in very handy and it would be great if I could just install the package via npm ;)

@puzrin

Best regards,
Hummel

@FederAndInk
Copy link

up, a release would be greatly appreciated 👍

@kisvegabor
Copy link
Member

@puzrin
Please comment about your availability recently.

@puzrin
Copy link
Collaborator

puzrin commented Mar 27, 2024

@kisvegabor Sorry, switched to another projects. As far as I remember, I granted you full admin permissions in npm registry, to avoid any dependencies on me.

Also, users can run any commit via npx https://github.com/lvgl/lv_font_conv?tab=readme-ov-file#install-the-script without waiting for release.

@puzrin
Copy link
Collaborator

puzrin commented Mar 27, 2024

AFAIK, core and binary format are stable for a long time. As soon as LVGL could support binary format instead of custom text one, there will be no need to change anything here.

@kisvegabor
Copy link
Member

Alright, thank you. I just wanted to be sure about your intentions.

I've checked that my NPX account is still working and I see both packages:
image

However, in lack of free time I cannot take the maintenance of this repo either. If you tell me how to create a new release for the package, I can do that, but I cannot contribute with creative and responsible ideas. 🙁

@puzrin
Copy link
Collaborator

puzrin commented Mar 28, 2024

I usually do something like this:

  • git clone ...
  • npm i
  • Make sure changelog is consistent, update if required
  • Update pachage.json with new version
  • Do commit x.y.z. released and add git tag
  • git push
  • npm publish
  • git push --tags

but I cannot contribute with creative and responsible ideas. 🙁

IMHO good project should be stable without creative ideas :). Take a look at the commits history. IMHO those are related to lvgl text format and web only. Core bugs were closed more than 2 years ago.

@kisvegabor
Copy link
Member

Thanks! I've just updated package.json to v1.5.3. Please test it, and if it looks good I'll tag and release it.

@Linjieqiang
Copy link

Please release...

@AvaGhafari
Copy link

@kisvegabor we've tested the last commit, everything works fine with LVGL 9. We would really appreciate if you tag the repo.
Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants