Create an Update Policy about scotch-box HOT 5 CLOSED

Thanks for posting this here vs Twitter - very thorough. I'll create an update policy.

The beauty of this is anyone using Puppet or Chef via Vagrant can add or provision updates whenever necessary without worrying about the base box. I should have an update policy for the base box though since that kills off the point of simplicity.

What do you recommend for schedule / timeline?

from scotch-box.

I don't know what kind of schedule it should have. I don't want maintaining the project to be onerous for your or anyone, nor us users; the more demanding the schedule, the more likely maintenance will slip, for both the image makers and the image users.

In contrast, Laravel Homestead is only 11 months old (April 16 2014) and has updated 15 times, updating dependancies and packages numerous times, including moving to PHP 5.6, MySQL 5.6, Postgres 9.4 and HHVM.
https://vagrantcloud.com/laravel/boxes/homestead

(2¢) Every three months feels like a sweet spot for keeping it up to date, but it could be less frequent, but I feel no more than 6 months should pass between updates.

from scotch-box.

Not as detailed as you'd probably like, but https://scotch.io/bar-talk/announcing-scotch-box-2-5#update-policy-and-the-future-of-scotch-box

Also, we'll eventually phase out in favor of Otto

from scotch-box.

This is actually great. Nice work by the way!

from scotch-box.

So now that Otto is gone and last Scotch update is 12 months old... are there any plans?

from scotch-box.