Future of the application cookbook


#1

Hi all,

I was wondering what’s happening with this cookbook and what is the
plan going forward.

As you probably know the application cookbook is, uhm, problematic;
there are a number of issues open, some of them opened recently.

coderanger has done some very interesting work, that is a pretty big
departure from the current way but is IMHO a very good way of handling
this.
There is also my fork and pull request that strives to be backward
compatible while still fixing the biggest problems.

So, what’s the plan?
Anything holding up integration of coderanger’s work? Any worry about
backward compat?
Would it make sense to add coderanger’s cookbook with a new name, and
provide a deprecation and migration path, to avoid having a flag day?

Andrea


#2

Finalizing the application cookbook from coderanges remains a prioritized
planned activity, and is in the product backlog queue to be included in an
upcoming sprint - it didn’t get assigned out in the current sprint due to
the holidays, the reduced availability of people, and the size of the
undertaking.

I’d expect that it will be included in one of the next couple of sprints,
from which additional pull requests, backlog compatibility, etc. would be
considered - discussed as appropriate - with the result incorporated.

  • Tom

On Thu, Dec 29, 2011 at 2:56 PM, Andrea Campi
andrea.campi@zephirworks.comwrote:

Hi all,

I was wondering what’s happening with this cookbook and what is the
plan going forward.

As you probably know the application cookbook is, uhm, problematic;
there are a number of issues open, some of them opened recently.

coderanger has done some very interesting work, that is a pretty big
departure from the current way but is IMHO a very good way of handling
this.
There is also my fork and pull request that strives to be backward
compatible while still fixing the biggest problems.

So, what’s the plan?
Anything holding up integration of coderanger’s work? Any worry about
backward compat?
Would it make sense to add coderanger’s cookbook with a new name, and
provide a deprecation and migration path, to avoid having a flag day?

Andrea


#3

Andrea,

Can you provide a link to coderanger’s application cookbook? I don’t
see it on his github page

The current application cookbook doesn’t meet my needs for tomcat and
jboss applications. I want to review all the different approaches that
currently exist before I reinvent the wheel. I am particularly
fascinated by joewilliams app cookbook.

On Thu, Dec 29, 2011 at 11:56 PM, Andrea Campi
andrea.campi@zephirworks.com wrote:

Hi all,

I was wondering what’s happening with this cookbook and what is the
plan going forward.

As you probably know the application cookbook is, uhm, problematic;
there are a number of issues open, some of them opened recently.

coderanger has done some very interesting work, that is a pretty big
departure from the current way but is IMHO a very good way of handling
this.
There is also my fork and pull request that strives to be backward
compatible while still fixing the biggest problems.

So, what’s the plan?
Anything holding up integration of coderanger’s work? Any worry about
backward compat?
Would it make sense to add coderanger’s cookbook with a new name, and
provide a deprecation and migration path, to avoid having a flag day?

Andrea