Previously Martin Aspeli wrote:
> Raphael Ritz <[EMAIL PROTECTED]> writes:
> > whit wrote:
> > Again, I propose Martin for this, if he is available.
> > Martin: would you be willing to do this?
>
> If there's one thing I do, it's yap on a lot. I'm happy to take on
> this role if people want me t
Previously Hanno Schlichting wrote:
> I wouldn't want to make the decision on whether or not we are dropping
> support for Zope 2.9 for Plone 3.0 but decide it based on the features
> we might get this way. If we have a PLIP that requires Zope 2.10, so be
> it ;)
Aren't the requirements more in ve
Previously Hanno Schlichting wrote:
> Don't support migrating to Plone 3 from versions earlier then Plone
> 2.1.0-final.
+1
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to m
Previously Hanno Schlichting said:
> 1. cubed / plone
> 2. plone / plone.app
> 3. plone / plone.cms
My vote:
cubed / plone: -1
plone / plone.app: +1
plone / plone.cms: +1
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http:
g, then
> i
> think we've lost a significant marketing and mindshare opportunity.
+1 to your -100
The consensus seems to be plone and plone.app? Martin, can you draft
something to communicate that to the folks?
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make t
ample".
Names containing dots are all the rage though :). I'm not sure if casing in
names survives all media and hosting services correctly.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.n
n't expect that people will produce
> stellar code in isolation without our guidance and encouragement. :)
>
> Martin
>
>
> _______
> Framework-Team mailing list
> Framework-Team@lists.plone.org
> http://lists.plone.org/mailman/listinfo/framework-
ch 12 we will
unleash Plone 3.0 unto the world.
Summarising
---
http://plone.org/products/plone/roadmap lists a lot of exciting proposals
and I know there are more good ideas floating around. If we can all pull
together to work on those we can make this one the best Plone release yet!
all pull
together to work on those we can make this one the best Plone release yet!
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Tea
Previously Martin Aspeli said:
> Wichert Akkerman wrote:
>> Hi guys,
>
> Looks good - just include a subject ;)
I'm restricted to using webmail at shell and that's all a bit awkward and
impractical.. That was actually the third attempt at sending it :(.
Thanks
uptools
>
> in particular, see
>
> http://peak.telecommunity.com/DevCenter/setuptools#development-mode
>
> Should you have any questions, please ask on the plone-developers list.
>
> Thanks!
>
> Martin & the rest of the Framework Team
>
>
> __
bit
odd. This makes me feel that perhaps the fwt should look for someone to
replace me. At least I'll withhold from voting in order to not have
conflicting roles.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It
viewing anyway. :)
You can setup an dummy bundle. That will get you the comment that the
plip has been submitted but is not ready for merging yet, giving you a
few weeks to get it all polished up.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.w
management on the sharing page. It's also relatively straightforward, it
> just needs a person in charge. :-(
Code-wide it should be fairly low impact though, so it can be developed
on a branch or on a seperate product and merged when we feel it's ready.
Wichert.
--
Wichert Akkerman <
Previously Martin Aspeli wrote:
> Wichert Akkerman wrote:
> >Previously Martin Aspeli wrote:
> >>>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.
e bastard, but only if
I really have to. I certainly do not have the illusion that I know more
and other people. I see the release manager role as mostly being about
making sure a good process is in place and being used. Most of the
required knowledge comes from community input.
Wichert.
--
W
haps we should
try to divide the work a bit so everyone reviews a few bundles and we'll
discuss the findings? And make sure people won't be reviewing their own
bundles :)
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/
eckout/staging
PLIP 179 - Improved commenting infrastructure
There are three plips (120, 124 and 149) which have a CMFPlone but no
bundle so I'm ignoring those.
121, 121 (both Bling) and 171 should be probably reviewed by the same
person and will warrant a lot of discussions - that's the blin
Previously Wichert Akkerman wrote:
> PLIP 8 - Versioning
> PLIP 112 - XML Import / Export
> PLIp 118 - Porlets engine basd on PlonePortlets and Viewlets
> PLIP 119 - Contextual help portlet
> PLIP 121 - Asynchronous loading of content views
> PLIP 122 - Edit-in-place mode for all
ou two weeks.
A reviewer will need to be be reasonably familiar with PAS plugins to be
able to review this I'm afraid.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to m
y to a certain extent) and then try to
> keep the KSS vs. Bling debate going in constructive direction.
>
> People happy with that?
+1
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/
6656.68 | F.+49.711.89665610 ]
> [ http://www.struktur.de | mailto:[EMAIL PROTECTED] ]
>
> ___
> Framework-Team mailing list
> Framework-Team@lists.plone.org
> http://lists.plone.org/mailman/listinfo/framework-team
--
Wiche
dency.
Considering the amount of problems users report who don't have PIL
installed and the fact image handling pretty much already requires it
(esp. with the current kupus offering resized images) perhaps making
PIL a hard dependency is worth it.
Wichert.
--
Wichert Akkerman <[EMAIL PROT
y risk: it will also remove a real
sanity-check that a member portrait is an actual image. Something which
is nicely exploited by the spam we've been seeing lately on plone sites.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://
packages of the various graphic
toolks you have installed.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing lis
configuration).
Using sessions means that ZEO clusters will not work out of the box: the
session storage is not shared between ZEO clients. This needs to be explicitly
documented in release notes.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wig
Previously Martin Aspeli wrote:
> Wichert Akkerman wrote:
> >Changes from stock Plone
> >
> >This bundle features two modifications from standard Plone:
> >
> > * adds the new SessionCrumbler product from collective
> > * Uses a modif
Is the session overhead a Zope-specific problem because of the
> implementation there, or is it something with using this approach
> inherently?
The Zope-specific bit is that the default Zope session setup does not (by
design) support Zeo clusters.
Wichert.
--
Wichert Akkerman <[EM
may also be interesting to see how hard it
will be to use those interfaces directly from sites that completely
replace the standard Plone templates.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to ma
bDAV locks (145 and 168).
> I've heard rumours PSOL just put iterate into production. Also, these
> are tough use cases, which seems to be Tesdal's speciality :)
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
Previously Raphael Ritz wrote:
> 2. Switch to using GS for AT at least internally now!
>
> Anyone up for 2?
Do we have a list of what is missing for that?
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/
illy.
> >
> >thus i don't think that the problem that martin mentions above
> >actually exists.
>
> Right - I may of course be totally wrong, which would be very good. :)
>
> In this case I'm less scared.
>
> I assume this applies to base and extensio
ongly feel the interfaces
need to be revisited. The interfaces from Ploneboard should be a good
basis here.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to ma
weeks away!
I'm thinking of posting a (expanded) version of this update to
plone-developers this weekend in order to keep everyone informed of our
status and get the message out there that people are actively working on
Plone 3.0. Any objections to that?
Wichert.
--
Wichert Akkerman &l
Previously Rocky Burt wrote:
> On Thu, 2006-14-09 at 19:29 +0200, Wichert Akkerman wrote:
> > I figured a quick status update might be useful. At this moment we have
> > four reviews in:
> >
> > PLIP 48 - session authentication
> > PLIP 121/122/171 - AZAX
d any feedback, and a delay this early in the
process is not a good sign for for the next couple of months.
If someone is not able to make the deadline please say so so we can try
to rearrange the workload.
Wichert.
Previously Wichert Akkerman wrote:
> I figured a quick status update might b
initial review the conclusions are not final: they can be
further discussed and bundle owners are encouraged to improve their
bundles based on the feedback.
Once the first bundles have been merged we will be releasing a first
alpha release of Plone 3.0.
Wichert.
--
Wichert Akkerman <[EMAIL PROTEC
ough a hierarchy is very impractical for that, and we need to support
storing comments in external systems like SQL which do not have a
concept of (folderish) types.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plo
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework-Team@lists.plone.or
#x27;t seen a review posted on the framework list though, that's why
I put it in this list.
> The other thing that's not here is the new workflows that Vincenzo said
> he'd look at. There's no bundle, but it's just a set of new workflows +
> possibly a control pan
Previously Alexander Limi wrote:
> On Wed, 04 Oct 2006 16:53:06 -0700, Wichert Akkerman
> <[EMAIL PROTECTED]> wrote:
>
> > PLIP 168 - integrate iterate for checkin/checkout/staging
> >
> > Viewing a locked front page gave an error until the page was checked
the global content menu
PLIP 148 - Move to CMF 2.1
if we can get releases for all relevant products during next week we
just might be able to release 3.0-alpha1 in about 10 days.
Wichert.
--
Wichert Akkerman
.
That means we have a deadline of October 15.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing lis
"from Products.CMFCore.TypesTool
> import ContentFactoryMetadata" produces an ImportError. There's not much
> we can do about it, other than taking the opportunity and converting it
> to an extension profile.
>
> What we fixed are the more common Archetypes helper func
ng from a non-voting member, to avoid anyone mis-counting.
>
> I would like to tally up the votes Friday and make an edict, unless
> anyone has strong objections.
At the moment my voting vote is:
-1 on Bling
+0 on Azax (I need to study it some more)
+0 on KSS (idem)
Wichert.
--
ere it fiddles
around with sys.modules to be usable outside of Products.
So here is my new vote:
-1 on Bling
+1 on Azax/KSS
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
_
install
them with a single easy_install command with automatic handling of
dependencies, etc.
This transition is going to take a while, and during that period we will
have a mix of both old-style Zope Products and new-style python
packages.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]
on in different
sizes? I can image that at some places in the UI you want to have a
large icon instead of a small one.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to make th
cally correct :)
I suspect that the people with the needed Five/Z3 knowledge already are
Zope committers :)
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
_
alpha
after that.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://list
hat.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.or
Is everyone on vacation? I was hoping for some response :)
W.
Previously Wichert Akkerman wrote:
> I just released 3.0-alpha1 unto the world. There are a number of
> known problems with this release: besides the bugs in the issue tracker
> there are a lot of failing unittests. As far
Are there any objections to merging the updated icon handling? The
changes are quite small and they bring us a lot more flexibility.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to make things
ces I can think of to use the @@plone_tools,
> @@context_state and @@portal_state views; obviously this would be an
> evolutionary thing, but I'd really rather get it in ASAP so people can
> start using it.
>
> Is this OK?
a definite +1
Wichert.
--
Wichert Akkerman <
Every python package will
have some dependency, and often dependencies are just implementation
details which can change over time.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
Previously Sidnei da Silva wrote:
> So we need to fix that. We can surely provide a 'stream' adapter for
> FileField. We should be able to change the transform API to make use
> of streams.
For 3.5 I'ld love to see a whole new transform infrastructure :)
Wichert.
--
ges. This is obviously less strong and requires a more
> direct dependency in CMFPlone.
>
> Given the amount of work (and tests!) that have gone into LinkIntegrity
> to date, and the fact that it does seem to work so well in the UI, I'd
> say we should keep the deeper integrati
t;
> 2.1 archetypes.kss: Tests that fail because of the event handling.
> (need to be fixed.)
>
> 2.2 There is another one in plone.app.kss,
> when the test view is declared but it's not picked up.
> (Needs to be fixed too.)
>
> --
> Balazs Ree
to endure come
> to my mind, like bots looking for insecure PHP apps on your domain (like
> awstats, phpmyadmin, ...). But probably you should filter those out in
> Apache or Squid in front of Plone anyways.
404 being slow has two problems: it is slow, and it is uncached which
makes it ext
Previously Martin Aspeli wrote:
> Wichert Akkerman wrote:
>
> >404 being slow has two problems: it is slow, and it is uncached which
> >makes it extra painful. Making it slower could be disastrous.
>
> It's merged now, but it's trivial to make changes to
>
I'll look later today), but that is no excuse
for breaking the 3.0 bundle.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Frame
cal
utility.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org
structure and UI in a single release. The infrastructure
changes are landing close to the merging deadlines and the UI is not
being done until after the infrastructure has landed. This means the UI
is being done too late and jeopardizes the release schedule.
Wichert.
--
Wichert Akkerman <[EM
t the people here can help
in trying to accomplish that.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
- End forwarded message -
--
Wichert Akkerman <[EMAIL PROTECTED]>
add it.
I just added the migration code and a test for it. What is still needed
is a test to see if the enable_sitemap property is being handled
correctly by the sitemap.xml.gz view.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www
With beta1 coming out soon I am wondering what the best moment would be
to branch off Plone 3.0 and open a new trunk. At the moment my
preference is to hold off until rc1 to make sure all attention stays
on 3.0. I would love some other opinions though.
Wichert.
--
Wichert Akkerman <[EM
sure if we should merge the new workflows, but
instead allow them to mature in an external package and reconsider them
for inclusion in 3.5.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to ma
Previously Alex Clark wrote:
> On Wed, Feb 28, 2007 at 12:27:18AM +0100, Wichert Akkerman wrote:
> > I have been looking at the new workflows in the CMFPlone
> > aclrak-ui-sprint-workflow-integration branch and I'm afraid they aren't
> > where they should be.
ecome a lot simpler and cleaner
and we need to find a way to keep the browser history updated so the
back button keeps working. We might be able to take some inspiration
from what gmail does. It is definitely a direction in which we should be
going.
Opinions? Thoughts?
Wichert.
--
Wichert Akk
Previously Hanno Schlichting wrote:
> Hi,
>
> Wichert Akkerman wrote:
> > Previously Alex Clark wrote:
> >> On Wed, Feb 28, 2007 at 12:27:18AM +0100, Wichert Akkerman wrote:
> >>> I have been looking at the new workflows in the CMFPlone
> >>> aclr
mped into the edit-mode.
Alex, can you give us a rational for the current behaviour? I think this
wants some discussion instead of a one-man decision.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://w
current hover
styling show a little popup which says 'shift-click to edit'.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Previously Wichert Akkerman wrote:
> Previously Martin Aspeli wrote:
> > I haven't tried the new behaviour yet, so I haven't made up my mind, but
> > there *was* discussion about this among the KSS people, Limi and others
> > nearby in Baarn. At the time, it so
uld handle that correctly.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework-Team@lists.plone.org
F group we just override in Plone.
Why not optimise this in Zope? That is where the bottleneck is.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
stpone the beta further, but the CMF changes
require some important change in our codebase that need to be finished.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard
ease
merge your list into that list so we have everything in a central place
all of us can access :)
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
__
e a good reason to
deprecate it, aside from the fact that CMF does and we do not want to
stray too far from their practices.
> >+100 and someone should blog or write a tutorial about these changes
> >and how to utilize them.
>
> Another +100
We need that for all changes, not
faces would be used outside of PlonePAS
specific PAS plugins, so that shouldn't be a problem.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
_
ot convinced that we have the problems that Thierry sees. I do see
that we have an increasing complexity and inter-dependencies between
components which will require some changes to the release process for
Plone 3.5 and later.
I also do not believe in electing leaders. Democracy works reasonably in
site admins are likely to need
>
> I'd suggest an "advanced" section in the control panel. I don't like the
> idea of moving this back to the ZMI because it's too complex for the typical
> user.
+1
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED
er-local
control panel: placeful workflow policies, content rules and type
restrictions. Workgroup systems like teamspace would also fit that
scheme very well.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard
ls bad to me. A 'advanced management'
permission which controls access to the advanced options feels nicer.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ I
we need to take it
out of the bundle and reconsider it for inclusion in Plone 3.5.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framew
Previously Alexander Limi wrote:
> Hi,
>
> Could we please remove PloneErrorReporting from Plone 3.0?
It's gone now.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard t
rial.
> - Search: "only in this section" checkbox
Needs to happen soon or becomes 3.5 material.
>
> - Fix in 3.0.x releases
> - Incremental KSS UI improvements, examples:
> - Login should be in-place (digg.com for an example)
> - Adding comment
Previously Alexander Limi wrote:
> On Tue, 03 Apr 2007 03:45:56 -0700, Wichert Akkerman
> >3.0.x minor are for bug and security fixes, not feature changes.
>
> So in 9 months, we can add comments without reloading the page, great...
Correct. That is the only way to do release
Previously Alexander Limi wrote:
> On Tue, 03 Apr 2007 03:30:52 -0700, Wichert Akkerman
> <[EMAIL PROTECTED]> wrote:
>
> >I'm wearing my release manager hat today and was looking at NuPlone. At
> >the moment there are still a lot things that do not work or lo
product that works and looks right on both
> >2.5 and 3.0.
> As soon as your customizations involve using the viewlets machinery,
> having a theme compatible with both Plone 2.5 and Plone 3.0 is impossible.
Or as soon as you touch main_te
un into the danger of coupling clients
> with the transforms at a lower level than the interface. Thus we lose real
> pluggability, because there's no exact specification and everyone can have
> their own interpretation of 'data' and 'kwargs'.
>
>
ore I make any decisions.
So... what do you think?
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Fra
ook for developers who
> want to work with Plone. See http://martinaspeli.net/plone-book
>
>
> ___
> Framework-Team mailing list
> Framework-Team@lists.plone.org
> http://lists.plone.org/mailman/listinfo/framework-team
--
Wichert Akkerman <[EMAIL PROT
in a mergeable state. That is not much, so you should be able
to enjoy some christmas vacation as well :)
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to make things
Previously Martin Aspeli wrote:
> Wichert Akkerman wrote:
> >Now that we have a new framework team it is time to start planning the
> >3.1 release. 3.1 is intended to be a low-risk upgrade which can follow
> >the 3.0 release quickly. The release cycle has to be short so we can
Previously Wichert Akkerman wrote:
> Now that we have a new framework team it is time to start planning the
> 3.1 release. 3.1 is intended to be a low-risk upgrade which can follow
> the 3.0 release quickly. The release cycle has to be short so we can
> get things out to people
miss in my last mail...
>
> >Maybe we could even indicate
> >an explicit time line for 3.2 right away as well?
>
> we would need to know/decide there will be a 3.2 first, imho :)
I want to do a 3.2.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to
goals of making 3.1 a simple, risk-free release with
only trivial migrations this timeline should be attainable.
Unless there are major objections I am going to make this official
tomorrow.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wig
.
--
Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/fra
Andreas Zeidler wrote:
On Nov 26, 2007, at 10:10 AM, Wichert Akkerman wrote:
Dear framework team,
I want to suggest PLIP 195 for inclusion in Plone 3.1. You can find the
full thing here: http://plone.org/products/plone/roadmap/195.
sounds great to me, esp after having to manually install
1 - 100 of 295 matches
Mail list logo
