cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Hunsberger <>
Subject Re: Fwd: Cocoon-trunk - Build # 49 - Unstable
Date Thu, 11 Aug 2011 12:17:17 GMT
> AFAIK, there should be no issue in making profiling results volatile, but I am really
not familiar with profiling internals: who knows better?

One could argue that the profiling should match up against the regular
release just so that we know the results correspond.  As long as
everyone know what is going on I don't see a big issue leaving it the
way it is, but that means documenting it in an obvious way some how.
Any ideas?

View raw message