Replies: 5 comments
-
Hi @kt10aan Yours is a very good suggestion we are already trying to target with our brand new policies for the code workflow. These policies will be out soon, hopefully, including a proper way to make very clear what changes will break compatibility needing all developers to be very much aware of. Stay tuned. |
Beta Was this translation helpful? Give feedback.
-
@pattacini great news! |
Beta Was this translation helpful? Give feedback.
-
@kt10aan, if you want to have already a "sneaky" preview of what these policies will be about, take a look at these instructions. With regards to the list of new features and bug fixes published upon tagging the stable branch - comprising breakage of back-compatibility -, we are thinking of exploiting directly the way Github allows detailing software releases. |
Beta Was this translation helpful? Give feedback.
-
Closing for now. |
Beta Was this translation helpful? Give feedback.
-
These are the pages that list the changes introduced at each past and upcoming releases: iCub: http://wiki.icub.org/wiki/ChangeLog |
Beta Was this translation helpful? Give feedback.
-
I had talked about this a long time ago, maybe before the QA repo was started. But I think it is a good time to bring it up again.
The YARP/iCub software is continuously evolving and quite often changes break older stuff. It can be innocent renames in the API (like moving math functions from
iCub::ctrl
toyarp::math
), it can be renaming and/or moving of essential modulesiCubInterface
torobotInterface
toyarprobotinterface
, it can be a new format of config files etc.While I do keep up with all the posts in the QA/yarp/icub-main etc, many people do not or cannot, for various reasons. Also, despite keeping up with all the posts, I do find it difficult to remember when a breaking change was announced, and in which repository and go back to search for it.
I think it would be very nice if there was (for example) a wiki page that would list any incompatibilities or changes introduced (not for ones already happened but for future ones).
In my opinion, that would make the life of people outside IIT much much easier during upgrades and during updating older code.
At the same time, it will save support time, as quite a few of the support requests have to do with changes that have been introduced and the user was unaware of.
Beta Was this translation helpful? Give feedback.
All reactions