"submit" command naming - just "bundle" preferred?

[Ian Clatworthy]

Aaron Bentley wrote:

> Yes.  diff -r submit:..-1

Thank-you.

>> After it gets through review, I switch to my integration branch, merge
>> it there, push to the public mirror of my integration branch and
>> pqm-submit.
> 
> This is because you only have a single public branch?

Well one per release series.

>> To clarify the outcomes so far, "submit" will be renamed "send", bundle
>> will be an alias and we'll continue discussing how best to configure
>> send to do the actual email/submission bit? Or is submit staying and
>> send is only the latter?
> 
> I'm loathe to call it "send" before we make it possible to send.

That's a fair argument, but submit fails that same test, yes?

My primary concern right now is UI churn. I'm not keen on revising the
documentation several times as the recommended commands change 3 times
in 3 releases (worse case):

* 0.18 = bundle or merge-directive
* 0.19 = submit
* 0.20 = send

I feel we ought to call submit send now or agree to leave it as submit
later.

Ian C.