agent-no-start with or without arg?

Michael Foley mfoley at redhat.com
Wed Jun 12 01:01:20 UTC 2013


Hi, 


I want to make sure QE stays properly engaged with changes like this .... so stuff gets tested, testcases added when appropriate, documentation gets added, etc... 

For significant changes ... RFEs and the like ... we are doing the "virtuous QE cycle ... developer demo, TCMS testcase review, TCMS testcase execution" ... but this seems like a small change ... too small for that approach. Still ... if changes are made without engaging QE or doc ... we could be missing something important. 

Couple of ideas: 


    * add a BZ ... and move it MODIFIED or ON_QA when ready 
    * add a card in the Trello Scrum board for Cassandra https://trello.com/board/cassandra-integration/5141e714c8c45ddf52002213 
    * other? 

I'd like a super low overhead process ... I'm not interested in anything heavyweight or that takes longer than 2 minutes .... 

Thoughts? 

Michael Foley 
QE Lead, JBoss Operations Network 


----- Original Message -----

From: "John Mazzitelli" <mazz at redhat.com> 
To: "rhq-devel" <rhq-devel at lists.fedorahosted.org> 
Sent: Tuesday, June 11, 2013 8:35:47 PM 
Subject: agent-no-start with or without arg? 

I added the "--agent-no-start" option to rhqctl a few days ago. It takes true or false as an argument (the default is false). 

I did this because I tend to prefer options whose two boolean values can be specified explicitly (true or false). Without accepting a value, there is no way to explicitly say you want the agent to start (the only way would be to not specify --agent-no-start). 

So we have: 

--agent-no-start=false means to start the agent after being installed (this is the default) 
--agent-no-start=true means don't start. 

However, I sense this might be confusing. 

Should I just make this a non-arg option? So to not have the agent start, you specify --agent-no-start. To have the agent start (which is the default behavior) you don't specify it at all. 

We are using org.apache.commons.cli.Options, I don't think you can tell it to have an optional argument (like you can with gnu getopt). If you CAN do this, let me know. 

What say you? If we want to change it, I want to do so now before release. 
_______________________________________________ 
rhq-devel mailing list 
rhq-devel at lists.fedorahosted.org 
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fedorahosted.org/pipermail/rhq-devel/attachments/20130611/ec0c9566/attachment.html>


More information about the rhq-devel mailing list