Hi,
Currently we are operating this way:
1) Bug fixes only in supported stable branches.
2) New features in trunk.
There are several problems with this approach:
1) Development of RT and NIL is slow because both are complete and bugs rarely happen.
2) HAL is flooded for requests on new features and bug fixes happen all time because its nature. I find myself answering like "good idea but it will have to wait", not good.
Starting from next big release (march likely) there will be a change:
1) The current approach will continue for RT and NIL, new features only in major releases. Not a big deal, both are very complete.
2) HAL will follow a rolling releases flow, new features will go live as soon ready in trunk. This means that stable releases will get all new HAL features unless there is something incompatible with RTOSes (very unlikely).
This will benefit everybody, including commercial users because currently they are stuck with old HALs unless they back-port the new features by themselves. All users on 16.1 will be upgraded to 17.3 for free.
Giovanni
[INFO] Change of Release Strategy
- Giovanni
- Site Admin
- Posts: 14455
- Joined: Wed May 27, 2009 8:48 am
- Location: Salerno, Italy
- Has thanked: 1076 times
- Been thanked: 922 times
- Contact:
Return to “Development and Feedback”
Who is online
Users browsing this forum: No registered users and 28 guests