Update version to 1.0.0 (prepare for release)

[reta]

Signed-off-by: Andriy Redko andriy.redko@aiven.io

Description

Update version to 1.0.0 (prepare for release)

Issues Resolved

N/A

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[reta]

@dblock please take a look when you have time

[reta]

@dblock please take a look when you have time

[dblock]

@bbarani Do we need to do anything else here related to security reviews?

[dblock]

@dblock please take a look when you have time

Sorry this somehow was below my GitHub email/notifications bar ;(

[bbarani]

@wbeckler @dlvenable please let us know if this needs to wait until security reviews are completed.

[exZStas]

Just wondering: any progress on security reviews?

[nsanaia]

Any thoughts approximately when the release will be done? Thanks

[reta]

@dblock could you please help with security reviews, not sure what it entails?

[wbeckler]

Security reviews are successfully completed and this can be approved.

[wbeckler]

@dblock would you be willing to approve?

[reta]

@gaiksaya could you please enable the release job on Jenkins? https://build.ci.opensearch.org/job/spring-data-opensearch-release/, thank you

[gaiksaya]

@gaiksaya could you please enable the release job on Jenkins? https://build.ci.opensearch.org/job/spring-data-opensearch-release/, thank you

Done!
cc: @bbarani

[reta]

@gaiksaya could you please enable the release job on Jenkins? https://build.ci.opensearch.org/job/spring-data-opensearch-release/, thank you

@gaiksaya I pushed the pre-release 0.2.0 [1] but Jenkins job didn't trigger [2], mind please taking a look?

[1] https://github.com/opensearch-project/spring-data-opensearch/releases/tag/0.2.0
[2] https://build.ci.opensearch.org/job/spring-data-opensearch-release/

[gaiksaya]

@reta, The workflow is based on draft release as a trigger which is generated using release-drafter.yml . I see it is marked as pre-release. You should just push the tag and let it do its thing. Once release is published, you can make is pre-release.

[reta]

@reta, The workflow is based on draft release as a trigger which is generated using release-drafter.yml . I see it is marked as pre-release. You should just push the tag and let it do its thing. Once release is published, you can make is pre-release.

@gaiksaya redid the tag [1] + release [2] - nothing is happening

[1] https://github.com/opensearch-project/spring-data-opensearch/tags
[2] https://github.com/opensearch-project/spring-data-opensearch/releases/tag/0.2.0

[gaiksaya]

Taking a look!

[gaiksaya]

@reta Can you confirm that 0.2.0 tag is based on main? I'll try triggering it from my end
Thanks!

[reta]

@reta Can you confirm that 0.2.0 tag is based on main? I'll try triggering it from my end Thanks!

@gaiksaya yes, it does, latest commit to main

[gaiksaya]

Its running: https://build.ci.opensearch.org/job/spring-data-opensearch-release/9/.
I did not push the tag just deleted the GH release and re-ran the release-drafter workflow. Once the release is successful, the release is auto-published on release. I believe, before it can trigger the workflow the release was published by you :D
The idea is GH release should be published on GH only when the components are out there In this case on maven.

[gaiksaya]

I can see it: https://aws.oss.sonatype.org/content/repositories/releases/org/opensearch/client/spring-data-opensearch-starter/0.2.0/
Feel free to edit the GH release as you want now.

Thanks!

[reta]

Its running: https://build.ci.opensearch.org/job/spring-data-opensearch-release/9/. I did not push the tag just deleted the GH release and re-ran the release-drafter workflow. Once the release is successful, the release is auto-published on release. I believe, before it can trigger the workflow the release was published by you :D The idea is GH release should be published on GH only when the components are out there In this case on maven.

Oh I see now, so it does not work when (pre)release is created using Github, understood, thank you!

[wbeckler]

What's the next step to get this released as a 1.0?

[reta]

What's the next step to get this released as a 1.0?

@wbeckler just an approval from one of the maintainers (@dblock , @dlvenable ), I cannot merge the pull request otherwise

[wbeckler]

@dblock can you take a look? Appsec review is a done.

[wbeckler]

@dlvenable are you okay to approve? The appsec review is complete.

[dblock]

Done! Sorry for the delay.