[Framework-Team] Re: Let sleeping PLIPs lie...

Alec Mitchell apm13 at columbia.edu
Tue Aug 22 20:14:53 UTC 2006

On 8/22/06, Martin Aspeli <optilude at gmx.net> wrote:
> Hi,
> > http://plone.org/products/plone/roadmap/117 (AJAX dep)
> > http://plone.org/products/plone/roadmap/116 (AJAX dep)
> > http://plone.org/products/plone/roadmap/163 (AJAX dep)
> > http://plone.org/products/plone/roadmap/124 (AJAX dep)
> All of these are fairly obvious. There will naturally be tweaking and
> iterations of the implementation, but I think that these types of
> improvements can sometimes be done on trunk rather than in branches
> where they either would affect several other branches (e.g. a new widget
> that several new features may need) or where they are straightforward
> and/or easily reversible (e.g. a template change can be reverted without
> serious dependency breakage).
> Let's see what does come in time for the deadline, but if some of these
> don't, I'd be +1 to seeing them done afterwards *provided* that the beta
> and RC deadlines are taken seriously!
> Pragmatically speaking, as Limi points out, it's also a bit unfair to
> penalise these PLIPs when we haven't got the AJAX story sorted out yet.
> There is still too much uncertainty to start on any of these in earnest.
> > http://plone.org/products/plone/roadmap/175 (sleeper PLIP)
> This is a kind of meta-PLIP. Yes, we need more control panel pages. :)
> Having people add them a bit later in the day should be fairly low-risk
> though. It's only slapping a nicer UI on features we already have!
> > http://plone.org/products/plone/roadmap/126 (sleeper PLIP)
> Link type improvements would be nice to have, but needs a champion.
> > http://plone.org/products/plone/roadmap/132 (limi was wrong)
> I believe Florian was onto this as well (getIcon improvements). Again,
> it's not terribly controversial.
> > http://plone.org/products/plone/roadmap/176 (visual redesign pending)
> If this is too invasive, it may be a bit risky and impact a lot of other
> PLIPs. If the changes are relatively minor or gradual, they may be OK.
> This sounds like branch work, though. :)
> > A special one is:
> > http://plone.org/products/plone/roadmap/134 (too important to be
> > dropped, needs champion - also relatively easy to do)
> We need a champion for this, badly. It's an important feature, and I've
> seen a lot of users confused by the lack of editor/viewer local role
> management on the sharing page. It's also relatively straightforward, it
> just needs a person in charge. :-(

I would say that anything that doesn't have something valuable ready
by the PLIP review deadline should probably only be allowed in at the
sole discretion of the release manager.


More information about the Framework-Team mailing list