Push Blueprint Content?

That's one possible way it'll work. You'll be able to specify the exact functionality you want, probably on a few different levels. I imagine that I'll make it work so that you can set up the default behavior, then also specify changes to those defaults whenever a new release is created. Here's basically the set of things you'll decide on when making new releases & pushing content: whether or not group admins get a choice on how/if they update (and that's granulated further by groups which have changed something and groups which haven't); how conflicts, if any, are handled between current versions & new releases; if you're operating in bundle-per-type mode, whether different default behaviors should be created for each group type (or just use the 'master' default). That sorta thing.

I am just loving this module so far. Just one question, when do you plan to implement the "Push" portion of this module?

I am already finding a need to update existing groups with new functionality and I am cringing at the thought of having to edit every single group one at a time.

Also let me know if there is some way I can help.

thx,
Katrina

--
www.ambereyes.net

Any plans in the works for this functionality?

It's a major feature requiring significant planning and commitment on my part to implement. My other commitments really mean that the best I can manage is an "I'll get to it when I get to it" which probably means months. May/June-ish, at the earliest.