Daniel Fagerstrom wrote:
Bertrand Delacretaz wrote:
We talked about that this morning with Jeremy at the GT: how about
creating a "contrib" directory in our repository, for stuff that we
want to stay available, without being directly tied to our releases.
This could contain:
-example apps like bricks-cms
-blocks that we'd like to remove from 2.2 yet keep around, but without
any guarantees
-useful tools: raccoon, etc.
-more?
Decoupling this stuff from releases would make it easier to release
more often, and draw a better line between critical, fully supported
stuff and more experimental or legacy stuff.
WDYT?
-Bertrand
+1
Exactly what a contrib dir might evolve into, I don't know, but I do
want there to be _something_ that can evolve!
Regards, Upayavira
