Anounce the changes about fosckeditorbundle HOT 8 CLOSED

Announcing the change is not really on the TODO-list of the 1.0.0 release, as we should rather do it after the release.

from fosckeditorbundle.

At least it shouldn't block the relase, but is a task related :-)

from fosckeditorbundle.

I would propose the following plan

• RC time until May the 3rd
• engage ro test via Twitter and slack
• test in sonata and cmf
• release on evening of may 3rd
• publish anouncement blog posts at moening of may the 4rh
• force a Symfony Live speaker to add a block for us

from fosckeditorbundle.

How are you gonna force someone to add a block? Don't like that part, else is ok

from fosckeditorbundle.

Force is a maybe to hard. It is half a joke. But at least one or two speakers are friends of mine. An i would ask them, if they would add a note to talk to me to thier closing section.

Sure it won't be @fabpot it self, but maybe @derrabus.

At the end we do have a story from november until may the 4th and we should move 2.1 Mio. Downloads in several thausend apps to move to the new one.

from fosckeditorbundle.

At Symfony Live Phantasialand, I'm having a workshop with 25 attendees at most. I don't think that announcing anything there would be helpful for you. 😉

from fosckeditorbundle.

@javiereguiluz can i have a Symfony blog post slot for that? Would wtite a short anouncement sith backgound why in symfony blog. And a longer one in an own blog.

from fosckeditorbundle.

thanks all involved.

from fosckeditorbundle.