[Framework-Team] Re: Plone 3.3 PLIP merges
Andrew Burkhalter, on 2009-02-27: PLIP 126 is now merged and the review bundle archived. I've tried to be as comprehensive as possible here, but I hope any mistakes I've made will be pointed out. Tasks that I believe need to be done from here are: - Need new release of plone.app.controlpanel (looks like wichert, hannosch, or optilude need to do this) - Need new release of plone.app.portlets (looks like this is either wichert or optilude) A new release of plone.app.portlets is also needed for plip 197 that I just merged. - Possibly changes to versions.cfg and etc/versions with plonenext/branches/3.3, I didn't take the time to figure out what was needed. It looks like nothing is needed here at this point. - Relevant merging to trunk I'd say you can do this now. Am I on the right track here? Looks like it to me, but plip 197 is the first plip I did, so I'm no expert. :) Thanks! Andrew And thank you for creating a new plone.app.portlets branch so I did not need to do that for my plip. :) Cheers, -- Maurits van Rees | http://maurits.vanrees.org/ Work | http://zestsoftware.nl/ This is your day, don't let them take it away. [Barlow Girl] ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Re: Plone 3.3 PLIP merges
PLIP 126 is now merged and the review bundle archived. I've tried to be as comprehensive as possible here, but I hope any mistakes I've made will be pointed out. Tasks that I believe need to be done from here are: - Need new release of plone.app.controlpanel (looks like wichert, hannosch, or optilude need to do this) - Need new release of plone.app.portlets (looks like this is either wichert or optilude) - Possibly changes to versions.cfg and etc/versions with plonenext/branches/3.3, I didn't take the time to figure out what was needed. - Relevant merging to trunk Am I on the right track here? Thanks! Andrew On Fri, Feb 20, 2009 at 9:45 AM, Hanno Schlichting hanno...@hannosch.euwrote: Wichert Akkerman wrote: In prepraration for the merges I have created a 3.3 plonenext branch; please use that to merge your work and test the results. Hanno Schlichting - PLIP 237: Minor i18n upgrades PLIP 237 is merged. New releases of PLT and PTS are made and plonenext is updated with new versions and branch locations. Finally I updated the PLIP page on plone.org (http://plone.org/products/plone/roadmap/237) and included the documentation I wrote for the review bundle. PLIP status was moved the Merged :) Hanno ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Re: Plone 3.3 PLIP merges
Wichert Akkerman wrote: In prepraration for the merges I have created a 3.3 plonenext branch; please use that to merge your work and test the results. Hanno Schlichting - PLIP 237: Minor i18n upgrades PLIP 237 is merged. New releases of PLT and PTS are made and plonenext is updated with new versions and branch locations. Finally I updated the PLIP page on plone.org (http://plone.org/products/plone/roadmap/237) and included the documentation I wrote for the review bundle. PLIP status was moved the Merged :) Hanno ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Re: Plone 3.3 PLIP merges
Wichert Akkerman wrote: On 2/19/09 8:59 AM, Raphael Ritz wrote: Wichert Akkerman wrote: Now that the final reviews are in it's time to start merging. I disagree with the framework team results on one item: PLIP 243 is not ready for merging. It still suffers from a problematic unicode decore error that I have not been able to fix, and which must be solved before it can be merged. (shameless request: I need help with that one! Sorry for not catching that one :-( Can you give more details maybe? I don't see anything reported on http://dev.plone.org/plone/browser/review/plip243-content-history/README.txt#25 I tried to look into this, but I wasn't able to provoke any error or see any obvious place where one could occur. Can you give me some concrete steps to follow to provoke the error? Hanno ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Re: Plone 3.3 PLIP merges
On Feb 19, 2009, at 1:42 AM, Martin Aspeli wrote: When merging keep in mind that you should not modify any branches that are used by Plone 3.2 (or older versions). That might mean you will have to create a new maintenance branch for Plone 3.x and update plonenext 3.2 and plone-coredev. We really ought to have some kind of map/script to tell us which branches are used by which versions. This is already part of plonenext. See http://svn.plone.org/svn/plone/plonenext/3.2/etc/sources for 3.2 and http://svn.plone.org/svn/plone/plonenext/3.3/etc/sources for 3.3 Hanno, any advice on forward-porting changes that are not compatible with Plone trunk? e.g. the locking stuff in PLIP 240 which uses some KSS for supporting inline editing (I suppose the correct answer is to create a new branch of the package for Plone trunk and omit the parts that are no longer relevant) David Glick Web Developer ONE/Northwest New tools and strategies for engaging people in protecting the environment http://www.onenw.org davidgl...@onenw.org work: (206) 286-1235 x32 mobile: (206) 679-3833 Subscribe to ONEList, our email newsletter! Practical advice for effective online engagement http://www.onenw.org/full_signup ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
