Re: Plone 4.3.4, please get your pulls in

Anthony Gerrard <[email protected]>
Newsgroups gmane.comp.web.zope.plone.devel
Message-ID <CAHA8JiRnk0pyPS15Wud8GptyGuA-V4oHmMP_G2fvtd5Y8N+axg@mail.gmail.com>
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 :)

------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
&#149; 3 signs your SCM is hindering your productivity
&#149; Requirements for releasing software faster
&#149; Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce

_______________________________________________
Plone-developers mailing list
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.