-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 19, 2009, at 3:08 PM, Patrick Ben Koetter wrote:
* Barry Warsaw :
The megamerge branch was merged into lazr.config proper and release
as
lazr.config 1.1. So you don't need this branch. The bzr branch of
mm3.0
is up-to-date now, but from
* Barry Warsaw :
> The megamerge branch was merged into lazr.config proper and release as
> lazr.config 1.1. So you don't need this branch. The bzr branch of mm3.0
> is up-to-date now, but from the tarball, you should just skip this step
> and edit buildout.cfg so that the "develop" line only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 18, 2009, at 2:59 PM, Patrick Ben Koetter wrote:
* Barry Warsaw :
For detailed information on 3.0a2, please read docs/ALPHA.txt. This
file explains how to build Mailman and run the test suite. The docs/
NEWS.txt file contains high level de
Patrick Ben Koetter wrote:
>
>Then I followed docs/ALPHA.txt from mailman-3.0.0a2 and tried to checkout
>megamerge. I get this and believe I shouldn't:
>
># bzr branch lp:~barry/lazr.config/megamerge
>bzr: ERROR: Not a branch: "https://code.launchpad.net/";.
>
>I can't tell if its a configuration e
* Barry Warsaw :
> For detailed information on 3.0a2, please read docs/ALPHA.txt. This
> file explains how to build Mailman and run the test suite. The docs/
> NEWS.txt file contains high level descriptions of what's changed since
> 3.0a1. Most notably are the new configuration system, the
