Wow - Jim agrees :) The creation of an automated cron job is a very good idea for making the "Build of the Day" to be proffered to the test pool and guinea pigs for evaluation. Each BOD would follow a common, documented naming convention with the version serialization or timestamp embedded in the filename proper and any perceived bugs logged against that particular revision. My previous comments regarding top-level web availability and click acknowledgement of possible peril still apply.
The cron job purge/fetch/build/link/pack/post idea allows users at all levels of software/environment/development/tools proficiency (and awareness) to evaluate flex builds. As a community, we must remember that there are participants - or potential participants - whom know very little about software, development environments, tools, etc. but are world-class operators, RF experts, user interface designers, human factors folks, etc. Just because they, through their youth, profession, experience, desire, etc. have not been baptized into the "dark side" <for us former hardware types> should not mean that we exclude their participation, losing the wealth of knowledge and experience they bring from adding to the improvement and enhancement of this fine activity. Think of it as flex's ADA compliance for the software disabled. My $0.02 Lee Pedlow NG6B San Diego, CA -----Original Message----- From: Jim Lux [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 18, 2006 8:10 PM To: Pedlow, Lee; flexradio@flex-radio.biz Subject: Re: [Flexradio] Am I Missing Something? Or Is Everyone? At 11:10 AM 4/18/2006, Pedlow, Lee wrote: >I >As indicated, Flex is facing the growing pains that every start-up goes >through. Many software activities begin as grass roots efforts and as >they become viable businesses, advancement of the business requires the >evolution of processes and practices. I think the suggestions made >above resonate with both Gerald's desires and Jim's very valid comments (be nice Jim). >Flame away. > > >Lee Pedlow NG6B >San Diego, CA I agree with you Lee.. The question I would have is who does the compile for the SVN .. Right now, you could check in a source code module without necessarily doing a build, bumping the SVN number. Might be nice to have the build in a standard environment? Maybe an automated "daily build" (as advocated by many software engineering pundits) run by a "cron job" (actually schedule service in the windows world, unless you've installed SFU) at a reference site might be useful? The cron would pick up the latest revision at 0700Z or something, run a batch compile, and plonk the resulting exe (if any) out there. Or, (gods forbid in the Windows world) a make file with a script to run it that gets zapped into SVN too. A script is available that a) updates your local copy b) fires off the make The Visual Studio world DOES have some way to do automated builds (MS uses it internally, for instance), but I haven't figured it out yet. I haven't spent much time hunting it down, though. Lots of ways to go, and over the next few weeks/months, I figure we'll converge on something. Jim
