I've implemented named parameters (per my proposal), done some light testing, and would like to make it available to others for some more testing.
How do I commit it? Should I commit it to HEAD or should I create a new branch? My personal opinion is that it should NOT be placed in HEAD unless there is a reasonable expectation that it will be included in a future release. That requires an action by the BOARD to approval part or all of my proposed changes. On the other hand, I'd like to get this into the system ASAP to avoid the types of problems I had when Keith Rumley and I were both making changes to the same base. I had to go back and rework, rehash, and retest my oword code; which was not fun. So... 1 -- Where should I commit it? 2 -- How do I do that? (I don't think I'm authorized to do that.) And I don't know how. (In the past, Alex Joni has walked me through the process.) 3 -- When should I do that? Next on the list is named owords. I'd like to do this as a separate step, though. After that, I think I'll try implementing comments that are logged and have embedded parameters. Then maybe integrator defined canned cycles. -- I think this one is pretty easy. Ken [EMAIL PROTECTED] Mark Kenny Products Company, LLC 55 Main Street Voice: (203)426-7166 Newtown, CT 06470 Fax: (203)426-9138 http://www.MarkKenny.com ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
