|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I think this is simple:
1) This release should be pulled.
2) Some kind of automated test (if only there was some kind of software package that could run integration tests after a software build, on a continuous basis) should be in place to load the nightly builds on each major OS and if they fail, then take action (back out submit, flag for review and don't release to public, any number of potential actions here)
3) Regarding a warning on the front page.. I disagree. Not because I feel that the people suggesting this are wrong, but it promotes bad behavior/poor code. The Jenkins community responsible for the stability of the product should take steps to reduce the possibility of a bugs like this making it to release-phase, instead of saying "meh, these things happen!".