I wasn't suggesting that a new format be adopted before next week's build. We're all capable of writing a COMMANDS file with the present file format to help the next build go smoothly.

But well before the COMMANDS file goes "beyond just defining the set of commands" it would be good to change to a standard format. It might be useful having some sort of outlet (maybe an RFC, if you wanna get all formal) for discussing and planning these kinds of standards with a set of the KBase developers before valuable effort is pored into coding up handlers. Usually, we're notified on this list of conventions after the format is decided and its software written. Maybe fodder for discussion at next month's all-hands meeting.

Shiran

On Mar 21, 2013, at 4:48 PM, brettint@gmail.com wrote:

Also. While the suggestion here are fine,  a change request usually lists all the code affected.  a change might seem trivial to someone not familiar with the code base.  And then someone needs to make the changes on the affected code. And it has to be fit into a schedule. And the value of the change needs to be weighed against the cost. Both the cost of making the change and the cost of not doing something else.

For the release on monday we need the COMMANDS file in the specified format  

I already anticipate a more structured format will be necessary.

Thanks all.
Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: brettint@gmail.com
Date: Thu, 21 Mar 2013 20:34:30
To: Travis Harrison<teharrison@anl.gov>; <kbase-devel-bounces@lists.kbase.us>; Thomas Brettin<brettin@mcs.anl.gov>
Reply-To: brettint@gmail.com
Cc: Kbase Devel<kbase-devel@lists.kbase.us>; release-team@lists.kbase.us<release-team@lists.kbase.us>
Subject: Re: [Kbase-devel] COMMANDS File and Minor Release Next Week

All. Answers toi come in due time. I'm leaving town on family vacation. For now just create the file according to the existing format. We can evolve. We have existing code that will evolve.
Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: Travis Harrison <teharrison@anl.gov>
Sender: kbase-devel-bounces@lists.kbase.usDate: Thu, 21 Mar 2013 14:52:11
To: Thomas Brettin<brettin@mcs.anl.gov>
Cc: kbase-devel@lists.kbase.us devel<kbase-devel@lists.kbase.us>; release-team@lists.kbase.us<release-team@lists.kbase.us>
Subject: Re: [Kbase-devel] COMMANDS File and Minor Release Next Week

_______________________________________________
Kbase-devel mailing list
Kbase-devel@lists.kbase.us
https://lists.kbase.us/mailman/listinfo/kbase-devel

_______________________________________________
Kbase-devel mailing list
Kbase-devel@lists.kbase.us
https://lists.kbase.us/mailman/listinfo/kbase-devel