[Zope-dev] Plone, Grok, Zope 2, Zope 3, Repoze and the future
Hi, Just wanted to make you aware of two excellent articles written by Martin Aspeli about the future of Plone and how we want to move forward and what roles the underlying technologies play — new and old: 1. http://martinaspeli.net/articles/pete-and-andy-try-plone-4 2. http://martinaspeli.net/articles/is-plone-too-hard Should be read in order, since the first one informs and sets the stage for much of what is discussed in the second one. -- Alexander Limi · http://limi.net ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: pinning, nailing and kgs'ing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kevin Teague wrote: > I wanted to try using the snowsprint-viewlets2 branch of grok in my > project the other day. It took me a little time to figure out how to > do this, so I thought it'd be nice if there was a bit of documentation > on how-to pull in a development version of Grok into a grok project, > so I wrote this: > > http://grok.zope.org/documentation/how-to/trail-blazing > > (I've configured the Grok site to allow OpenId for authentication, and > granted the View and Reply to Item permissions to documentation that > is in the "Waiting for Review" state, which means you need to log-in > to see the document, but that anyone can log-in, which seems like a > decent compromise for unreviewed documentation on the Grok site which > is potentially incorrect.) > > The part where I was fuzzy in the documentation process was the > terminology for Known Good Sets. There are Grok releases such as "Grok > 0.11" which has been called "pinned versions" (or "nailed versions") > and when writting my help doc I've been calling this a "Known Good > Set". I would propose this definition for Known Good Set: > >Known Good Set : A frozen set of Python egg names and version > numbers that have been tested to work together. This set of eggs is > also available from an archive maintained by the publisher of the > known good set. > > For Grok this would be: > > http://grok.zope.org/releaseinfo/grok-0.11.cfg > > and the eggs are archived at: > > http://download.zope.org/distribution/ > > (at least that's my understanding of the Grok releases, maybe I don't > have that quite right ... ) You have one of the tow (disputed) definitions right (and I agree with you). > However, the Zope 3.4 release announcement varies a bit from my > understanding of Grok-centric understanding of Known Good Set: > > "The known good set -- or in short KGS -- is a package index that > derives from the official Python Package Index (PyPI) and thus > contains all available packages in the Python world. But for a > controlled set of packages, only certain versions that are known to > work together are available. " > > This is the part that seems a bit confusing to me, since it's not > clear if the "set" also includes the super-set of packages from PyPI. > It's also not clear if the super-set of all PyPI packages is also a > continually updated mirror, or a frozen index. Or is the known good > set just the controlled set of packages? Agreed: the'package index he refers to is a mirror of PyPI, with the exception that packages tracked by the KGS have those versions, rather than whatever is in PyPI. The rationale (which I disagree with) is that people want to use an index, but aren't willing to switch indexes when installing a package not tracked by the KGS. I have argued fairly strongly in the past that this is a bad idea, since there is no possiblity that the indexed packages are "known good". > It's also not entirely clear > on how maintenance releases happen with Zope 3.4 from this, e.g. one > could interpret the contents of the versions.cfg URL as either > "frozen" (Zope 3.4.0-final) or "latest". For maintenance releases > would there be: > > http://download.zope.org/zope3.4/versions.cfg I would argue that this page shouldn't exist yet, because 3.4 final has not yet been released. It shod be something like: http://download.zope.org/zope3.4.0c1/versions.cfg > http://download.zope.org/zope3.4.1/versions.cfg > http://download.zope.org/zope3.4.2/versions.cfg Those pages don't exist yet, because there are no releases later than 3.4.0. > Or if this URL will always contain the latest stable packages in the > 3.4 series then perhaps this should be more explicit with an URL such > as: > > http://download.zope.org/zope3.4/current-versions.cfg +1: if they represent a set which is changing over time, then they should be named in a way that represents that: otherwise, people may expect repeatable results when using the page. > Shouldn't there also be URLs such as these? > > http://download.zope.org/zope3.4/3.4.0c1-versions.cfg > http://download.zope.org/zope3.4/3.4.0-versions.cfg > http://download.zope.org/zope3.4/3.4.1-versions.cfg Something like that. ;) > It should also be more explicit what "controlled" means. It seems like > this is the same set of packages and versions and versions.cfg except > that it also contains versions of previous packages? Is this a > continually updated set of the most current versions of all packages > that make up the Zope 3.4 series after all test suites pass? > > http://download.zope.org/zope3.4/controlled-packages.cfg I don't nnow what that page means, exaclty. > Too me it seems easier to understand if there are two URLs in > buildout's find-links setting. e.g. for Plone there is a link to a > controlled archive of Plone produced packages, then there is a link to > P
Re: [Zope-dev] pinning, nailing and kgs'ing
On Feb 3, 2008, at 3:35 AM, Kevin Teague wrote: I wanted to try using the snowsprint-viewlets2 branch of grok in my project the other day. It took me a little time to figure out how to do this, so I thought it'd be nice if there was a bit of documentation on how-to pull in a development version of Grok into a grok project, so I wrote this: http://grok.zope.org/documentation/how-to/trail-blazing I couldn't access this page. The easiest way to use grok trunk/branch is to use svn:externals and change a few lines in buildout.cfg [buildout] develop = . src/grok src/grok/martian [versions] martian = and put this in svn:externals for src/ grok svn://svn.zope.org/repos/main/grok/branches/snowsprint-viewlets2 Anyways, I hope I don't sound too complain-y, but it would be much appreciated if the terminology and plan for maintaining the Zope 3.4 release series was made a bit clearer. And it would also be really nice if the Grok terminology and release methods lined up with the Zope 3 terminology and release methods :) Grok should use KGS. Someone just needs to do the work. /Tim ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 3.4.0 candidate 1 Released
On Fri, Feb 01, 2008 at 05:26:14PM -0500, Chris McDonough wrote: > Marius Gedminas wrote: >> On Fri, Feb 01, 2008 at 11:06:48AM -0500, Chris McDonough wrote: >>> I typed four more paragraphs full of markety stuff here but deleted them. >>> >> *cheers* > > I'll take that as STFU ;-) It wasn't intended that way. I know from personal experience how hard it is to suppress rants I've written. I was just applauding your self-control. Uhh, not that I'm implying your "markety stuff" was a rant. I'll shut up now. :-) Marius Gedminas -- Place mark here ->[ ]<- if you want a dirty monitor. signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: [Zope3-Users] Re: Zope 3.4.0 candidate 1 Released
On Sat, Feb 2, 2008 at 2:55 PM, Martin Aspeli <[EMAIL PROTECTED]> wrote: > Heh, I was joking. It's not a secret. It's just that we'd like to have > something to show before getting everyone all excited. I'll repeat my position on this that the best way forward for zope.org is to move all functionality out of zope org to microsites or otherwise. The collector is pretty much gone now, the wikies are on wiki.zope.org, and the next step would be to set up a new products.zope.org, with the Plone product software. A new site with new design and marketing talk could then replace www.zope.org. This sites main focus would just be to point people to the correct other sites. :) -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 6 OK
Summary of messages to the zope-tests list. Period Sat Feb 2 12:00:00 2008 UTC to Sun Feb 3 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Unit Tests. Tests passed OK --- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sat Feb 2 21:03:18 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009047.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sat Feb 2 21:04:49 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009048.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Feb 2 21:06:19 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009049.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Feb 2 21:07:49 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009050.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Feb 2 21:09:19 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009051.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Feb 2 21:10:50 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009052.html ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
