Skip to content

[Release] 18.2.0 #574

Closed
Closed

Description

@kou

Describe the enhancement requested

I think that we can release a new version from apache/arrow-java now.

#571 is a problem but it's not a blocker for 18.2.0.

@lidavidm @wgtmac Can I release 18.2.0 or do you want to become a release manager?

Activity

  1. lidavidm commented on Jan 30, 2025

    @lidavidm
    Member

    @wgtmac I think you wanted to run this?
    @jbonofre giving you a heads up here too

    If not go for it Kou!

  2. jbonofre commented on Jan 30, 2025

    @jbonofre
    Member

    @lidavidm Thanks ! Happy to be release manager if it's ok 😄

  3. kou commented on Jan 30, 2025

    @kou
    MemberAuthor

    OK! I will help you!

    https://github.com/apache/arrow-java/blob/main/dev/release/README.md is the release procedure.
    Some operations need Arrow committer/PMC member permission. I'll do them.

    Here are tasks that you can do:

    1. Test the revision to be released
      • Could you work on this?
    2. Bump version for new release (detailed later)
      • We don't need this for the next release because we already bumped.
    3. Prepare RC and vote (detailed later)
      • I'll push tag and then you can start a vote on the dev@arrow.apache.org mailing list.
      • You can generate a vote email template by RELEASE_DEFAULT=0 dev/release/release_rc.sh ${RC}
    4. Publish (detailed later)
      • I'll do this because this needs Arrow PMC member permission.
    5. Bump version for new development (detailed later)
      • Could you work on this?
  4. jbonofre commented on Jan 30, 2025

    @jbonofre
    Member

    Thanks @kou !

    Let me start with (1), build but also quick test and legal check.
    I will keep you posted when 1 is done.

  5. jbonofre commented on Jan 30, 2025

    @jbonofre
    Member

    I found issue in the LICENSE/NOTICE in some distributed jar files (like arrow-vector-shade-format-flatbuffers).
    I'm preparing a PR to fix that.

  6. lidavidm commented on Jan 30, 2025

    @lidavidm
    Member

    BTW, should we create/push tags for 18.1.0 (and maybe 18.0.0)? Since we don't have any historical tags after splitting from apache/arrow

  7. jbonofre commented on Jan 30, 2025

    @jbonofre
    Member

    BTW, should we create/push tags for 18.1.0 (and maybe 18.0.0)? Since we don't have any historical tags after splitting from apache/arrow

    I would create some GitHub Issues on the milestone as a start.

  8. lidavidm commented on Jan 30, 2025

    @lidavidm
    Member
  9. added this to the 18.2.0 milestone on Jan 30, 2025
  10. jbonofre commented on Jan 30, 2025

    @jbonofre
    Member

    Thanks @lidavidm ! Let me do a quick git log to create some issues 😄

  11. lidavidm commented on Jan 30, 2025

    @lidavidm
    Member

    I moved all the pull requests already.

    It seems the new github UI does not let me mass select issues! What product manager came up with that bright idea...

  12. lidavidm commented on Jan 30, 2025

    @lidavidm
    Member

    Oh, if I refresh it somehow shows the checkboxes again...

  13. kou commented on Jan 30, 2025

    @kou
    MemberAuthor

    BTW, should we create/push tags for 18.1.0 (and maybe 18.0.0)? Since we don't have any historical tags after splitting from apache/arrow

    I think that we should not create 18.1.0 tag because we don't have the same code base as 18.1.0 in apache/arrow that can be built correctly. We proceeded apache/arrow -> apache/arrow-java migration and bug fixes/feature implementations in parallel.

  14. lidavidm commented on Jan 30, 2025

    @lidavidm
    Member

    OK, I guess we can make a changelog with a manual git log then

  15. 25 remaining items

  16. lidavidm commented on Feb 18, 2025

    @lidavidm
    Member

    We also need to close the milestone. I'll close 18.2.0 and open 18.3.0.

  17. jbonofre commented on Feb 18, 2025

    @jbonofre
    Member

    We also need to close the milestone. I'll close 18.2.0 and open 18.3.0.

    Yes. Ok for 18.3.0. Having both 19.0.0 and 18.3.0 milestones allow us to target the issues.

  18. jbonofre commented on Feb 18, 2025

    @jbonofre
    Member

    The milestones have been updated.

    About pending tasks:

    1. Let me do the announce on dev@ / user@ / announce@
    2. I will prepare the blog post
    3. For the LinkedIn and BlueSky, I don't think I have the permission to do that. @kou @lidavidm can you please take this point ?

    Thanks !

  19. kou commented on Feb 19, 2025

    @kou
    MemberAuthor

    Thanks!

    @raulcd Could you announce 18.2.0 to LinkedIn and BlueSky when we publish a 18.2.0 announce blog post?

  20. raulcd commented on Feb 19, 2025

    @raulcd
    Member

    Sure, I can post. Ping me once the blog post is merged in case I miss it.

  21. jbonofre commented on Feb 19, 2025

    @jbonofre
    Member

    @raulcd great ! I'm working on it. I will let you know when ready to review.

  22. jbonofre commented on Feb 19, 2025

    @jbonofre
    Member

    @kou @raulcd @lidavidm here's the blog post about Arrow Java 18.2.0: apache/arrow-site#594

    As soon as it's merged/published, I will do the annouces.

  23. kou commented on Feb 20, 2025

    @kou
    MemberAuthor

    Thanks!

    I've merged it.

  24. jbonofre commented on Feb 20, 2025

    @jbonofre
    Member

    @kou awesome ! Thanks ! I'm doing the announce right now.

  25. jbonofre commented on Feb 20, 2025

    @jbonofre
    Member

    announce sent to dev@, user@ and announce@

  26. kou commented on Feb 20, 2025

    @kou
    MemberAuthor

    Thanks!

    @raulcd Could you announce to LinkedIn and BlueSky?

    FYI: https://arrow.apache.org/blog/2025/02/19/arrow-java-18.2.0/ is the blog post.

  27. raulcd commented on Feb 21, 2025

    @raulcd
    Member
  28. jbonofre commented on Feb 21, 2025

    @jbonofre
    Member

    @raulcd awesome ! Thanks

    I guess we can close this issue now.

  29. lidavidm commented on Feb 21, 2025

    @lidavidm
    Member

    Thanks all!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions