releasing documentation: make check-dist-tarball and plugins

[Bob Tanner]

When making a release should plugins be disabled?

The plugin issue is not noted in the releasing documentation.

https://bugs.launchpad.net/bzrtools/+bug/345597

Is a bug in bzrtools, detected when I was doing make check-dist-tarball

Should any plugins be active during a release build and test?

If the plugins should be deactive, just mv the plugin directory out of  
the way or is there a command line switch to deactivate them?

IF some plugins should be part of the build/test of a release:

Like my todo on tracking down the list of python projects needed to  
build and test, I would like to make a list of bzr plugins that are  
needed (if any) to build and test.

Thanks.

--
Bob Tanner <tanner at real-time.com>                 | Phone : 952-943-8700
http://www.real-time.com, Linux, OSX, VMware | Fax      : 952-943-8500
Key fingerprint = F785 DDFC CF94 7CE8 AA87 3A9D 3895 26F1 0DDB E378
















-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20090320/0376c2d2/attachment.pgp