releasing documentation: make check-dist-tarball and plugins

[Vincent Ladeuil]

>>>>> "jam" == John Arbash Meinel <john at arbash-meinel.com> writes:

    jam> Aaron Bentley wrote:
    >> Bob Tanner wrote:
    >>> 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
    >> 
    >> That bug is not in bzrtools 1.3.0, which is what you should be bundling,
    >> so I don't see why this is an issue.

Good point. (1.13 of course)

    >> 
    >> Aaron

    jam> He isn't bundling anything. "make check-dist-tarball" takes the tarball
    jam> that "make dist" generated, extracts it into /tmp and runs "make check".


    jam> The issue is that the new extraction also tests whatever plugins you
    jam> happen to have installed in ~/.bazaar/plugins (or presumably in your
    jam> site-wide configuration as well).

    jam> Potentially 'make check-dist-tarball' should be running 'bzr selftest
    jam> --no-plugins' since it isn't otherwise isolating the release from the
    jam> rest of your installation.

+1

And that's very important, we really need a better way to handle
plugins (I nearly went nuts working on selftest in a loom while
having loom failures and wanting to avoid --no-plugins (mv loom
DISABLED/ ; do one thing ; mv DISABLED/loom . ; do another
thing).

        Vincent