Tracking issues of OpenDAL v0.45.1 Release - Locked for unexpected mention

[Xuanwo]

This issue is used to track tasks of the opendal v0.45.1 release.

Plan

Component	Old Version	New Version
core	0.45.0	0.45.1
bin/oay	0.41.0+core.0.45.0	0.41.1
bin/oli	0.41.0+core.0.45.0	0.41.1
bin/ofs	0.0.1+core.0.45.0	0.0.2
bindings/python	0.45.0+core.0.45.0	0.45.1
bindings/nodejs	0.45.0+core.0.45.0	0.45.1
bindings/c	0.44.2+core.0.45.0	0.44.3
bindings/zig	0.0.0+core.0.45.0	0.0.0
bindings/dotnet	0.1.0+core.0.45.0	0.1.1
bindings/haskell	0.44.2+core.0.45.0	0.44.3
bindings/java	0.45.0+core.0.45.0	0.45.1
bindings/lua	0.1.0+core.0.45.0	0.1.1
bindings/ruby	0.1.0+core.0.45.0	0.1.1
bindings/swift	0.0.0+core.0.45.0	0.0.0
bindings/ocaml	0.0.0+core.0.45.0	0.0.0
bindings/php	0.1.0+core.0.45.0	0.1.1
bindings/cpp	0.44.2+core.0.45.0	0.44.3
bindings/go	0.0.0+core.0.45.0	0.0.0
integrations/object_store	0.42.0+core.0.45.0	0.43.0
integrations/dav-server	0.0.0+core.0.45.0	0.0.1

Tasks

Blockers

Blockers are the tasks that must be completed before the release.

Build Release

GitHub Side

• Bump version in project
  • rust
  • cpp
  • haskell
  • java
  • nodejs
• Update docs
• Generate dependencies list
• Push release candidate tag to GitHub

ASF Side

• Create an ASF Release
• Upload artifacts to the SVN dist repo
• Close the Nexus staging repo

Voting

• Start VOTE at opendal community

Official Release

• Push the release git tag
• Publish artifacts to SVN RELEASE branch
• Change OpenDAL Website download link
• Release Maven artifacts
• Send the announcement

Future Works

• Scripts to update version of package
• Scripts to check the version of package
• Split changelog into different packages
• Generate Release Plan

For details of each step, please refer to: https://opendal.apache.org/community/committers/release

[Xuanwo]

Publish dry-run failed for https://github.com/apache/opendal/actions/runs/8004944390/job/21863303313

[Xuanwo]

Publish dry-run failed for apache/opendal/actions/runs/8004944390/job/21863303313

Only rust package failed, we can keep going on and fix the dry-run test in next version.

[Xuanwo]

ERROR    HTTPError: 400 Bad Request from https://test.pypi.org/legacy/          
         '0.45.1+core.0.45.1' is an invalid value for Version. Error: Can't use 
         PEP 440 local versions. See                                            
         https://packaging.python.org/specifications/core-metadata for more     
         information.

[Xuanwo]

Let's take one step back, remove core.0.45.1 from versions.

[Xuanwo]

Waiting for https://issues.apache.org/jira/browse/INFRA-25533

[Xuanwo]

The VOTE for 0.45.1-rc.4 has been started, welcome to take a look, thanks! @apache/opendal-committers

---

I sincerely apologize for the incorrect notifications I sent; I hope this hasn't ruined your day.

I meant to ping opendal-committers but accidentally hit Enter too soon and pinged the apache-committers group instead.

[kxepal]

The VOTE for 0.45.1-rc.4 has been started, welcome to take a look, thanks! @apache/opendal-committers

There is something wrong with committers group reference since I'm not belong to that specific one, but received notification due to this group. May be we should use such with caution....

[Xuanwo]

There is something wrong with committers group reference since I'm not belong to that specific one, but received notification due to this group. May be we should use such with caution....

Apologies for the mistake. I incorrectly pinged @apache/apache-committers.

[JacquesLeRoux]

OK, thanks

[Xuanwo]

I sincerely apologize for the incorrect notifications I sent; I hope this hasn't ruined your day.

[StephanEwen]

Folks, I seem to have accidentally ended up on this thread and the person you really wanted in here is missing :-)

…

On Mon, Feb 26, 2024 at 1:39 PM Xuanwo ***@***.***> wrote: There is something wrong with committers group reference since I'm not belong to that specific one, but received notification due to this group. May be we should use such with caution.... Apologies for the mistake. I incorrectly pinged @apache/apache-committers. — Reply to this email directly, view it on GitHub <#4244 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANFVKR5WCUNJGOKGFQWIS3YVR673AVCNFSM6AAAAABDUNC4PKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRUGA2DSNRWGE> . You are receiving this because you are on a team that was mentioned.Message ID: ***@***.***>

[StephanEwen]

All good, no worries. I just thought the person you really wanted cc-ed here is missing out...

…

On Mon, Feb 26, 2024 at 1:42 PM Xuanwo ***@***.***> wrote: I sincerely apologize for the incorrect notifications I sent; I hope this hasn't ruined your day. — Reply to this email directly, view it on GitHub <#4244 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANFVKQK4YN5JO2ADFDP45TYVR7G7AVCNFSM6AAAAABDUNC4PKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRUGA2TGNZQGU> . You are receiving this because you are on a team that was mentioned.Message ID: ***@***.***>

[tom-pytel]

Likewise, who are all you people? On Mon, Feb 26, 2024 at 7:55 AM Stephan Ewen ***@***.***> wrote:

…

Folks, I seem to have accidentally ended up on this thread and the person you really wanted in here is missing :-) On Mon, Feb 26, 2024 at 1:39 PM Xuanwo ***@***.***> wrote: > There is something wrong with committers group reference since I'm not > belong to that specific one, but received notification due to this group. > May be we should use such with caution.... > > Apologies for the mistake. I incorrectly pinged @apache/apache-committers. > > — > Reply to this email directly, view it on GitHub > <#4244 (comment)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AANFVKR5WCUNJGOKGFQWIS3YVR673AVCNFSM6AAAAABDUNC4PKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRUGA2DSNRWGE> > . > You are receiving this because you are on a team that was mentioned.Message > ID: ***@***.***> > — Reply to this email directly, view it on GitHub <#4244 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMMEGNZQRHGCFXSJAOFQHU3YVSA4FAVCNFSM6AAAAABDUNC4PKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRUGA3DCNRWHE> . You are receiving this because you are on a team that was mentioned.Message ID: ***@***.***>

[melloware]

it seems I can't unsubscribe from this ticket. Can you please delete this ticket and open a new one with the correct list. I think you have CCed the entire Apache Dev list.