( I apologize for being stuck with a lotus notes client).
Dave's response triggered an indirect point as pertains to the vision
statement:
"IT managers should have confidence in hiring enterprise architects who
specialize in Perl, in supporting enterprise development projects in Perl,
and in deploying enterprise applications in Perl."
For many stupid reasons Perl has more barriers to adoption as a platform
than other languages in large Corporations such as the one I currently
work for. For what it's worth P5EE will have to go up and beyond normal
standards to overcome these barriers. Attention to even small things like
the interfaces and comments that an IT manager see's over the shoulder of
his architect/developer as he works or researches has an impact on the
above stated vision. P5EE won't be able to shower the media or the IT
manager with glossy pictorial's and grandiose promises. The look and feel
of the interfaces (shallow and silly as it may be ) is one of the few
places where P5EE will be able to help 'sell' itself when seen by Managers
or presented before 'review' boards for approval. The question of "And how
will you support this?" will definitely come up in a formal review and
displaying a professional interface to a changelog or a bug track log
could make a huge impression.
just my .02 to stick in the back of your collective mind
Jeff
aka Coreolyn
Dave Rolsky <[EMAIL PROTECTED]>
02/01/2002 11:53 AM
To: Stephen Adkins <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED]
Subject: Re: autogeneration of CHANGES file
On Fri, 1 Feb 2002, Stephen Adkins wrote:
> Unless there is a clear consensus on how to do this, I will
> probably modify my "cvshistory" script to create the
> "CHANGES" file. ("cvshistory" is the script which creates the
> CVS Activity page and is located in the P5EEx/Blue/sbin directory.)
>
> http://www.officevision.com/pub/p5ee/activity.html
I really hate seeing changelogs that are collections of CVS comments. You
end up with lots of stuff like:
Rewrote algorithm to detect smells
Tweaked some variable names
...
They tend to be way too low level to be of interest to non-core
developers, people who just use the stuff. When I look at a changelog for
a Perl module, I want to to see what will affect me. Faster, more
features, API changes, etc. And that's it. Take the time to write a
changelog by hand based on the CVS changes or something.
-dave
/*==================
www.urth.org
we await the New Sun
==================*/
