Hey,
Am Mittwoch, den 03.10.2007, 13:43 -0400 schrieb Jim Fulton:
> I'm skeptical that such a tool can do that much. Certainly, when we
> broke the trunk up, we didn't know what all the issues would be. We
> couldn't automate a process we didn't yet fully understand. My only
> real regret i
On 10/3/07, Fred Drake <[EMAIL PROTECTED]> wrote:
> On 10/3/07, Lennart Regebro <[EMAIL PROTECTED]> wrote:
> > It currently only makes releases as tgz, but adding eggs should be so
> > hard (it's done by calling setup.py anyway if I remember correctly).
>
> tgz files are all that's needed (or wante
On Oct 2, 2007, at 6:52 PM, Stephan Richter wrote:
On Tuesday 02 October 2007 17:14, Jim Fulton wrote:
One hole I see is giving people guidance on what needs to be tested
(and how) before a release is made. My preference would be to rely
heavily on judgement with a few checks so as not to mak
Tres Seaver wrote:
I would prefer that we quit releasing non-source distributions at all;
the exceptions would be Windows eggs for packages containing extensions.
+1
--
Benji York
Senior Software Engineer
Zope Corporation
___
Zope3-dev mailing list
Zo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lennart Regebro wrote:
> On 10/3/07, Stephan Richter <[EMAIL PROTECTED]> wrote:
>> I want tools! Actually, I just want one tool. 70% of the release process is
>> repetition and that needs to be factored into a tool. This tool should have
>> been writte
On 10/3/07, Lennart Regebro <[EMAIL PROTECTED]> wrote:
> It currently only makes releases as tgz, but adding eggs should be so
> hard (it's done by calling setup.py anyway if I remember correctly).
tgz files are all that's needed (or wanted); there's no reason to use
a .egg file. For packages tha
On 10/3/07, Stephan Richter <[EMAIL PROTECTED]> wrote:
> I want tools! Actually, I just want one tool. 70% of the release process is
> repetition and that needs to be factored into a tool. This tool should have
> been written before the Zope trunk was blown into pieces, but it wasn't. :-(
I'd reco
Stephan Richter wrote:
On Tuesday 02 October 2007 17:14, Jim Fulton wrote:
One hole I see is giving people guidance on what needs to be tested
(and how) before a release is made. My preference would be to rely
heavily on judgement with a few checks so as not to make things too
heavy. This
On Tuesday 02 October 2007 17:14, Jim Fulton wrote:
> One hole I see is giving people guidance on what needs to be tested
> (and how) before a release is made. My preference would be to rely
> heavily on judgement with a few checks so as not to make things too
> heavy. This might rule out s
On Oct 2, 2007, at 5:05 PM, Philipp von Weitershausen wrote:
Martijn Faassen wrote:
A release of zope.dottedname was made apparently today that refers
to a CHANGES.txt but doesn't have one. Probable scenario: someone
forgot to svn add a CHANGES.txt, then didn't check out before the
tag be
Martijn Faassen wrote:
A release of zope.dottedname was made apparently today that refers to a
CHANGES.txt but doesn't have one. Probable scenario: someone forgot to
svn add a CHANGES.txt, then didn't check out before the tag before
releasing...
Right. This is actually a *common* mistake. Not
11 matches
Mail list logo
