-
Notifications
You must be signed in to change notification settings - Fork 228
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
New release? #213
Comments
Sounds like a good idea.
I need to dust off the release run book. That can't happen this month. But
it is a very good idea.
…On Thu, Oct 12, 2023, 06:06 Greg Oledzki ***@***.***> wrote:
Would it be possible to get a release from current main?
We would appreciate a version with #183
<#183>.
Is there any help needed to make it happen?
—
Reply to this email directly, view it on GitHub
<#213>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB5E6QKLFJGCQFEDV42EVLX653ETANCNFSM6AAAAAA55ANSPU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Sure. That'd be great. We are not in a hurry, just making sure all our dependency stack is kept up-to-date. |
The new release IIRC will contain the change that makes the JAR an automatic module and will play well with JPMS. |
Could you please provide an update on the new release? When can we expect it? |
@tdunning Would you be so kind to offer a comment from your perspective? I appreciate the effort you have put into building and maintaining this library. |
My perspective is that my time is limited while traveling just now. I would
be happy to entertain contributions and would love to build up the
community.
I have thought a fair bit about the problem and would be happy to have a
call or to continue discussion here
…On Fri, Sep 20, 2024, 10:16 Greg Oledzki ***@***.***> wrote:
@tdunning <https://github.com/tdunning> Would you be so kind to offer a
comment from your perspective?
I guess you might see some blockers and might not prefer releasing a new
version. If that's the case, can you please elaborate on what are they? We
as a community could try contributing towards solving these obstacles.
I appreciate the effort you have put into building and maintaining this
library.
—
Reply to this email directly, view it on GitHub
<#213 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB5E6WN53CIYNM74ZYOW23ZXPKUDAVCNFSM6AAAAAA55ANSPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRTGEZTQMRYGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Oh. Great. Let us know what you prefer. |
What timezones are each you guys in? I am in EU (UTC-1) until early October. If that's not where you are, then we should work here. The first order of business is to collect a list of driving issues that indicate a new release is good (java version support, clarify APIs, bug fixes) and a list of blocking issues. Once we have that, we can burn down the blockers and get this out the door. I really appreciate the prod and the productive nature of the comments! |
Would it be possible to get a release from current
main
?We would appreciate a version with #183.
Is there any help needed to make it happen?
The text was updated successfully, but these errors were encountered: