|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
@Shannon, as you mentioned, your experience using "weekly builds" may have made you wary of using them. My experience on the other hand is slightly different in that the company I'm currently a part of does an agile weekly production release cycle of their cloud-based Software as a Service product. As a DevOps and Release Engineer, I am part of that process and we make sure to the extent possible that our weekly releases are stable. We have large companies using/hosted on our platform and our releases need to happen live without causing any noticeable downtime to our clients. So I am skewed towards the other end of the spectrum whereby I would generally trust a weekly release unless, as you mentioned, there is a "more visible warning". Nevertheless, I agree with you that if you want a stable and tested environment, go with the LTS release. I also agree with you that in general, the latest and greatest are not always the greatest. In fact, they'd probably be buggy and crash =)