Re: [Framework-Team] PLIP process in Trac for Plone 4 onwards

2009-04-02 Thread Alexander Limi
On Thu, Apr 2, 2009 at 5:39 PM, Sidnei da Silva
wrote:

> That sounds a lot like Blueprints in Launchpad. Just sayin! :)
>

Of course it does. :)
If we were using Launchpad for our issue tracking, we'd use the blueprints.
They are all the same, but it makes sense to track them in the same system
as you track the bugs/feature suggestions.

-- 
Alexander Limi · http://limi.net
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team


Re: [Framework-Team] PLIP process in Trac for Plone 4 onwards

2009-04-02 Thread Sidnei da Silva
On Thu, Apr 2, 2009 at 10:49 AM, Alexander Limi  wrote:
> Hi all,
>
> Just wanted to summarize how I think we'll using Trac for the PLIPs for
> Plone 4 onwards:
>
> - PLIPs are added as tickets with the "PLIP" type.
>
> - PLIPs show up in http://dev.plone.org/plone/report/24
>
> - If you propose for a particular release, you assign it to that release's
> milestone.
>
> - "Idea" PLIPs are put in the "Future" milestone.
>
> - That the ticket is "accepted" reflects FWT vote
>
> - When the ticket is "resolved", it means that it has been merged.
>
> I have added this to the description on the Trac report, let me know if
> anything should be added or changed.
>
> We probably want to add the state of the ticket to that report, so we can
> keep track of the resolved/accepted states.

That sounds a lot like Blueprints in Launchpad. Just sayin! :)

-- 
Sidnei da Silva
Canonical Ltd.
 Landscape · Changing the way you manage your systems
http://landscape.canonical.com

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


[Framework-Team] PLIP process in Trac for Plone 4 onwards

2009-04-02 Thread Alexander Limi

Hi all,

Just wanted to summarize how I think we'll using Trac for the PLIPs for  
Plone 4 onwards:


- PLIPs are added as tickets with the "PLIP" type.

- PLIPs show up in http://dev.plone.org/plone/report/24

- If you propose for a particular release, you assign it to that release's  
milestone.


- "Idea" PLIPs are put in the "Future" milestone.

- That the ticket is "accepted" reflects FWT vote

- When the ticket is "resolved", it means that it has been merged.

I have added this to the description on the Trac report, let me know if  
anything should be added or changed.


We probably want to add the state of the ticket to that report, so we can  
keep track of the resolved/accepted states.


--
Alexander Limi · http://limi.net


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


[Framework-Team] Re: [Plone-installers] [Plone-developers] Plone 3.3rc11 tagged and uploaded

2009-04-02 Thread Wichert Akkerman

On 4/2/09 9:42 AM, Vincent Fretin wrote:

Hi Wichert,

Can you release Products.CMFEditions 1.2? There is an i18n fix in it.
   


Can you port those changes to trunk first? I don't want to cut a release 
until all fixes have been merged to trunk to prevent future regressions.


Wichert.

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