Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

10
  • 6
    @gnat I am not dragging anyone into a discussion - I am after a specific and clear definition of a "train" development process/methodology. Commented Mar 15, 2014 at 6:17
  • 1
    I found tons of useful information here: google.com/search?q=train-based+software+development Commented Mar 15, 2014 at 8:46
  • 1
    @RobertHarvey Thanks, although I have to say that there is very little information in that search results. The closest that one can dig out when separates the train from the wagons is that "train" is about making releases at regular intervals according to a schedule. It seems contentious that this maps well to the quote of "pulling Firefox of the trains". It seems that "train" is a sort of concrete QA setup. Commented Mar 15, 2014 at 8:55
  • 1
    Related meta question: meta.programmers.stackexchange.com/q/6551/53019 Commented Mar 20, 2014 at 14:48
  • 2
    Isn't this how Ruby on Rails was developed? Commented Mar 25, 2014 at 18:54