Re: [Framework-Team] Plone 3.3 review: the final verdict

2009-02-15 Thread Raphael Ritz 

Andrew Burkhalter wrote:
Can someone refresh my memory as to who is responsible for the merging 
and by when?


As I understand it that's Wichert's job now as he is our
release manager. Whether he does all the merging by
himself or whether he'll ask authors for help is up to him.

Raphael



I see the following lists 2/14 as the final deadline on the schedule:
http://plone.org/support/forums/announcements#nabble-td1490066

Thanks!
Andrew

On Sun, Feb 15, 2009 at 12:42 PM, Raphael Ritz 
mailto:r.r...@biologie.hu-berlin.de>> 
wrote:



Summary of reviews for Plone 3.3 as of 2009-02-15
=


In short: all submitted PLIPs are ready for merging

That's really great and once more thanks to all who contributed!


Specifically, we were dealing with the following:


PLIP 126 - links redirect

 ready for merging


PLIP 197: Add FeedParser as external requirement instead of
shipping with it

 ready for merging


PLIP 232: Resource Registries Improvements

 ready for merging

 (Raphael notes: while we are missing one review I consider this
non-critical)


PLIP 234: Standardizing our use of INavigationRoot

 ready for merging

 (Raphael notes: there is still the wish to have more test)


PLIP 237: Minor i18n upgrades

 ready for merging


PLIP 238: Disable inline editing by default

 ready for merging


PLIP 239: Adapterise the Extensible Indexable Object Wrapper

 ready for merging


PLIP 240: Improve locking configurability

 ready for merging


PLIP 241: Clean up auto-sort: auto-order code

 ready for merging


PLIP 243: Replace workflow history viewlet with content history
viewlet

 ready for merging

 (Raphael notes: i18n support might need some love still but that's
  not considered a show stopper)


PLIP 246: View for rendering events as an iCalendar file

 ready for merging


PLIP 247: Automate ZCML Loading for Plone Plug-ins

 ready for merging



Links to further information can be found at

 http://dev.plone.org/plone/wiki/PLIPTallies33


For the Framework Team,

 Raphael





___
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

Re: [Framework-Team] Plone 3.3 review: the final verdict

2009-02-15 Thread Andrew Burkhalter 
Can someone refresh my memory as to who is responsible for the merging and
by when?  I see the following lists 2/14 as the final deadline on the
schedule:
http://plone.org/support/forums/announcements#nabble-td1490066

Thanks!
Andrew

On Sun, Feb 15, 2009 at 12:42 PM, Raphael Ritz  wrote:

>
> Summary of reviews for Plone 3.3 as of 2009-02-15
> =
>
>
> In short: all submitted PLIPs are ready for merging
>
> That's really great and once more thanks to all who contributed!
>
>
> Specifically, we were dealing with the following:
>
>
> PLIP 126 - links redirect
>
>  ready for merging
>
>
> PLIP 197: Add FeedParser as external requirement instead of shipping with
> it
>
>  ready for merging
>
>
> PLIP 232: Resource Registries Improvements
>
>  ready for merging
>
>  (Raphael notes: while we are missing one review I consider this
> non-critical)
>
>
> PLIP 234: Standardizing our use of INavigationRoot
>
>  ready for merging
>
>  (Raphael notes: there is still the wish to have more test)
>
>
> PLIP 237: Minor i18n upgrades
>
>  ready for merging
>
>
> PLIP 238: Disable inline editing by default
>
>  ready for merging
>
>
> PLIP 239: Adapterise the Extensible Indexable Object Wrapper
>
>  ready for merging
>
>
> PLIP 240: Improve locking configurability
>
>  ready for merging
>
>
> PLIP 241: Clean up auto-sort: auto-order code
>
>  ready for merging
>
>
> PLIP 243: Replace workflow history viewlet with content history viewlet
>
>  ready for merging
>
>  (Raphael notes: i18n support might need some love still but that's
>   not considered a show stopper)
>
>
> PLIP 246: View for rendering events as an iCalendar file
>
>  ready for merging
>
>
> PLIP 247: Automate ZCML Loading for Plone Plug-ins
>
>  ready for merging
>
>
>
> Links to further information can be found at
>
>  http://dev.plone.org/plone/wiki/PLIPTallies33
>
>
> For the Framework Team,
>
>  Raphael
>
>
>
>
>
> ___
> 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

Re: [Framework-Team] PLIP #247 ready for review (I think)

2009-02-15 Thread Israel Saeta Pérez 
On Sun, Jan 18, 2009 at 8:48 PM, Israel Saeta Pérez wrote:

> On Sat, Jan 17, 2009 at 2:37 AM, Ethan Jucovy wrote:
>
>>
>> Some of the things that people have said ought to be discussed about PLIP#
>> 247 are:
>>   1) impact on server startup time
>>   2) implications for test environments
>>   3) stabilizing and releasing a new version of z3c.autoinclude
>>   4) debugging tools/APIs for z3c.autoinclude
>> *  5) documentation and/or code generation templates to explain the entry
>> point for plugin authors*
>>
>> I'll begin working on #3 immediately, since there's plenty I can do there
>> while discussion is still happening.
>>
>> Please let me know if there's anything else I'll need to submit for the
>> PLIP's review.
>>
>
> I'm not a member of the Framework Team so this is not mandatory for the
> PLIP's review, but as a member of the Documentation Team I would
> appreciate number (5).
>
> Something like "Before, we did this to accomplish this task. Now, we can do
> that.", as Wichert (?) suggested, so we would be able to find and update
> affected docs easily.
>
> Thanks in advance!
>

The buildout manual has been updated (but updates are still private) to
reflect this new feature:

http://plone.org/documentation/tutorial/buildout/copy_of_creating-a-new-package

See the new "Automate ZCML loading for your package section".

I would appreciate any review input since I'm not sure I've got it right.
Thanks!

-- israel
Documentation Team
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team

[Framework-Team] Plone 3.3 review: the final verdict

2009-02-15 Thread Raphael Ritz 


Summary of reviews for Plone 3.3 as of 2009-02-15
=


In short: all submitted PLIPs are ready for merging

That's really great and once more thanks to all who contributed!


Specifically, we were dealing with the following:


PLIP 126 - links redirect

  ready for merging


PLIP 197: Add FeedParser as external requirement instead of shipping with it

  ready for merging


PLIP 232: Resource Registries Improvements

  ready for merging

  (Raphael notes: while we are missing one review I consider this 
non-critical)



PLIP 234: Standardizing our use of INavigationRoot

  ready for merging

  (Raphael notes: there is still the wish to have more test)


PLIP 237: Minor i18n upgrades

  ready for merging


PLIP 238: Disable inline editing by default

  ready for merging


PLIP 239: Adapterise the Extensible Indexable Object Wrapper

  ready for merging


PLIP 240: Improve locking configurability

  ready for merging


PLIP 241: Clean up auto-sort: auto-order code

  ready for merging


PLIP 243: Replace workflow history viewlet with content history viewlet

  ready for merging

  (Raphael notes: i18n support might need some love still but that's
   not considered a show stopper)


PLIP 246: View for rendering events as an iCalendar file

  ready for merging


PLIP 247: Automate ZCML Loading for Plone Plug-ins

  ready for merging



Links to further information can be found at

  http://dev.plone.org/plone/wiki/PLIPTallies33


For the Framework Team,

  Raphael





___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team

Re: [Framework-Team] PLIP #246 ready for review (pending review notes)

2009-02-15 Thread Raphael Ritz 

Graham Perrin wrote:

[..]

1. Please, for test purposes, can anyone provide a well populated  
folder of events?


2. If not Calendaring + p4a.plonecalendar then can we suggest any  
other route to .ics import?
  


Hi Graham,

thanks for testing this.

Please note that this PLIP isn't about importing events
from remote sites but about displaying events as ics feeds.

But I do indeed understand your wish to bulk import from
such files (this is the subject of the WebDAV plip BTW).

When I tested this I went through the effort of generating
a few events manually ...

Keep us updated on any further insights you may have.

Raphael


Thanks
Graham

References


 (expires mid-February 2010).

___
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