'juju destroy-environment' missing from 'juju help'

[Jono Bacon]

$SUBJECT says it all. 'juju help' gives me:

jono@forge:~$ juju help
Juju -- devops distilled
https://juju.ubuntu.com/

Juju provides easy, intelligent service orchestration on top of environments
such as OpenStack, Amazon AWS, or bare metal.

Basic commands:
  juju init generate boilerplate configuration for juju environments
  juju bootstrap start up an environment from scratch

  juju deploy deploy a new service
  juju add-relation add a relation between two services
  juju expose expose a service

  juju help bootstrap more help on e.g. bootstrap command
  juju help commands list all commands
  juju help topics list all help topics

juju destroy-environment is missing. Also see https://bugs.launchpad.net/juju-core/+bug/1182902

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: juju-core 1.10.0.1-0ubuntu3
ProcVersionSignature: Ubuntu 3.9.0-2.6-generic 3.9.2
Uname: Linux 3.9.0-2-generic i686
ApportVersion: 2.10.2-0ubuntu1
Architecture: i386
Date: Wed May 22 14:03:01 2013
InstallationDate: Installed on 2013-05-05 (17 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130504)
MarkForUpload: True
SourcePackage: juju-core
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[James Page (james-page)]

Raised upstream; I think that generally the new CLI need to be made more compliant with UNIX standards.

[William Reade (fwereade)]

It's missing from the "basic commands" list, but is listed in `juju help commands` (referenced in the default help) and described in `juju help destroy-environment`.

What's the rationale for adding destroy-environment specifically to the most-important-commands list? If we add everything, it becomes a somewhat unhelpful firehose -- not quite as bad as bzr would be, but still not very pleasant -- and it seems to us that the bzr model is actually helpful and worth following.