On Oct 15, 2013, at 9:31 , Harald Friessnegger wrote:
> hi jens
>
> sure, i'll forward port the changes to trunk too. just wanted to wait until
> you guys are ok with it.
>
> normally i'd add Products.CMFCore to the plone cordev buildout to make sure
> the new version gets released with plon
On Oct 15, 2013, at 9:09 , yuppie wrote:
> Jens Vagelpohl wrote:
>> I have created a new release and uploaded it to PyPI.
>
> -2.2.8 (unreleased)
> +2.2.8 (2014-10-15)
>
> You've got a time machine? Cheers, Yuppie
Sorry, typo. I have corrected the file in SVN
On Oct 14, 2013, at 23:02 , Harald Friessnegger wrote:
> hi jens
>
> i've added a test for my change.
> http://svn.zope.org/Products.CMFCore/branches/2.2/Products/CMFCore/tests/test_SkinsTool.py?rev=130325&view=rev
>
> can you fix the other tests and make a new release?
Hi Harald,
You have
On Oct 14, 2013, at 13:31, Harald Friessnegger wrote:
> hi jens
>
> you're right about a missing test for the change.
> however, the method getSkinNameFromRequest is not involved in any unit-test
> by now.
> if you wont' add the change to the next release w/o a propert test, i'll add
> it. ju
On Oct 11, 2013, at 19:11 , Tres Seaver wrote:
> Signed PGP part
> On 10/11/2013 07:34 AM, Harald Friessnegger wrote:
> > hi tres
> >
> > sorry for the last mail. it got sent accidentally before i could
> > finish it.
> >
> > i did a minor change to cmfcore that i'd love to see in the next
> >
Hi all,
I don't recall any information being provided to the CMF developers about CMF
fixes in the most recent Plone Hotfix:
http://plone.org/products/plone-hotfix/releases/20121106
For example, there's a monkey patch to make sure getToolByName only returns
valid tool objects and nothing else,
On Apr 9, 2012, at 23:10 , Charlie Clark wrote:
> Am 22.03.2012, 13:28 Uhr, schrieb yuppie :
>
>> The tools are *local* utilities. Including the ZCML doesn't fix this issue.
>> You have to run the upgrade step.
>
> Should we add a warning to CMFTools.utils.getToolByName? To use getUtility
> a
On Apr 5, 2012, at 17:08 , Charlie Clark wrote:
> fuchsia:Products.DCWorkflow charlieclark$ bin/sphinx-build docs tmp
> Running Sphinx v1.1.3
> loading pickled environment... done
> No builder selected, using default: html
> building [html]: targets for 0 source files that are out of date
> updat
On Apr 4, 2012, at 19:54 , Charlie Clark wrote:
>> """
>> fuchsia:CMF charlieclark$ bin/sphinx-build src/Products.CMFDefault/docs tmp
>> Running Sphinx v1.1.2
>> Exception occurred:
>> File "/Users/charlieclark/Sites/CMF/src/Products.CMFDefault/docs/conf.py",
>> line 16, in
>>import pkginfo
On Apr 3, 2012, at 14:55 , Charlie Clark wrote:
> I had a go at autogenerating the api documentation but failed miserably -
> lots of empty pages got generated because Sphinx had trouble with import
> paths. Does anyone know the appropriate incantations for this?
I have fixed it by creating a s
Hi Charlie,
On Apr 3, 2012, at 14:55 , Charlie Clark wrote:
> Am 03.04.2012, 14:11 Uhr, schrieb yuppie :
>
>> +1
>> Is CMFDefault/help now obsolete? Could it be deleted?
>
> I guess so. I'm still working on "tidying" up what can loosely be termed as
> the narrative documentation. Still in the c
On Mar 31, 2012, at 17:03 , Charlie Clark wrote:
> Am 21.03.2012, 22:58 Uhr, schrieb Jens Vagelpohl :
>
>> The beta eggs are released now.
>
> Jens,
>
> could we have a patch release to include my fallbacks? I'd like to be able to
> try the beta with a coup
On Mar 22, 2012, at 13:42 , Charlie Clark wrote:
> PS. I've just run tests on trunk and am getting failures in CMFCore:
The tests only fail on Python 2.7, they run through fine on 2.6. As such,
they're not functional failures but failures dur to changes in behavior between
2.6 and 2.7. In one
On Mar 20, 2012, at 23:25 , Jens Vagelpohl wrote:
>
> On Mar 20, 2012, at 16:14 , Charlie Clark wrote:
>
>> Hi,
>>
>> I finally landed my update step for syndication during the PyCon sprints! I
>> thought I had a few more browser views to update to using
On Mar 21, 2012, at 15:55 , Charlie Clark wrote:
> Am 21.03.2012, 00:36 Uhr, schrieb Tres Seaver :
>
>> Sounds good. We should review the code for any stuff
>> deprecated-and-promised-to-be-remove-in-2.3 before releasing a beta.
>
> I suppose we could also migrate the old Zope Help docs to "do
On Mar 20, 2012, at 16:14 , Charlie Clark wrote:
> Hi,
>
> I finally landed my update step for syndication during the PyCon sprints! I
> thought I had a few more browser views to update to using the
> EditSettingsForm but on a quick check of the files it seems that this has
> already been don
On Sep 12, 2011, at 11:52 , yuppie wrote:
> Hi!
>
>
> 5 years ago we started converting CMF tools into local utilities, and we
> are still stuck in the middle of that task.
>
> The problem is that local utilities don't have REQUEST in their
> acquisition chain. A few tool methods use self.RE
On Aug 11, 2011, at 21:10 , Hanno Schlichting wrote:
> On Sun, Aug 7, 2011 at 5:13 PM, Jens Vagelpohl wrote:
>> After the wrapping, the discussion item has the wrong path. Even though
>> "self", the "talkback" object, has the correct path when calling
&g
On Aug 7, 2011, at 07:00 , CMF tests summarizer wrote:
>
> [1]UNKNOWN FAILED (failures=3, errors=4) : CMF-trunk Zope-trunk
> Python-2.6.6 : Linux
> https://mail.zope.org/pipermail/cmf-tests/2011-August/015089.html
I have tried to pinpoint the reason for some of these test failures. Tw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/19/11 13:15 , Laurence Rowe wrote:
> Hi,
>
> What are the CMF 2.3 release plans? If we wanted to consider this for
> Plone 4.2 we would need a release fairly soon so we could make the
> required changes around member handling.
Hi Laurence,
I co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/9/11 11:18 , Lennart Regebro wrote:
> On Sat, Apr 9, 2011 at 10:11, Jens Vagelpohl wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 4/9/11 09:09 , Suresh V. wrote:
>>> Please see:
>&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/9/11 09:09 , Suresh V. wrote:
> Please see:
>
> http://stackoverflow.com/questions/5603459/genericsetup-what-does-toolset-xml-accomplish-if-toolinit-still-has-to-be-called
>
> I could not create a "cmf" tag, so if you can please add that to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/2/11 12:15 , Suresh V. wrote:
> How come the following versions are not found in svn tags?
>
> Products.CMFCore: Versions 2.2.1, 2.2.2, 2.2.3
I have no idea where you are looking, but those tags exist. See
http://svn.zope.org/Products.CMFCore/ta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/21/10 13:58 , CMF Tests Summarizer wrote:
> Summary of messages to the cmf-tests list.
> Period Wed Oct 20 12:00:00 2010 UTC to Thu Oct 21 12:00:00 2010 UTC.
> There were 4 messages: 4 from CMF Tests.
>
>
> Unknown
> ---
>
> Subject: UNKNO
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/12/10 20:45 , Charlie Clark wrote:
> Am 23.09.2010, 12:47 Uhr, schrieb Jens Vagelpohl :
>
>> Let's talk about 2.2 releases after the bug day then.
>
> Hi Jens,
>
> I'd like a 2.2 release to include the fixes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/30/10 23:54 , Charlie Clark wrote:
> I propose to add Site Syndication Settings to the actions/global and
> remove the Properties form from the SyndicationTool. I also think that
> synPropertiesForm should be moved to actions/folder and the co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Charlie,
> "enable_permalink". Now, while this is easy enough to add both to the
> Script and my view and there is support for this in
> zpt_generic/main_template with get_permalink, there is actually an
> implicit dependency about CMFUid for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/23/10 12:38 , yuppie wrote:
> My goal is to have *one* branch for each CMF version. (Except of CMF
> 2.1, which has also a non-buildout branch.) I think we have always a
> primary target platform that is used for development (e.g. Zope trunk
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/23/10 11:36 , Charlie Clark wrote:
> Am 23.09.2010, 10:40 Uhr, schrieb yuppie :
>
>> Are you sure you want to make these changes in CMF 2.1? Jens is not
>> talking about CMF 2.2 or trunk.
>
> Oh, yeah. Sorry, so caught up in 2.3 awesomeness that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/23/10 11:39 , Charlie Clark wrote:
> Hi,
>
> Yuppie brought this up at the "Dresden Sprint": does anyone have any
> objections to removing the "ursa" and "werebear" skins in 2.3? Both are
> just examples of using a BrowserView for the tool lo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/23/10 11:36 , Charlie Clark wrote:
> Am 23.09.2010, 10:40 Uhr, schrieb yuppie :
>
>> Are you sure you want to make these changes in CMF 2.1? Jens is not
>> talking about CMF 2.2 or trunk.
>
> Oh, yeah. Sorry, so caught up in 2.3 awesomeness that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/22/10 20:49 , Charlie Clark wrote:
> Am 22.09.2010, 14:31 Uhr, schrieb Jens Vagelpohl :
>
>> Are there any outstanding issues or blockers that need resolving or can
>> I go ahead and publish the new releases?
>
> Wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I've lost a little track of release plans for the 2.1 branch, just got
back from a vacation. Eric Steele would like a new CMF 2.1 release, and
the following eggs have changes:
- Products.CMFCalendar
- Products.CMFCore
- Products.CMFDefault
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Yuppie,
> I can't see any additional burden caused by the proposed change.
The burden will appear when people are told or get the impression that
the package represents the official sanctioned buildout for the CMF as
opposed to being a developer c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/5/10 16:52 , yuppie wrote:
> Charlie Clark wrote:
>> I'm actively abstaining as while I understand the need to clean things up,
>> I'm not sure I understand the whole context (my lack of understanding
>> rather than any lack of explanation). CMF i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Subject: FAILED (failures=15) : CMF-2.2 Zope-2.12 Python-2.6.5 : Linux
> From: CMF Tests
> Date: Thu Jul 29 21:57:59 EDT 2010
> URL: http://mail.zope.org/pipermail/cmf-tests/2010-July/013347.html
>
> Subject: FAILED (failures=15) : CMF-trunk Zope-2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/4/10 13:46 , Hanno Schlichting wrote:
> On Sun, Jul 4, 2010 at 11:30 AM, Jens Vagelpohl wrote:
>> As you may have seen from the checkins, I have done a CMF 2.2 point
>> release. Hanno said this would help Plone 4 testing.
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
As you may have seen from the checkins, I have done a CMF 2.2 point
release. Hanno said this would help Plone 4 testing.
jens
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iEYEARECAAYFAkwwVLUACgkQRAx5nvEhZLLTaQCfdyWFFYqxtp6Mh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/26/10 14:05 , Hanno Schlichting wrote:
> This looks like its caused by Jens cleanup in Zope2:
>
> Error in test test_manage_propertiesForm_allows_adding
> (Products.CMFCore.tests.test_ActionInformation.ActionTests)
> Traceback (most recent call l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/14/10 15:49 , Charlie Clark wrote:
>File
> "/Users/charlieclark/Sites/cmf-svn/CMF.buildout/trunk/src/Zope2/src/OFS/SimpleItem.py",
>
> line 45, in
> from App.Undo import UndoSupport
>File
> "/Users/charlieclark/Sites/cmf-svn/C
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/14/10 15:43 , Charlie Clark wrote:
> Am 09.04.2010, 13:38 Uhr, schrieb Jens Vagelpohl :
>
>> Needless to say, this is more useful when using a CookieCrumbler as a
>> standalone object without a portal. The CMF does not need th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/9/10 13:29 , Charlie Clark wrote:
> Any idea why CookieCrumbler is a Folder?
They can contain objects that can be used as login/logout pages, such as
DTML methods or Page Templates.
Needless to say, this is more useful when using a CookieCrumb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/9/10 11:09 , Charlie Clark wrote:
> Am 09.04.2010, 10:58 Uhr, schrieb Jens Vagelpohl :
>
>>> I'll remove it from editToolsActions.dtml then. Can we backport this to
>>> CMF 2.2?
>> Sure.
>
> Committed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/9/10 10:54 , Charlie Clark wrote:
>> That warning should not show up for type-specific Actions. They are not
>> deprecated. This is a bug.
>
> I'll remove it from editToolsActions.dtml then. Can we backport this to
> CMF 2.2?
Sure.
> In my w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/7/10 13:09 , Charlie Clark wrote:
> Hi,
>
> I'm currently working on a project which will hopefully have no TTW code
> so I was hoping to be do without skins - currently I have a my skin on top
> of CMFDefault but it is just main_template and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/1/10 12:28 , yuppie wrote:
> Jens Vagelpohl wrote:
>> On 4/1/10 12:10 , yuppie wrote:
>>> IIRC the general policy for the Zope repository is to switch to relative
>>> externals after the release of Ubuntu 10.04
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/1/10 12:10 , yuppie wrote:
> IIRC the general policy for the Zope repository is to switch to relative
> externals after the release of Ubuntu 10.04 LTS, but I guess all people
> using CMF.buildout have already Subversion >=1.5 available.
Huh? S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/31/10 22:07 , Tres Seaver wrote:
> Jens Vagelpohl wrote:
>> On 3/31/10 20:33 , Tres Seaver wrote:
>>> I also don't know why the 'instance' and 'i18n*' parts are configured in
>>> these buildout
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/31/10 20:33 , Tres Seaver wrote:
> I also don't know why the 'instance' and 'i18n*' parts are configured in
> these buildouts -- does somebody have a memory of why, or a reason to
> keep them?
The "instance" part is a pure convenience to quickly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/9/10 22:23 , Charlie Clark wrote:
> Am 09.02.2010, 13:46 Uhr, schrieb Jens Vagelpohl :
>
>> Your event handler "handle_new_masterpage" should be rewritten to look
>> if the object it wants to instantiate already exist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/9/10 13:27 , thomas.dingel...@camao.de wrote:
> Module Products.camaoCms.container.masterpage, line 59, in
> handle_new_masterpage
> Module OFS.ObjectManager, line 332, in _setObject
> Module Products.CMFCore.PortalFolder, line 313, in _che
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I noticed that the last release, 1.5.0b1, is over 3 months old. Would
anyone mind if I created a 1.5.0-final release?
jens
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iEYEARECAAYFAks8lF8ACgkQRAx5nvEhZLL2ZACfechr9IQECgcYYoYALWwepdXf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hanno Schlichting wrote:
> What you want is probably something like this:
>
> from zope.component.interfaces import ComponentLookupError
> from zope.component.interfaces import IComponentRegistry
> from zope.location.interfaces import IPossibleSite
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tres Seaver wrote:
> Hanno Schlichting wrote:
>> And then adjust exportComponentRegistry in a similar way. This is
>> untested code :)
>
> Why would a PAS plugin do such a thing? PAS doesn't expect (or want)
> any local / persistent component registr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
> On 2009-12-30 16:19, Jens Vagelpohl wrote:
>> However, even that
>> registration by interface for profiles isn't considered in the ZMI in
>> the base profile or extension profile select lists that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
> On 2009-12-30 15:35, Jens Vagelpohl wrote:
>> The reason I thought this list of steps may (should?) change is that for
>> example the PluggableAuthService profiles (both of which are BASE
>> profiles) e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
> On 2009-12-30 15:06, Jens Vagelpohl wrote:
>> Separate note: On the "Import" tab I see a dropdown of extension
>> profiles to select. Changing the selection here never affects the list
>> of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I'm working on a PAS plugin and want to ensure it has GenericSetup
support like the standard plugins. I'm running into issues trying to use
GenericSetup in a manual test, though.
With a setup_tool inside the PluggableAuthService instance I ca
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hanno Schlichting wrote:
> On Sun, Dec 27, 2009 at 8:31 PM, Jens Vagelpohl wrote:
>> Please keep release scheduling in mind. I had announced a release date
>> for CMF 2.2.0-final about a week from now. Andreas cannot possible thro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hanno Schlichting wrote:
> On a related note, if I'm going to backport the five.formlib
> extraction to 2.12, it would it be ok to depend on a 2.12.3 release
> for CMF 2.2 with this stuff in it, right?
Please keep release scheduling in mind. I had ann
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
CMF Tests Summarizer wrote:
> Summary of messages to the cmf-tests list.
> Period Thu Dec 17 12:00:00 2009 UTC to Fri Dec 18 12:00:00 2009 UTC.
> There were 4 messages: 4 from CMF Tests.
>
>
> Unknown
> ---
>
> Subject: UNKNOWN : CMF-trunk Zope-
On Dec 9, 2009, at 16:32 , yuppie wrote:
> I think it would be good to catch in .to22.check_dcmi_metadata *all*
> tools that don't have a 'DCMI' attribute.
>
> CMF 2.0 and 2.1 did not add '_DCMI' in __init__, I just changed that
> before the 2.2 beta. If the old migration code was never trigge
Hi Charlie,
> Is there an easy to way to setup a project buildout based
> on CMF? I've tried various combinations of the following:
>
> [buildout]
> extends =
> http://svn.zope.org/*checkout*/CMF.buildout/branches/zope212-cmf22/buildout.cfg
> versions = versions
> parts = parts
> eggs = eggs
Hello,
> - The MetadataTool has write-on-read migration code in _get_DCMI. That
> should be converted into two migration steps: One from CMF 1.6 to CMF
> 2.0 and one from 2.1 to 2.2.
This is done on the trunk and the 2.2 branch.
> - The upgrade scripts in CMFCore/Extensions and CMFDefault/Ext
On Dec 1, 2009, at 07:52 , Jens Vagelpohl wrote:
> Reminder: After this week (probably this coming Sunday) I plan on doing the
> first CMF 2.2 beta, and creating the 2.2 release branch.
All done now:
- release branches for the 2.2 release series are cut
- the 2.2.0 beta release is
Reminder: After this week (probably this coming Sunday) I plan on doing the
first CMF 2.2 beta, and creating the 2.2 release branch.
jens
___
Zope-CMF maillist - Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf
See https://bugs.lau
Hi Charlie,
> 1) How do I tie my buildout to 3.9.0?
> 2) Should we be updating for the change in CMF?
The buildout ties it by extending the versions.cfg file from the Zope 2 trunk.
That versions file contains these overrides:
zope.app.publisher = 3.9.0
zope.container = 3.9.0
zope.publisher = 3.
On Nov 6, 2009, at 20:16 , Tres Seaver wrote:
> Eric Steele wrote:
>
>> Jens, could I possibly talk you into releasing an alpha (or even dev?)
>> egg in the next week? After showing off Plone 4 at our conference, I'm
>> getting a flood of "when can I get an alpha?" requests daily.
>
> - -sy
On Nov 10, 2009, at 20:07 , Charlie Clark wrote:
I merged my branch in my local trunk. I spotted the path changes and
made them but I'm still getting the following error:
VocabularyRegistryError: unknown vocabulary: u'cmf.contents delta
vocabulary'
As a result I didn't commit my changes
On Nov 3, 2009, at 13:24 , Charlie Clark wrote:
Worked with Eric on my formlib for folders and fixing
https://bugs.launchpad.net/zope-cmf/+bug/308947
I can't commit my formlib for folders because the browser tests fail
due
to a utility lookup. Something must have changed in the browser test
Hi Eric,
Jens, could I possibly talk you into releasing an alpha (or even dev?)
egg in the next week? After showing off Plone 4 at our conference, I'm
getting a flood of "when can I get an alpha?" requests daily.
I'll be happy to do an alpha this coming Friday. I'd do it earlier,
but I'm tra
On Oct 30, 2009, at 14:30 , Charlie Clark wrote:
Am 30.10.2009, 14:27 Uhr, schrieb Eric Steele :
Is anyone still willing to sprint on CMF 2.2 at the Plone
conference? I
don't think I've managed to meet any of you yet. I'd like to make
sure a
sprint gets announced tomorrow if we can actual
On Oct 14, 2009, at 23:13, "Charlie Clark"
wrote:
> Me and Jens will be there and Jens will be holding the "Hat of
> Shame" over
> my head. Not sure who will be there and who'll be sober. Better
> order the
> langos in advance! ;-)
I will be there, but not for the post-conference sprints
On Oct 10, 2009, at 01:15 , Maurits van Rees wrote:
Hi,
Products.PasswordResetTool is used by CMFPlone. Is anyone using it
in a plain CMF site?
I highly doubt it. Most Plone or Collective code, even though much of
it is confusingly named "CMFsomething", does not work with plain CMF.
jen
On Sep 24, 2009, at 14:17 , Charlie Clark wrote:
Regarding something completely different - I picked up on zope-dev
that
the svn server has been updated. Does this mean that we can now use
the
svn branch to trunk merging offered in svn >= 1.5 or is this still
inadvisable? If it is still ina
On Sep 24, 2009, at 15:16 , Maurits van Rees wrote:
Personally, I am the maintainer of Products.Poi. It will take more
than one bottle of whisky to convince me to rename that. ;-)
Personally, I believe most product authors who have a real Zope 2
Product but chose a name other than "Product
On Sep 24, 2009, at 14:01 , Charlie Clark wrote:
Am 24.09.2009, 13:52 Uhr, schrieb Andreas Jung :
In my understanding: packages using the Products namespace are
subject
to be registered during the startup phase of Zope (using their
initialize()
method). And I think there is some other evil
On Sep 15, 2009, at 17:19 , Eric Steele wrote:
Hi,
Quick introduction: I'm the new Plone 4 release manager; apologies for
not popping my head up here sooner.
Assuming we don't hit any further delays, we're looking at having a
Plone 4.0 alpha available in about 6 weeks. Would it be possible to
78 matches
Mail list logo
