Currently listing 522 projects with 1143 releases.

Le 31 déc. 06 à 15:10, Martin Aspeli a écrit :

> David Sapiro|Pilot Systems wrote:
>> Hi,
>>
>> Le 31 déc. 06 à 13:56, Martin Aspeli a écrit :
>>
>>> David Sapiro|Pilot Systems wrote:
>>>
>>>> BTW : the "tested with Plone X"
should be synchronized with the
>>>> current release of Plone. It can be in a
tool, or elsewhere, we  
>>>> agree
>>>> that 2.5 is an example, right?
>>> Yes, we obviously can't hard-code 2.5. In PHC
(plone.org/
>>> documentation)
>>> we have a field that lists the current version
as well as the  
>>> list of
>>> available versions.
>>>
>>> In PSC we only have "available"
versions. It may be a good idea to
>>> have
>>> another LinesField with a MultiSelectWidget
that uses as a  
>>> vocabulary
>>> the values in the "Versions" field
called "Currently supported
>>> versions". From there, you can select the
versions that we
>>> "require" and
>>> then we could use that for the listing of the
drop-down (note  
>>> that we
>>> still need to make it not-too-hard to find
products only tested with
>>> older versions). We should also only do this
for projects that  
>>> have a
>>> release in beta, rc or final states (imho).
>>>
>>> Alex - opinions on this?
>>>
>>> Now, PSC is currently undergoing a lot of
cleanup, moving a ton of
>>> display-related code out of content types and
into zope 3 views and
>>> adding unit tests very belatedly. We felt this
was necessary
>>> because we
>>> kept breaking PSC when making changes (the
code's grown very
>>> organically). Alex Clark is leading on this
work, I'm not quite
>>> sure how
>>> far along he is.
>>>
>>> To fix things quickly, we can do it on the 1.0
branch, which is what
>>> plone.org is running; we should then also merge
to trunk ASAP to  
>>> avoid
>>> the code going out of sync.
>>
>> So what is next step? I understand it's
complicated, and that a lot
>> of things are related. We wait for Alex? Hope he
has the time.
>
> I'd like Alex to agree that this is behaviour we want.
Unless he  
> objects
> or has better ideas I agree that it'd be useful. In
that case,  
> check out
> the 1.0 branch and dependencies and make the change
(add a field to  
> the
> schema, with the appropriate vocabulary and validation,
and modify the
> template so that it uses this as part of the search
results).
>
> Once it's done and tested (you can probably get a
download of
> plone.org/products to test on) merge the changes to
trunk so that we
> dont't lose them going forward, and update plone.org.

It will be done next week, unless specific instructions from
Alex or  
impossible things due to permissions, that we do experience
quite  
often in these situations.

Thanks for your time.

Dave





-- 
David Sapiro - davidpilotsystems.net
Pilot Systems - 9, rue Desargues - 75011 Paris
Tel : +33 1 44 53 05 55 - http://www.pilotsystems.n
et
Hébergement Zope et Plone gratuit - http://www.objectis.org



------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys -
and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Plone-website mailing list
Plone-websitelists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plone-web
site
The Wiki: http://plone.org/development/current/projects/WebsiteTe
am