Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

Versioning third party package by snapshot date

asked 2014-09-03 14:47:20 -0500

vooon

404 ●6 ●9 ●15

I maintain release of mavlink package ros.

Upstream developers stopped making releases, it is recommended to use the latest snapshot. So that the original version is stuck at 1.0.9. When I release the update, the release number of the package rises, but it hard to track between ros releases (also it confuse users).

I think it is more convenient to use instead of the original version of the snapshot date in the form of YEAR.MONTH.DAY. But i don't find any related information about releasing snapshots.

edit retag flag offensive close merge delete

add a comment

1 Answer

Sort by » oldest newest most voted

answered 2014-09-03 15:09:48 -0500

Dirk Thomas
16276 ●62 ●190 ●215

Since year.month.day also represents a version number consisting of three parts it is absolutely ok to use that. Important is the order of version number but that is guaranteed with the scheme you posted (obviously day.month.year would be bad).

There are already packages using a similar name, e.g.: http://www.ros.org/debbuild/indigo.ht...

edit flag offensive delete link

add a comment

Question Tools

Stats

Asked: 2014-09-03 14:47:20 -0500

Seen: 286 times

Last updated: Sep 03 '14

Versioning third party package by snapshot date edit

1 Answer

Question Tools

Stats

Related questions

Versioning third party package by snapshot date