Software release train
![]() | This article includes a list of references, but its sources remain unclear because it has insufficient inline citations. (April 2019) (Learn how and when to remove this template message) |
![]() | It has been suggested that this article be merged into Software versioning. (Discuss) Proposed since April 2019. |
A software release train is a form of software release schedule in which a number of distinct series of versioned software releases for multiple products are released as a number of different "trains" on a regular schedule. Generally, for each product line, a number of different release trains are running at a given time, with each train moving from initial release to eventual maturity and retirement on a planned schedule. Users may experiment with a newer release train before adopting it for production, allowing them to experiment with newer, "raw", releases early, while continuing to follow the previous train's point releases for their production systems prior to moving to the new release train as it becomes mature.
Cisco's IOS software platform used a release train schedule with many distinct trains for many years. More recently, a number of other platforms including Firefox,[1] Eclipse,[2] LibreOffice,[3] Ubuntu[4] and VMware have adopted the release train model.
References[edit]
External links[edit]
![]() | This software-engineering-related article is a stub. You can help Wikipedia by expanding it. |