[kupu-dev] Upcoming Plone release and Kupu changes

[Duncan Booth]

Ed Manlove <devPyPlTw at verizon.net> wrote:

>>> I'm trying to understand the package release of Plone with Kupu. I
>>> am correct in saying that changes to Products.kupu under the Plone
>>> 3.2 branch will be part of the Plone release?
>>> 
>>> I known this sounds like a Plone question but I am trying to
>>> understand what constitutes a Kupu package as compared to what is a
>>> Plone package? and how they may interrelate?
>>> 
>> I generate new releases of Kupu before each release of Plone when
>> there have been changes made. Until recently that has meant uploading
>> a tgz file to plone.org but with Plone 3.2 it means also creating a
>> new kupu egg. The egg is packaged differently but the actual kupu
>> files are the same in both cases.
>> 
>> If you have an older version of Plone then you may upgrade it to use
>> a newer kupu: so far kupu has remained compatible with all versions
>> of Plone from 2.1ish through to 3.2 (although there may be a few
>> other product dependencies if you use a really old Plone).
>> 
>> Does that help any?
> 
> Duncan,
> 
> Yes.  I'm working on closing out several RTL bugs under Plone before
> the next Plone release.  One I would like to fix #7177 depends upon
> patching the precedence of Kupu stylesheets in relation to RTL.css, 
> http://dev.plone.org/plone/ticket/8570.  #8570 in turns depended upon 
> #8505 which I've fixed under Plone 3.2 branch and closed.
> 
> Basically if I patched NuPlone stylesheet ordering (#7177) but not 
> Kupu's stylesheet ordering(#8570), Kupu stylying under the NuPLone
> theme would break.  Thus I wanted to make sure the issues were fixed
> in order and that under the upcoming release all patches were applied
> leaving no one part broken.
> 
> As I fixed #8505 would it be alright to add the patches for Kupu
> (#8570)? 
> 
So long as the fixes don't break older versions of Plone just go ahead.