> +1. Plone 3 ships with NuPlone in the same way it does with CMFEditions > or any other package, we shouldn't change this in the 3.x series.
+1 Nothing should break on a 3.x upgrade unless we've thought it through carefully and intend to break it. On Mon, Jan 12, 2009 at 3:14 PM, Hanno Schlichting <hanno...@hannosch.eu> wrote: > Martin Aspeli wrote: >> Martin Aspeli wrote: >>> Hi, >>> >>> Why on earth is Products.NuPlone not in the Plone 3.2 egg? >>> >>> Is this in purpose or just a gross oversight? >> >> Ok, I've released Products.NuPlone 1.0b3. >> >> This one should be compatible with 3.2. You can use it straight away by >> adding Products.NuPlone to your eggs. >> >> The question now is how we deal with the release. We could: >> >> - Add Products.NuPlone as a dependency of the Plone egg. This would >> mean 'Plone' always comes with NuPlone, but there's no reason overt for >> the dependency. > > +1. Plone 3 ships with NuPlone in the same way it does with CMFEditions > or any other package, we shouldn't change this in the 3.x series. Please > introduce no special handling of it. > > Hanno > > > _______________________________________________ > Framework-Team mailing list > Framework-Team@lists.plone.org > http://lists.plone.org/mailman/listinfo/framework-team > -- Steve McMahon Reid-McMahon, LLC st...@reidmcmahon.com st...@dcn.org _______________________________________________ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
