Re: Plone 4.3.4, please get your pulls in
Luca Fabbri <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Message-ID | <CAGfGq=bBHwNfnvqms0oJHNb=sXFaZyQCEyqzRnmhaDh9hFvWYQ@mail.gmail.com> |
On Tue, May 6, 2014 at 1:57 PM, Anthony Gerrard <[email protected]> wrote: > On 6 May 2014 12:01, Luca Fabbri <[email protected]> wrote: >> >> On Tue, May 6, 2014 at 12:23 PM, Anthony Gerrard >> <[email protected]> wrote: >> > I have a customer with thousands of existing ATNewItems on a site. I'm >> > sure >> > we'll switch to Dexterity at some point but doing this piecemeal doesn't >> > feel like a good idea and doing the full switch to dexterity is not a >> > priority right now. >> > >> > My understanding is plone.app.blob is only used by Archetypes and there >> > already is code in p.a.contenttypes that assumes this change gets >> > merged. >> > >> > If the change can't go in Plone 4.3.x I don't see why we can't have a >> > plone.app.blob 1.6.x that goes into Plone 5. Surely we're not saying >> > all >> > Archetypes development must stop just because it's becoming optional in >> > Plone 5? >> > >> >> I see your point and I agree, but this is still a deep change. >> >> So I've another idea: why not simply merge a part of the pull request? >> We can give to users no upgrade step but only the migration view. So >> only users who really want will be able to migrate to blobbed news. >> >> What you think? > > > Yes agree - that's actually what I suggested a few emails ago :) Ops! :) -- -- luca twitter: http://twitter.com/keul linkedin: http://linkedin.com/in/lucafbb blog: http://blog.keul.it/ ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce