[email protected] ([email protected]) wrote: > Thomas, > I have received word from our development teams. Here is the view our > leadership team asserted that we need to address to ensure that we can > quickly respond and support deployments in the field. > We should not be taking chances with our code trees unless
It's trivially easy to make this a zero-risk operation. Simply take a full git clone of the repositories as they stand and put it somewhere safe (either via a standard backup or by taking at least 2 copies). (Even *without* doing that, in my eyes this is already very close to zero-risk since it's also trivially easy to reconstruct a branch from a tag.) > 1) There is a significant benefit to doing this Yes there is, and it has already been explained. > 2) We understand exactly what is going to occur Thomas provided all the details 9 days ago. > and what it's repercussions are Zero repercussions: > 3) It is tested and validated that we are capable of recreating our > releases. See above. If you take a mirror of the current state, then you are guaranteed to be no worse off than you are right now. (Can you even guarantee right now that you are capable of recreating *all* your old releases? I think this is highly unlikely unless you regularly test *all* of them, due to the lack of proper branching in the top-level repo.) > Outside of clearing up community confusion, I see no significant > benefit to doing this. That is significant benefit in itself. Why do you need any other reason to accept a zero-risk change? The biggest reason that Crowbar has failed to attract a wider community so far is that there has been great resistance to prioritizing simple clean up of things which cause community confusion. That applies in all areas: code, documentation, website, wiki pages, tests, issue tracking ... > And even though we know what is going to occur and it's > repercussion, we don't have time to invest in testing and validating > that we can quickly recreate our releases. See above - investing that time is completely unnecessary. _______________________________________________ Crowbar mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
