[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?