[Epo-ec-advisors] Some thoughts on areas to address in the EC

[jesse]

> > Designing for deprecation and evolution is very important.  What's the
> > plan for releasing new versions of the extended core _without_ things
> > that were previously there?
> 
> I haven't worked out a formalized one yet except a rough idea of
> deprecation cycles and regular releases. I think a policy of deprecate
> for N release and then removal is the workable rough idea in my head.
> Better suggestions?

What comes to mind is something like this:

- Deprecations (or really, "Extended Core Best Practices") are calendar based, not release-count based.
- EPO::Core (or whatever it's actually called) would depend on
  EPO::Core::$CurrentYear (say EPO::Core::2009).
- Nothing in EPO::Core::2009 would ever be removed from future releases
  of EPO::Core::2009, though EPO::Core::2010 might finally remove Moose 
  and replace it with Goose or something.
- The recommended deployment practice would be to depend on a specific
  model-year of EPO::Core::, thus ensuring that if you tried to redeploy
  your system after the hardware smokes 36 months down the line, you
  don't get screwed.

How on crack am I?