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

ROS Buildfarm Release "Noetic and Foxy" #521

Open
4 of 12 tasks
Levi-Armstrong opened this issue Jan 11, 2021 · 11 comments
Open
4 of 12 tasks

ROS Buildfarm Release "Noetic and Foxy" #521

Levi-Armstrong opened this issue Jan 11, 2021 · 11 comments

Comments

@Levi-Armstrong
Copy link
Contributor

Levi-Armstrong commented Jan 11, 2021

Noetic:

  • ros_industrial_cmake_boilerplate
  • opw_kinematics
  • osqp
  • osqp_eigen
  • qpOASES
  • tesseract

Foxy

  • ros_industrial_cmake_boilerplate
  • opw_kinematics
  • osqp
  • osqp_eigen
  • qpOASES
  • tesseract
@Levi-Armstrong Levi-Armstrong changed the title ROS Buildfarm Release "Noetic" ROS Buildfarm Release "Noetic and Foxy" Jan 11, 2021
@Levi-Armstrong
Copy link
Contributor Author

@mpowelson, @marip8 and @johnwason I believe this repository is ready to be released. Any objections to me releasing this repository for Noetic with tag 1.0.0?

@johnwason
Copy link
Contributor

I am going to try a conda build tonight, let's make sure it will work there.

@johnwason
Copy link
Contributor

No, it isn't building using conda on windows. I can't look into this until the week after next most likely. We can add patches later to the conda package if needed, or wait until the conda build is working.

@marip8
Copy link
Contributor

marip8 commented Apr 8, 2021

I'm on board for the release. As far as I can tell it looks like the major discussions about de-coupling the planning/visualization code have been addressed and there aren't any outstanding PRs with major changes.

What is your tagging strategy? Are the 0.x.x tags supposed to represent pre-release states and 1+.x.x represent post-release states? Just wondering if the next tag should be 0.3.0 since there really hasn't been a "major" change since the last tag

@gavanderhoorn
Copy link

What is your tagging strategy? Are the 0.x.x tags supposed to represent pre-release states and 1+.x.x represent post-release states? Just wondering if the next tag should be 0.3.0 since there really hasn't been a "major" change since the last tag

Going to 1.x immediately may indeed not be what you'd want.

If you're going to use semver, seeing a 1.x release implies quite a few things.

@mpowelson
Copy link
Contributor

I think I agree that a 0.x release might be a better option right now. Then if that goes well we can plan on a 1.0 release sometime soon.

@Levi-Armstrong
Copy link
Contributor Author

Levi-Armstrong commented Apr 8, 2021

@gavanderhoorn, @mpowelson, @marip8 and @johnwason Thank you all for the input. I will begin the release process and use tag 0.4.0.

@Levi-Armstrong
Copy link
Contributor Author

Just submitted the release on the ROS buildfarm.

@Levi-Armstrong
Copy link
Contributor Author

@johnwason Everything has been upgraded to taskflow v3.0.0.

@johnwason
Copy link
Contributor

@Levi-Armstrong ok I'll give the conda build another try

@Levi-Armstrong
Copy link
Contributor Author

The release status can be tacked here.

@marip8 marip8 mentioned this issue Jun 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants