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.co
Hanno Schlichting wrote:
> Wichert Akkerman wrote:
>> On 2/19/09 8:59 AM, Raphael Ritz wrote:
>>> 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 abl
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 opt
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 unico
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 n
David Glick wrote:
> 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
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 re
On Feb 18, 2009, at 11:20 PM, Wichert Akkerman wrote:
From what I can see most PLIPs should be simple to merge and have
little
or no conflicts with others, so I would like to ask everyone to merge
their own PLIP at their own time during the next two weeks. In order
to
keep things coordinat
