A new development model for Zope?
Hi everybody, I was just wondering if Zope could not get a better development model. I will explain briefly. Currently, Zope seems to have a model for major releases, in which bugs are corrected and features (possibly large features) are added in each new release. This model, IMHO, performs poorly on the stability and bug fixing side. My proposal is that Zope should go through a stable/development version, in a similar way to the linux-kernel. New heavy features should be only for the development Zope, whereas the stable Zope should receive only the bugfixes and the (micro) new features. This should be of major importance, because I would like to have Zope to increase stability on normal versions, without any further feature that I do not need. What do you think about it ? Paolo -- Paolo Bizzarri - Responsabile Marketing I3 Icube Srl Sede: Via Ridolfi 15 - 56124 Pisa (PI), Italia E-mail: p.bizzarri@icube.it WWW: www.icube.it Tel: (+39) 050 97 02 07 Fax: (+39) 050 31 36 588
Paolo Bizzarri wrote:
Hi everybody,
I was just wondering if Zope could not get a better development model. I will explain briefly.
Currently, Zope seems to have a model for major releases, in which bugs are corrected and features (possibly large features) are added in each new release. This model, IMHO, performs poorly on the stability and bug fixing side.
My proposal is that Zope should go through a stable/development version, in a similar way to the linux-kernel. New heavy features should be only for the development Zope, whereas the stable Zope should receive only the bugfixes and the (micro) new features. This should be of major importance, because I would like to have Zope to increase stability on normal versions, without any further feature that I do not need.
What do you think about it ?
I think we see this proposal about every three months on average. ;-) Personally, I would like to see a patch collector, for 'unofficial patches'. Kind of like the ac patches for linux (and now the aa and who knows who else is doing it now).
Hi Zopers,
My proposal is that Zope should go through a stable/development version, in a similar way to the linux-kernel. New heavy features should be only for the development Zope, whereas the stable Zope should receive only the bugfixes and the (micro) new features. This should be of major importance, because I would like to have Zope to increase stability on normal versions, without any further feature that I do not need.
What do you think about it ?
I think we see this proposal about every three months on average. ;-)
Well, perhaps I got my eyes too much closed... :=(
Personally, I would like to see a patch collector, for 'unofficial patches'. Kind of like the ac patches for linux (and now the aa and who knows who else is doing it now).
Exactly. For example, here two simple patches that should be collected and posted toward 2.1.6: - patch for renaming single objects (something I have seen in the new 2.2.0a version); - patch for the REQUEST object problem What do you think about it ? Ciao Paolo -- Paolo Bizzarri - Responsabile Marketing I3 Icube Srl Sede: Via Ridolfi 15 - 56124 Pisa (PI), Italia E-mail: p.bizzarri@icube.it WWW: www.icube.it Tel: (+39) 050 97 02 07 Fax: (+39) 050 31 36 588
Paolo Bizzarri wrote:
Hi Zopers,
My proposal is that Zope should go through a stable/development version, in a similar way to the linux-kernel. New heavy features should be only for the development Zope, whereas the stable Zope should receive only the bugfixes and the (micro) new features. This should be of major importance, because I would like to have Zope to increase stability on normal versions, without any further feature that I do not need.
What do you think about it ?
I think we see this proposal about every three months on average. ;-)
Well, perhaps I got my eyes too much closed... :=(
Fear not, I happen to like the proposal myself.
Personally, I would like to see a patch collector, for 'unofficial patches'. Kind of like the ac patches for linux (and now the aa and who knows who else is doing it now).
Exactly. For example, here two simple patches that should be collected and posted toward 2.1.6:
- patch for renaming single objects (something I have seen in the new 2.2.0a version);
- patch for the REQUEST object problem
What do you think about it ?
Well, unless anyone has any serious objections (or DC can pull it off soon), I can implement a site for this. On that note, I am now accepting suggestions and requests on it. ;-) Bill Anderson
Hi all, Don't know if this has been discussed before, but I am experiencing a weird problem with 'title' and 'title_or_id'; no matter what I specify as 'title' value, Zope returns 'Zope' (every page is titled 'Zope') Vanilla binary install of Zope 2.1.6, just started a new project. Any ideas? Thnx Jonathan
"Zope" is the name of the main folder so when you do <dtml-var title> you are getting that folder's title. <dtml-var title_or_id> will give you the title or id of the object that it is within (DTML Document title or id). That is probably what you want. J At 1:53 PM +0200 6/6/2000, Jonathan wrote:
Hi all,
Don't know if this has been discussed before, but I am experiencing a weird problem with 'title' and 'title_or_id'; no matter what I specify as 'title' value, Zope returns 'Zope' (every page is titled 'Zope')
Vanilla binary install of Zope 2.1.6, just started a new project. Any ideas?
Thnx Jonathan
"Zope" is the name of the main folder so when you do <dtml-var title> you are getting that folder's title.
<dtml-var title_or_id> will give you the title or id of the object that it is within (DTML Document title or id). That is probably what you want.
Well, that don't work either. And if I am correct; <dtml-var title_or_id> yields the same results as <!--var title_or_id--> right?
\> Well, that don't work either. And if I am correct; <dtml-var
title_or_id> yields the same results as <!--var title_or_id--> right?
Yeah. <!--var is the old <DTML-VAR When I create a document with these three things... <dtml-var title_or_id> = Which gives me the title of the document <dtml-var id> = which gives the id <dtml-var title> = which gives the title http://www.bwanazulia.com/testtest J
Jonathan wrote:
"Zope" is the name of the main folder so when you do <dtml-var title> you are getting that folder's title.
<dtml-var title_or_id> will give you the title or id of the object that it is within (DTML Document title or id). That is probably what you want.
Well, that don't work either. And if I am correct; <dtml-var title_or_id> yields the same results as <!--var title_or_id--> right?
Yes, that is correct. I think what you want is <dtml-var document_title> which should get you the title of the document whether it's a DTML Method or a DTML Document. -- Nick Garcia | ngarcia@codeit.com CodeIt Computing | http://codeit.com
participants (5)
-
Bill Anderson -
J. Atwood -
Jonathan -
Nick Garcia -
Paolo Bizzarri