Re: [Checkins] SVN: zc.sourcefactory/branches/0.3/buildout.cfg Move to more modern buildout setup. In library packages we really don't want
On Tue, Jun 10, 2008 at 10:42 AM, Christian Theune <ct@gocept.com> wrote:
Log message for revision 87286: Move to more modern buildout setup. In library packages we really don't want to fix all the versions.
Actually, I think we do want to fix the versions, but using the KGS. -- Benji York Senior Software Engineer Zope Corporation
On Tue, Jun 10, 2008 at 11:12:22AM -0400, Benji York wrote:
On Tue, Jun 10, 2008 at 10:42 AM, Christian Theune <ct@gocept.com> wrote:
Log message for revision 87286: Move to more modern buildout setup. In library packages we really don't want to fix all the versions.
Actually, I think we do want to fix the versions, but using the KGS.
Maybe on a branch, but not on a trunk and not using a local implementation of `version=` ;) -- Christian Theune · ct@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development
On Tue, Jun 10, 2008 at 11:21 AM, Christian Theune <ct@gocept.com> wrote:
On Tue, Jun 10, 2008 at 11:12:22AM -0400, Benji York wrote:
On Tue, Jun 10, 2008 at 10:42 AM, Christian Theune <ct@gocept.com> wrote:
Log message for revision 87286: Move to more modern buildout setup. In library packages we really don't want to fix all the versions.
Actually, I think we do want to fix the versions, but using the KGS.
Maybe on a branch, but not on a trunk and not using a local implementation of `version=` ;)
I disagree; we should be explicit about what versions we test with (including the trunk). I believe this discussion has come up before; I don't believe we came up with a hard and fast policy at that point. I'm not interested enough to have the argument now, but for anything that I maintain I'll certainly want nailed versions on the trunk (KGS or otherwise). -- Benji York Senior Software Engineer Zope Corporation
On Tue, Jun 10, 2008 at 11:34:45AM -0400, Benji York wrote:
On Tue, Jun 10, 2008 at 11:21 AM, Christian Theune <ct@gocept.com> wrote:
On Tue, Jun 10, 2008 at 11:12:22AM -0400, Benji York wrote:
On Tue, Jun 10, 2008 at 10:42 AM, Christian Theune <ct@gocept.com> wrote:
Log message for revision 87286: Move to more modern buildout setup. In library packages we really don't want to fix all the versions.
Actually, I think we do want to fix the versions, but using the KGS.
Maybe on a branch, but not on a trunk and not using a local implementation of `version=` ;)
I disagree; we should be explicit about what versions we test with (including the trunk). I believe this discussion has come up before; I don't believe we came up with a hard and fast policy at that point. I'm not interested enough to have the argument now, but for anything that I maintain I'll certainly want nailed versions on the trunk (KGS or otherwise).
Unfortunately I won't shut up immediately. ;) I think it was very helpful that the buildbot picked up the changes of zope.tal for the other packages' trunks quickly so we all still knew why they broke. We would loose that when sticking to explicit versions and get updated much much later requiring us to work harder to remember what happened. Christian -- Christian Theune · ct@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development
On Tue, Jun 10, 2008 at 11:39 AM, Christian Theune <ct@gocept.com> wrote:
Unfortunately I won't shut up immediately. ;)
That's ok, I will. ;) This is a classic discussion, there are pros and cons to each perspective. -- Benji York Senior Software Engineer Zope Corporation
participants (2)
-
Benji York -
Christian Theune