As I mentioned before, I'd like to see Christian's blob work make it
into 2.9. So that's one feature. ;-)
On Mon, 2005-06-20 at 09:55 +0200, Martijn Faassen wrote:
> Lennart Regebro wrote:
> > OK, so becuase of the tomembased release schedule, let's not dicuss
> > what goes in 2.9. let's discuss
Lennart Regebro wrote:
OK, so becuase of the tomembased release schedule, let's not dicuss
what goes in 2.9. let's discuss what features we found most
urgent/desirable, so we can start working on that, like now.
I think it's fine to discuss what we want to be in Zope 2.9. This way we
can plan
--On 19. Juni 2005 11:35:32 +0200 Lennart Regebro <[EMAIL PROTECTED]> wrote:
OK, so becuase of the tomembased release schedule, let's not dicuss
what goes in 2.9. let's discuss what features we found most
urgent/desirable, so we can start working on that, like now.
Propose something :-)
-aj
OK, so becuase of the tomembased release schedule, let's not dicuss
what goes in 2.9. let's discuss what features we found most
urgent/desirable, so we can start working on that, like now.
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/m
Jim Fulton wrote:
Martijn Faassen wrote:
[snip]
This definitely gets me worried about coordinating everybody. We need
very good planning to pull this off, something we haven't shown in
previous Zope 2 or Zope 3 release processes. Perhaps a little ambitious?
Actually, I think that time-based
--On 17. Juni 2005 13:17:13 -0400 Chris McDonough <[EMAIL PROTECTED]> wrote:
Policy aside, I trust all of these people implicitly to do the right
thing with judging whether a feature should make it into a dot release
and I wouldn't complain any of them snuck a minor feature into one. If
one
On Fri, 2005-06-17 at 13:00 -0400, Tim Peters wrote:
> [Tres Seaver]
> > Agreed, in theory. In practice, the usual handwave has been to construe
> > the absence of the feature as a bug (with greater or lesser justification).
>
> Like that's going to change .
Over the last year Tres, Andreas, Tim
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
Chris McDonough wrote:
On Fri, 2005-06-17 at 10:12 -0400, Jim Fulton wrote:
...
We have historically always ha
[Tres Seaver]
> Agreed, in theory. In practice, the usual handwave has been to construe
> the absence of the feature as a bug (with greater or lesser justification).
Like that's going to change .
> Perhaps we can be more hard-nosed about a "no new features in third-dot
> releases" policy *after*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
> Tres Seaver wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Jim Fulton wrote:
>>
>>> Chris McDonough wrote:
>>>
>>>
On Fri, 2005-06-17 at 10:12 -0400, Jim Fulton wrote:
>>>
>>> ...
>>>
>>>
We have
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
Chris McDonough wrote:
On Fri, 2005-06-17 at 10:12 -0400, Jim Fulton wrote:
...
We have historically always had the opportunity to introduce features
that preserve 100% b/c (like filestream iterators) i
Martijn Faassen wrote:
Jim Fulton wrote:
Max M wrote:
Jim Fulton wrote:
Further, we will coordinate the releases. Essentially, *Zope*
is switching to a new release schedule. Zope will be released every
6 months
and the releases will be in two parts, a Zope 2 part that includes
the curren
Jim Fulton wrote:
Max M wrote:
Jim Fulton wrote:
Further, we will coordinate the releases. Essentially, *Zope*
is switching to a new release schedule. Zope will be released every 6
months
and the releases will be in two parts, a Zope 2 part that includes
the current
Zope 3 and a Zope 3 pa
Max M wrote:
Jim Fulton wrote:
Further, we will coordinate the releases. Essentially, *Zope*
is switching to a new release schedule. Zope will be released every 6
months
and the releases will be in two parts, a Zope 2 part that includes the
current
Zope 3 and a Zope 3 part.
Will they h
14 matches
Mail list logo
