On Wed, 30 Oct 2002 13:32:59 -0700
Jeffrey P Shell <[EMAIL PROTECTED]> wrote:
> On Wednesday, October 30, 2002, at 04:22 AM, Chris Withers wrote:
>
> > Ross J. Reedstrom wrote:
> >> It what world do you live, and can I move there?
> >
> > You miss the point ;-)
> >
> > The flurry to get features
Jeffrey P Shell wrote:
But release often is a BITCH for software configuration management.
Good for developers, bad for deployers.
Why?
Chris
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross
>
> Likewise, with Zope my impression is that once the Beta is cut, we are in
> feature freeze. Now, ZC may not have operated that way in the
> past *entirely*,
> but I think we should from now on.
>
> A flurry of commits *before* feature freeze seems unaviodable, however.
> That's what deadlin
On Wednesday, October 30, 2002, at 04:22 AM, Chris Withers wrote:
Ross J. Reedstrom wrote:
It what world do you live, and can I move there?
You miss the point ;-)
The flurry to get features into a 'stable' release is what I was on
about.
If you flurry, the release won't be stable.
I like t
On Wed, 30 Oct 2002, Chris Withers wrote:
> The flurry to get features into a 'stable' release is what I was on about.
> If you flurry, the release won't be stable.
>
> I like the pattern of having stable releases and CVS or nightly builds for
> people who want the latest and greatest. That way eve
Ross J. Reedstrom wrote:
It what world do you live, and can I move there?
You miss the point ;-)
The flurry to get features into a 'stable' release is what I was on about.
If you flurry, the release won't be stable.
I like the pattern of having stable releases and CVS or nightly builds for
pe
Oliver Bleutgen writes:
> ...
> > What do _you_ think 'normal open source practice' is?
>
>
> FWIW, see as an example
> http://developer.kde.org/development-versions/kde-3.0-release-plan.html
>
> and/or
> http://developer.kde.org/development-versions/kde-3.2-features.html
>
> Seems t
Ross J. Reedstrom wrote:
It what world do you live, and can I move there? Every large open source
project I've particpated in or kept track of has had this problem - it's
_really hard_ to turn down cool new patches just because your supposed to
be in feature freeze, trying to get a stable releas
On Tue, Oct 29, 2002 at 09:55:40AM +, Chris Withers wrote:
> Chris McDonough wrote:
> >FWIW, the reason that there is a flurry of activity before any release
> >is because people want to see features in a stable release version and
> >by nature (IMHO) programmers are procrastinators. ;-)
>
> T
Chris McDonough wrote:
FWIW, the reason that there is a flurry of activity before any release
is because people want to see features in a stable release version and
by nature (IMHO) programmers are procrastinators. ;-)
This doesn't fit with normal open source practice. Why are we starting to
op
On 21 Oct 2002, Chris McDonough wrote:
> on a "stable release". Quis custodiet ipsos custodes? ;-)
That's the job of the "release engineer". And the community
as a whole gets to pass judgement on him or her .
--RDM
___
Zope-Dev maillist - [EMAIL PR
> For sanity's sake, 2.6.x is now the current maintenance branch, not the
> place to put new features. New features should only go into 2.7. We
> need to get out of the hotfixes business. Adherence to strict rules is
> the right way to get there.
And just for the record:
The bad old Zope tradi
Leonardo Rochael Almeida wrote:
On Mon, 2002-10-21 at 13:33, Andy McKay wrote:
In Florent's message on date screwup he mentioned 2.6.1...
I know 2.6.1 is supposed to be finished pretty soon but not within a week,
right? :-)
Is there a plan, schedule etc for 2.6.1? I couldn't find it in the
On Mon, 2002-10-21 at 13:33, Andy McKay wrote:
> In Florent's message on date screwup he mentioned 2.6.1...
>
> > I know 2.6.1 is supposed to be finished pretty soon but not within a week,
> right? :-)
>
> Is there a plan, schedule etc for 2.6.1? I couldn't find it in the Wiki's
> but that doesn'
> For sanity's sake, 2.6.x is now the current maintenance branch, not the
> place to put new features. New features should only go into 2.7. We
> need to get out of the hotfixes business. Adherence to strict rules is
> the right way to get there.
Thanks, you've answered my second question and I
FWIW, the reason that there is a flurry of activity before any release
is because people want to see features in a stable release version and
by nature (IMHO) programmers are procrastinators. ;-)
You could say that the folks in charge at ZC should back out any changes
that happen in the period bet
16 matches
Mail list logo
