yuppie wrote:
[snip]
Overall, I would really like to find a person for each release being
responsible for backporting bug fixes. It would be a relatively easy
way to contribute to Zope 3.
IMHO maintaining the current stable branch should be the responsibility
of all developers - if you fix a
On 7/16/06, Jim Fulton [EMAIL PROTECTED] wrote:
On Jul 11, 2006, at 8:05 AM, Patrick Gerken wrote:
On 7/7/06, Julien Anguenot [EMAIL PROTECTED] wrote:
...
I marked the bug as bug + bugfix but nobody cares. That is much more
discouraging than what I can not do nice wiki links to in my
Christian Theune wrote:
Yes, but how much of this is by necessity and how much is choice?
When do we change the policy from make it nicer to make it stable?
I kind of had the impression that switching to make it stable is the
tenor of this thread.
I live in hope ;-)
(btw: it particularly
On Sep 10, 2006, at 9:00 AM, Adam Groszer wrote:
Hello,
I think I found a bug in zope.wfmc.
Let's say the ReviewPublish and ReviewReject transitions are guarded
by conditions.
---
--| Publish |
-- -- /
On Sep 10, 2006, at 9:38 AM, Philipp von Weitershausen wrote:
Tres Seaver wrote:
Stephan Richter wrote:
On Friday 08 September 2006 04:12, yuppie wrote:
Are there good reasons why these changes were not backported?
I volunteer to backport some fixes I'm missing in Zope 3.2, but
that's
no
Jim Fulton wrote:
I agree in principle. In practice, I'm not sure we have enough
maintainers to get a release out, let alone maintain two previous
release branches. :( We need more volunteers.
If we want to maintain releases for a year, I suspect we need to release
once a year.
I did
On Sep 11, 2006, at 5:47 AM, Patrick Gerken wrote:
On 7/16/06, Jim Fulton [EMAIL PROTECTED] wrote:
On Jul 11, 2006, at 8:05 AM, Patrick Gerken wrote:
On 7/7/06, Julien Anguenot [EMAIL PROTECTED] wrote:
...
I marked the bug as bug + bugfix but nobody cares. That is much
more
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philipp von Weitershausen wrote:
Jim Fulton wrote:
I agree in principle. In practice, I'm not sure we have enough
maintainers to get a release out, let alone maintain two previous
release branches. :( We need more volunteers.
The marginal
On Mon, 2006-11-09 at 11:28 -0400, Tres Seaver wrote:
Philipp von Weitershausen wrote:
Jim Fulton wrote:
I agree in principle. In practice, I'm not sure we have enough
maintainers to get a release out, let alone maintain two previous
release branches. :( We need more volunteers.
The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rocky Burt wrote:
On Mon, 2006-11-09 at 11:28 -0400, Tres Seaver wrote:
Philipp von Weitershausen wrote:
Jim Fulton wrote:
I agree in principle. In practice, I'm not sure we have enough
maintainers to get a release out, let alone maintain two
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Patrick Gerken wrote:
On 7/16/06, Jim Fulton [EMAIL PROTECTED] wrote:
On Jul 11, 2006, at 8:05 AM, Patrick Gerken wrote:
On 7/7/06, Julien Anguenot [EMAIL PROTECTED] wrote:
...
I marked the bug as bug + bugfix but nobody cares. That is much
Hi,
It's piece of cake making the [Logout] to appear with
adapter
for=zope.publisher.interfaces.browser.IBrowserRequest
factory=zope.app.security.LogoutSupported
/
How do I do this if I have several different applications in one
instance? They start to complain about
On Monday 11 September 2006 13:23, Adam Groszer wrote:
The solution might be simple, but at this late time I don't see it.
Any help is welcome.
No, the solution was not even possible (easily) till recently. For exactly
this use case I developed z3c.baseregistry, which allows you to make
Tres Seaver wrote:
Rocky Burt wrote:
On Mon, 2006-11-09 at 11:28 -0400, Tres Seaver wrote:
Philipp von Weitershausen wrote:
Jim Fulton wrote:
I agree in principle. In practice, I'm not sure we have enough
maintainers to get a release out, let alone maintain two previous
release branches. :(
Hi.
Rocky Burt wrote:
On Mon, 2006-11-09 at 11:28 -0400, Tres Seaver wrote:
I've only ever worked on one open source project where I was not
supposed to backport my fixes to the maintenance release branches and
that is Plone. For Plone we have someone responsible for back-portting
that
Hello,
I am working on a 'light' version of Zope, where all deprecated things are
removed (and maybe other less useful things). Although this is probably not
convenient for the main part of Zope developers, this has some benefits for our
internal project, and probably for other people:
- easier
Florent wrote:
I propose to patch the 'trunk' in order to allow removing of these packages.
Here are the proposed changes:
- catch 'ImportError' when we make use of zope.app.skins
- introduce ZCML feature 'deprecatedlayers' which is 'on' by default
and can be disabled
- add a
Christian Theune wrote:
what's the status on the release? We should have an RC and maybe a
release in one or two weeks.
Yup. We will be making an RC this week.
Philipp
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub:
Florent Xicluna wrote:
I am working on a 'light' version of Zope
You may want to contribute toward eggifying Zope 3 for the next
release. Once Z3 is sufficiently broken into individual components,
projects can use as few (or many) as they need.
--
Benji York
Senior Software Engineer
Zope
Rocky Burt wrote:
Thanks Hanno!
I don't think we should take Hanno for granted (not that you do) - he
does some incredible work, and he's always done it without anyone asking
him to do so. It benefits Plone more than people realise, and we're
really fortunate. If Hanno was less generuos or
Hi,
as we're running late already on Zope 3.3 and also running into the
original alloted time for 3.4, I've taken a minute to update the RoadMap
[1].
As far as I understand the grand plan for Zope 3.4 is the eggification.
I don't see any proposal attached to that, but we better get this
rolling
On Sep 11, 2006, at 5:22 PM, Florent Xicluna wrote:
Florent wrote:
I propose to patch the 'trunk' in order to allow removing of these
packages.
Here are the proposed changes:
- catch 'ImportError' when we make use of zope.app.skins
- introduce ZCML feature 'deprecatedlayers' which is 'on'
The Buildbot has detected a failed build of Zope3 trunk 2.4 Windows 2000
zc-bbwin3.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 7604
Blamelist: baijum
BUILD FAILED: failed failed slave lost
sincerely,
-The Buildbot
23 matches
Mail list logo
