<div dir="ltr">ahh cool. I was just reading the docs and didn't notice any specifics about that.</div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Jan 25, 2015 at 11:42 PM, David Glick (Plone) <span dir="ltr"><<a href="mailto:david.glick@plone.org" target="_blank">david.glick@plone.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF" text="#000000"><span class="">
    <div>On 1/25/15 9:34 PM, Nathan Van Gheem
      wrote:<br>
    </div>
    <blockquote type="cite">
      <div dir="ltr"><br>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Sun, Jan 25, 2015 at 11:33 PM,
            David Glick (Plone) <span dir="ltr"><<a href="mailto:david.glick@plone.org" target="_blank">david.glick@plone.org</a>></span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On 1/25/15 9:24 PM, Nathan Van Gheem wrote:<br>
                <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                  Hi All,<br>
                  <br>
                  <br>
                  I'd like to merge plone.app.widgets into all of other
                  plone packages for plone 5.<br>
                  <br>
                  In doing so, I need to create some plone 4 only
                  branches for plone.app.dexterity and
                  plone.app.contenttypes.<br>
                  <br>
                  Any objections?<br>
                </blockquote>
                <br>
              </span>
              I don't really understand the benefit of spending effort
              to move the code. Is there an important reason I'm
              forgetting?</blockquote>
            <div>plone.app.widgets overrides things in other packages to
              work so it's a bit of indirection. I'd like to cut off
              plone.app.widgets and whoever wants to maintain it for
              plone 4 can if they care to.</div>
          </div>
        </div>
      </div>
    </blockquote>
    <br></span>
    Okay. I agree it would be ideal to avoid those overrides, although
    it maybe should be considered lower priority than fixing bugs in
    Plone 5.<br>
    <br>
    It looks like we already have branches for these packages -- Plone
    4.3 is using the 2.0.x branch of plone.app.dexterity and the 1.1.x
    branch of plone.app.contenttypes (at least according to sources.cfg
    in buildout.coredev).<span class=""><br>
    <blockquote type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div> <br>
            </div>
            <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>
                <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                  <br>
                  Also, what does everything think about Archetypes and
                  plone.app.widgets. Should that code be merged as well
                  or do we just start ignoring Archetypes in plone 5 a
                  bit?<br>
                  <br>
                </blockquote>
              </span>
              I think if we ignore Archetypes in Plone 5, it will
              significantly discourage users with custom AT content
              types from upgrading to Plone 5.<br>
            </blockquote>
            <div>Alright, we might need a branch for Archetypes also
              then :)</div>
            <div> </div>
          </div>
        </div>
      </div>
    </blockquote></span>
    Also already exists -- Plone 4.3 uses the 1.9.x branch of
    Products.Archetypes.<br>
  </div>

<br>_______________________________________________<br>
Framework-Team mailing list<br>
<a href="mailto:Framework-Team@lists.plone.org">Framework-Team@lists.plone.org</a><br>
<a href="https://lists.plone.org/mailman/listinfo/plone-framework-team" target="_blank">https://lists.plone.org/mailman/listinfo/plone-framework-team</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr">Nathan Van Gheem<div>Solutions Architect</div><div>Wildcard Corp</div></div></div>
</div>