Plan for makara deprecation about makara HOT 6 CLOSED

Hm. Or make it a wrapping project, usable as-is: re-export child module bits and bobs.

from makara.

I'm not really clear on what pre-makara and post-makara looks like, i.e. what exactly is the deprecation? I assume it means for people to move away from makara entirely? Or they need to re-integrate makara into their project to account for breaking changes etc? Sorry, I probably should know.

from makara.

No, that's the thing, it's undefined.

Right now, the last change took localizr and used it to implement the exact interface makara has always used, by re-exporting its functions. I could see doing similar for the rest of it -- engine-munger being perhaps the next target.

from makara.

Deprecation? What deprecation? krakenjs.com references Makara. Could someone please provide a clear explanation of how new projects based on Kraken should be implementing localization?

from makara.

kraken 1.0 projects use localizr, engine-munger, adaro, bundalo and grunt-localizr. They were extracted from makara for the 1.0 release. Use those, with dust < 2.7

I'm working on new components -- a simplified engine-munger, reworked adaro to work with dust 2.7 -- they will be bundled into a kraken-friendly configuration as a new release of makara

from makara.

Makara 2.0.0 has been released!

from makara.