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

Looking for co-maintainers #223

Open
siordache opened this issue Dec 25, 2022 · 10 comments
Open

Looking for co-maintainers #223

siordache opened this issue Dec 25, 2022 · 10 comments

Comments

@siordache
Copy link
Member

I'm looking for co-maintainers who can help keep the plugin alive. If you're interested, please leave a comment here. Anyone who is willing to help is welcome!

@airsquared
Copy link
Collaborator

@siordache I'd be happy to help out.

@siordache
Copy link
Member Author

That's great, thanks! I sent you an invitation.

@airsquared
Copy link
Collaborator

Thanks! Would it be ok if I bumped the minimum Java to Java 17? That's the first LTS where jpackage is not preview/incubator.

@siordache
Copy link
Member Author

Definitely. Thanks for your help, it's really great to have you as a co-maintainer!

@airsquared
Copy link
Collaborator

Great! How would I go about releasing a new version of the plugin?

@siordache
Copy link
Member Author

I configured the GRADLE_PUBLISH_KEY and GRADLE_PUBLISH_SECRET secrets and added a manual GitHub action for publishing the plugin to the Gradle Plugins Portal. I didn't test it though, so you may need to adjust it a bit.
Set pluginReleaseBuild to true in gradle.properties. You can play with it before publishing the release by setting the pluginVersionLabel to some value (for example alpha-1).

@airsquared
Copy link
Collaborator

Thanks! Released the next version.

@DaiYuANg
Copy link
Contributor

DaiYuANg commented Mar 5, 2024

I'd be happy to help out too

@xzel23
Copy link
Collaborator

xzel23 commented Sep 21, 2024

Hi @siordache, @airsquared ,

there are several bugs that have been fixed since the last release and I think a new release would be a good thing. If both of you do not have the time, I'd volunteer to become a co-maintainer and spin a new release.

List of fixed bugs/PRs I'd recommend to include in a new version:

@siordache
Copy link
Member Author

Hi @xzel23 , I've sent you an invitation to become a maintainer. I'm very grateful for your help!

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

4 participants