|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-14273) Matrix jobs... [email protected] (JIRA)
- [JIRA] (JENKINS-14273) Matrix jobs... [email protected] (JIRA)
- [JIRA] (JENKINS-14273) Matrix jobs... [email protected] (JIRA)
- [JIRA] (JENKINS-14273) Matrix jobs... [email protected] (JIRA)
- [JIRA] (JENKINS-14273) Matrix jobs... [email protected] (JIRA)
- [JIRA] (JENKINS-14273) Matrix jobs... [email protected] (JIRA)
- [JIRA] (JENKINS-14273) Matrix jobs... [email protected] (JIRA)
- [JIRA] (JENKINS-14273) Matrix jobs... [email protected] (JIRA)
- [JIRA] (JENKINS-14273) Matrix jobs... [email protected] (JIRA)
- [JIRA] (JENKINS-14273) Matrix jobs... [email protected] (JIRA)
- [JIRA] (JENKINS-14273) Matrix jobs... [email protected] (JIRA)
- [JIRA] (JENKINS-14273) Matrix jobs... [email protected] (JIRA)
- [JIRA] (JENKINS-14273) Matrix jobs... [email protected] (JIRA)

I don't follow the ins and outs of the release process that closely but basically v1.474 had already been built by the time that this issue was reported/fixed.
The weekly builds are basically just snapshots of the current state of the tree at the time of the build. They allow the latest changes to get to a wider audience and to catch bugs like this before they get into a long-term release. There is always scope for better unit/integration testing and help is appreciated.
If you need a known/stable build then I would suggest that you switch to the LTS release that is updated every 3 months or so after more extensive testing.