Versioning for every module (assembly, jar, dll, exe, binaries in general, excluding executables as web-applications, services and web-services) can be even further simplified
when
the software development team that develop the module is the same team that use the module in their applications
or
at least the two team can agree on a common release date for the application and the module. In pracatice when both teams has synchronized time-boxed sprints and releases.
In this case for the modules there is no need to have an explicit beta=>release-candidate=>official cycle, the last source code for the code can be used instead.
So also there is no need to manual handling of version number (an automatically assigned unique number is enough) nor for release notes of the module.
Tags :
Team Work |
Agile |
Complessità |
Pratiche |
Progettazione Software |