The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Isn't there a unified Changelog for those burst-releases?
No, unfortunately not.
It would also not be trivial to do that, as packages are (mostly) developed in relative isolation, so it would take additional effort to create such a unified changelog.
Coalescing changelogs could be done however by a job on the buildfarm fi, but that is currently not something that exists.
| | 2 | No.2 Revision |
Isn't there a unified Changelog for those burst-releases?
No, unfortunately not.
It would also not be trivial to do that, as packages are (mostly) developed in relative isolation, so it would take additional effort to create such a unified changelog.
Coalescing changelogs could be done however by a job on the buildfarm fi, but that is currently not something that exists.
Edit:
One can observe that they're released in "bursts", so a group of packages are released together.
just to clarify: the packages are only synced in aggregation, they are not released together. Package maintainers are free to release their packages at any time, but those newer versions will not appear in the public/main repository until they are moved from the staging repository to the public one.
See ShadowRepository for some background on this process.
| | 3 | No.3 Revision |
Isn't there a unified Changelog for those burst-releases?
No, unfortunately not.
It would also not be trivial to do that, as packages are (mostly) developed in relative isolation, so it would take additional effort to create such a unified changelog.
Coalescing changelogs could be done however by a job on the buildfarm fi, but that is currently not something that exists.
Edit:
One can observe that they're released in "bursts", so a group of packages are released together.
just to clarify: the packages are only synced in aggregation, they are not released together. Package maintainers are free to release their packages at any time, but those newer versions will not appear in the public/main repository until they are moved there from the staging repository to the public one.
See ShadowRepository for some background on this process.
| | 4 | No.4 Revision |
Isn't there a unified Changelog for those burst-releases?
No, unfortunately not.
It would also not be trivial to do that, as packages are (mostly) developed in relative isolation, so it would take additional effort to create such a unified changelog.
Coalescing changelogs could be done however by a job on the buildfarm fi, but that is currently not something that exists.
Edit:
One can observe that they're released in "bursts", so a group of packages are released together.
just to clarify: the packages are only synced in aggregation, they are not released together. Package maintainers are free to release their packages at any time, but those newer versions will not appear in the public/main repository until they are moved there from the staging one.
See ShadowRepository for some background on this process.
Edit2:
Of course, I could search github for each package, find out the package version (not to mix up with the release version!) and look into the changelog, but this seems very cumbersome.
just in case you didn't know: package wiki pages for released packages have a link to the changelog as well. That might be more efficient than trawling github repositories.
It's in the Package Links box on the right side of the page:
The one for roscpp is here fi.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
