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

Release Fortress #459

Closed
chapulina opened this issue May 11, 2021 · 5 comments
Closed

Release Fortress #459

chapulina opened this issue May 11, 2021 · 5 comments
Labels
🆕 collection-release-tracker Tag for collection releasing issues. Usually meta trackers

Comments

@chapulina
Copy link
Contributor

chapulina commented May 11, 2021

Timeline

Current tentative timeline

  • Feature freeze: 2021/09/07 (Tuesday)
  • Code freeze: 2021/09/21 (Tuesday)
  • Tutorial party: 2021/09/22 - 2021/09/29
  • Community meeting: 2021/09/29 (Wednesday)
  • Release: 2021/09/30 (Thursday)

During development

Feature freeze

Code freeze

Release day

Post-release

If the collection will be officially paired with a ROS 2 distro:

Status tracker

Repo Version Release Branch Feature frozen Synced with C,D&E? Prerelease? Code Frozen Stable release? Open PRs Pending dep release
ign-tools 1 ign-tools1 ✔️ ✔️ ✔️ ✔️ ✔️ PRs -
ign-cmake 2 ign-cmake2 ✔️ ✔️ ✔️ ✔️ ✔️ PRs -
ign-math 6 ign-math6 ✔️ ✔️ ✔️ ✔️ ✔️ PRs -
ign-plugin 1 ign-plugin1 ✔️ ✔️ ✔️ ✔️ ✔️ PRs -
ign-utils 1 ign-utils1 ✔️ ✔️ ✔️ ✔️ ✔️ PRs -
ign-common 4 ign-common4 ✔️ ✔️ ✔️ ✔️ ✔️ PRs -
ign-msgs 8 ign-msgs8 ✔️ ✔️ ✔️ ✔️ ✔️ PRs -
ign-rendering 6 ign-rendering6 ✔️ ✔️ ✔️ ✔️ ✔️ PRs -
sdformat 12 sdf12 ✔️ ✔️ ✔️ ✔️ ✔️ PRs -
ign-fuel-tools 7 ign-fuel-tools7 ✔️ ✔️ ✔️ ✔️ ✔️ PRs ign-msgs
ign-transport 11 ign-transport11 ✔️ ✔️ ✔️ ✔️ ✔️ PRs ign-msgs
ign-gui 6 ign-gui6 ✔️ ✔️ ✔️ ✔️ ✔️ PRs ign-transport, ign-rendering
ign-sensors 6 ign-sensors6 ✔️ ✔️ ✔️ ✔️ ✔️ PRs ign-transport, ign-rendering
ign-physics 5 ign-physics5 ✔️ ✔️ ✔️ ✔️ ✔️ PRs sdformat
ign-gazebo 6 ign-gazebo6 ✔️ ✔️ ✔️ ✔️ ✔️ PRs ign-physics, ign-gui, ign-sensors
ign-launch 5 ign-launch5 ✔️ ✔️ ✔️ ✔️ ✔️ PRs ign-gazebo
ign-fortress 1 main ✔️ ✔️ ✔️ ✔️ ✔️ PRs ign-launch
ros_ign noetic / rolling noetic / ros2 ✔️ ✔️ ✔️ PRs ign-fortress

Track stable release of metapackage ignition-fortress.

  • ⌛ TODO
  • 🟡 waiting in the buildfarm
  • 🟢 in the repo
  • 🔴 requires action
  • ⚫ no release

Linux

  • Ubuntu:

    • 🟢 Bionic/amd64
    • 🟢 Bionic/i386
    • 🟢 Bionic/armhf
    • 🟢 Bionic/arm64
    • 🟢 Focal/amd64
    • 🟢 Focal/arm64
    • 🟢 Focal/armhf
  • Debian: (no DART in physics)

    • 🟢 Buster/i386
    • 🟢 Buster/amd64
    • 🟢 Buster/arm64
    • 🟢 Buster/armhf (raspbian)
    • ⚫ Sid/*: (since we are working downstream my plan is to release only the remaining pieces)

MacOSX

  • Brew
    • 🟢 Bottles

Windows

@chapulina chapulina added this to Inbox in Infrastructure via automation May 11, 2021
@chapulina chapulina moved this from Inbox to In progress in Infrastructure May 11, 2021
Infrastructure automation moved this from In progress to Done Aug 16, 2021
@chapulina chapulina reopened this Aug 16, 2021
@chapulina chapulina moved this from Done to In progress in Infrastructure Aug 31, 2021
@traversaro
Copy link

traversaro commented Oct 2, 2021

Windows

conda-forge

(WIP Table, will be updated with more rows as more Fortress packages are released, @chapulina let me know if you like this format or we can do a separate issue or something else). Contains several PRs that are merged by @Tobias-Fischer or @wolfv .

Repo Related PRs Fortress-related release available in conda-forge
ign-tools conda-forge/libignition-tools-feedstock#10 🟢
ign-cmake None, as there was no ign-cmake release related to Fortress (perhaps the closest candidate is conda-forge/libignition-cmake0-feedstock#18 ?) 🟢
ign-math conda-forge/libignition-math4-feedstock#18, conda-forge/libignition-math4-feedstock#19, conda-forge/libignition-math4-feedstock#21 🟢
ign-plugin conda-forge/libignition-plugin-feedstock#14 🟢
ign-utils conda-forge/libignition-utils-feedstock#6 🟢
ign-common conda-forge/libignition-common-feedstock#41 🟢
ign-msgs conda-forge/libignition-msgs1-feedstock#58 🟢
ign-rendering conda-forge/libignition-rendering4-feedstock#19, conda-forge/libignition-rendering4-feedstock#20, conda-forge/libignition-rendering4-feedstock#24 🟢
sdformat conda-forge/libsdformat-feedstock#49 🟢
ign-fuel-tools conda-forge/libignition-fuel-tools-feedstock#48 🟢
ign-transport conda-forge/libignition-transport4-feedstock#47 🟢
ign-gui conda-forge/libignition-gui-feedstock#14 🟢
ign-sensors conda-forge/libignition-sensors-feedstock#16, conda-forge/libignition-sensors-feedstock#17 🟢
ign-physics conda-forge/libignition-physics-feedstock#21 🟢
ign-gazebo conda-forge/libignition-gazebo-feedstock#24, conda-forge/libignition-gazebo-feedstock#25 🟢
ign-launch conda-forge/libignition-launch-feedstock#7, conda-forge/libignition-launch-feedstock#8 🟢

For what regards ign-fortress, we do not have meta packages for ignition releases in conda-forge (even if it would be possible to have them if anyone is interested, see conda-forge/staged-recipes#13551 (comment)). For what regards ros_ign , we should probably deal with this on RoboStack repos, but it does not make sense to do so until we have libign-gazebo6 properly released on conda-forge .

@chapulina
Copy link
Contributor Author

Thanks for all the work on Windows, @traversaro , that format looks good to me.

Probably not just related to Fortress, but I did notice some feedstocks have version numbers that don't match the major versions in Fortress (msgs1, rendering4, transport4...). Let me know what would be a better place to talk about this.

@traversaro
Copy link

traversaro commented Oct 5, 2021

Probably not just related to Fortress, but I did notice some feedstocks have version numbers that don't match the major versions in Fortress (msgs1, rendering4, transport4...). Let me know what would be a better place to talk about this.

That is just the name of the repositories, that we only understood how to create with the name that we wanted only later in the process of packaging (see conda-forge/staged-recipes#13551). However, the name of the repo has no influence on the name of the created packages, so both https://github.com/conda-forge/libignition-transport4-feedstock and https://github.com/conda-forge/libignition-gazebo-feedstock (for example) create packages with the name libignition-<library-name><major-version> that can be side-by-side installable as in apt or homebrew. For example https://github.com/conda-forge/libignition-transport4-feedstock creates libignition-transport8, libignition-transport9 and libignition-transport10 (thanks to its branches: https://github.com/conda-forge/libignition-transport4-feedstock/blob/412f8cfbbfef0d9a075e4edf7534b2cc084a421f/conda-forge.yml#L2) and will create libignition-transport11 once conda-forge/libignition-transport4-feedstock#47 is merged.

We never looked in understand if there is a way to rename the repos as that is mostly a cosmetic issue, and we do not know if a repo name change would create problems in the conda-forge bot infrastructure, that is quite complex to handle things like ABI migrations (see https://conda-forge.org/blog/posts/2019-12-06-cfep09/).

@traversaro
Copy link

@chapulina All the Fortress ignition packages now have binaries on conda-forge. We still have some issues (see conda-forge/libignition-gazebo-feedstock#27, conda-forge/libignition-gazebo-feedstock#6) and ign gazebo starts correctly only on Linux (mainly due to gazebosim/gz-tools#7 and other issues), but the basic library functionality is there.

@chapulina
Copy link
Contributor Author

That's awesome, @traversaro ! Thanks for all the work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🆕 collection-release-tracker Tag for collection releasing issues. Usually meta trackers
Projects
None yet
Development

No branches or pull requests

3 participants