Re: [Zope-CMF] CMF 1.5.3 beta?

2005-08-01 Thread Jens Vagelpohl
If we have a go for the beta I suggest cutting the tag and  
publishing the release tomorrow morning, about 9am british time.  
That way zope.org won't have traffic from the Americas, making it  
marginally more responsive ;)





Great, thanks! I am planning to release Plone 2.1 final in 2 weeks.  
Would be convenient to have CMF 1.5.3 final by then.


Yes, if we can keep the beta cycle short and the changeset  
manageable. With everyone helping out testing the changed bits that  
came in since 1.5.2 and no big isssues arising a single beta can be  
sufficient.




I'm here, I'm here jumps up and down.

If you'd dis Plone a little less I am sure more of us would chime  
in more often ;-)


Don't tell me you're scared of certain peoples' personal opinion... :P

jens

___
Zope-CMF maillist  -  Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See http://collector.zope.org/CMF for bug reports and feature requests


Re: [Zope-CMF] CMF 1.5.3 beta?

2005-08-01 Thread Alec Mitchell
On Monday 01 August 2005 06:55 am, Florent Guillaume wrote:
 However I'd like to urge the Plone guys (95% of which don't bother to
 read or post in this list) to move their collective butts and actually
 implement forward-compatibility in Plone itself rather that, once more,
 tying the release of a base software to their own schedule.

I'm on here too, though pretty quiet.  I've even been subscribed here longer 
than I have been subscribed to plone-devel.

As stated, the only important issues are minor bugfixes in CMF 1.5.  We'd be 
OK without them, but everybody would be better off with them.  Maintaining 
our own monkeypatch set with every svn fix to CMF is a bit untenable.

Alec
___
Zope-CMF maillist  -  Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See http://collector.zope.org/CMF for bug reports and feature requests


Re: [Zope-CMF] CMF 1.5.3 beta?

2005-08-01 Thread Florent Guillaume
Jens Vagelpohl  [EMAIL PROTECTED] wrote:
 Florent: Quick heads-up to me when you're done with your changes,  
 please.

Ok I'm done I think.

Heads up for Plone devs (but we were discussing it on #plone):
The change I made impacts the signature of CatalogTool.reindexObject,
which until recently Plone was overloading.

http://svn.zope.org/CMF/branches/1.5/CMFCore/CatalogTool.py?rev=37626view=rev

Florent

-- 
Florent Guillaume, Nuxeo (Paris, France)   CTO, Director of RD
+33 1 40 33 71 59   http://nuxeo.com   [EMAIL PROTECTED]
___
Zope-CMF maillist  -  Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See http://collector.zope.org/CMF for bug reports and feature requests


[Zope-CMF] Re: Plone participation in the CMF list

2005-08-01 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Jens Vagelpohl wrote:

 We have contributed quite a few bug fixes to CMF, though that has been
 hampered by problems getting CVS access (I sent in my contributor form
 over a year ago and have yet to hear anything; as Tres has indicated,
 this has been a problem for several other Plone developers as well).

 I'm hoping that will move along faster now. That's out of the hands  of
 any of the active developers unfortunately.

I am working with Jim and Andrew to expedite access for Geoff and for
Alec Mitchell.  Please let me know of any other Plone folks who want to
contribute to CMF but whose repository access is stuck.


 We have also offered some fairly substantial pieces of code to the CMF
 (Archetypes, CMFFormController, SpeedPack), but have met with
 indifference and/or active rejection.  I have several products I think
 could find a home in the CMF, but given the response to previous  offers,
 I'm not sure it's worth the trouble to make the offer.

 I don't claim to know the details of how that went down, but I
 distinctly remember from the time both Tres and I were still at ZC  that
 Tres offered to incorporate AT and have it become part of CMF.  I'm not
 sure who exactly he talked to, but from what I remember that  was met
 with the same indifference you're attesting the CMF community.

One issue was licensing;  contributor access may also have been a
problem for some folks.  I think the discussion around Archetypes, in
particular, ended up stalled over the question of whether to code
generation design should be preferred over configuration-based design
(as found in CPSSchemas, for instance).

 In general, I sense a fair amount of hostility to Plone expressed  on the
 list in the form of gratuitous sniping.

 If you want us to participate, it might help to play more nicely.

 I would like to note that CMF != Plone. Plone is the largest
 consumer, correct, but that doesn't mean everyone who uses CMF uses
 Plone, or that individual participants are forbidden to have a  negative
 opinion about Plone. Life on mailing lists is tough and full  of taunts
 and flame throwing. The CMF list is actually one of the  least
 offensive lists I am on.

Gratuitous is the key here -- neither the CMF nor Plone are perfect
pieces of software, and we can all be honest (and even fairly peeved, at
times) about that.  We shouldn't have to attribute malice or stupidity
to each other over that fact, however:  there is plenty enough blame to
go around.

Geoff, we *do* want the Plone developers to participate here.  Some of
the past history we can let pass, in order to share better in the
future.  In general, we would like to see infrastructure components
shared, where possible.

 That said, I have heard some good ideas from e.g. Paul about how to
 re-align the factions better in the future and I hope both Paul and
 Tres can talk about it more in Vienna, and pull in suitable Plone
 leaders. It would help everyone if the CMF side opened up a little  more
 to ideas coming down from Plone, and if the Plone side stopped
 reinventing wheels that would be much better off (and benefit  everyone)
 in the CMF or other non-Plone core products.

Exactly.


Tres.
- --
===
Tres Seaver  +1 202-558-7113  [EMAIL PROTECTED]
Palladion Software   Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFC7n5/+gerLs4ltQ4RAhIpAJ0Qi2QETxx/+QFVCHvlyTOsKcGvtACg0VK1
bE3pzHLOe6f9vmMir7VECMs=
=zoRB
-END PGP SIGNATURE-
___
Zope-CMF maillist  -  Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See http://collector.zope.org/CMF for bug reports and feature requests