As of Wagn 1.6, developers can extend Wagn without forking its code by creating a "pack".
"Packs" are ways to extend Wagn's functionality. In the long term, we envision that a "pack" may refer to several things:
- "modularized" code that can easily be added or subtracted
- a "tradeable" group of configuration cards
- a combination of the above
√- 1. knock off the biggest hoptoad errors
√ 2. the mime type instantiation warnings
√ 3. Slavic's various windows/sqlite patches
Unlike most releases, 1.5.4 will basically be defunct until we run migrations. So we will need to handle downtime, including:
1. a static web message
2. preparing clients for downtime
--Ethan McCutchen.....Wed Apr 27 10:44:55 -0700 2011
I may have a way to do this without downtime. but I do have a way to put up a maintenance message now.
--Ethan McCutchen.....Fri May 06 20:02:47 -0700 2011
Unless there is urgency about some of the migrations above, I think I'm going to punt for now and avoid adding any extra complexity to this release. Can do in a point release soon.
--Ethan McCutchen.....Fri May 06 20:16:51 -0700 2011