CMF 1.2

[Lukas Kahwe Smith]

Aloha,

I realize we currently do not have all that much lined up for 1.2 but it would be good to get inline again with our release plan of following closely with Symfony major and minor releases.

What I currently see for 1.2:
- PHPCR ODM 1.2 (end flush, fixes for multiple flushes, a few other bug fixes)
- RoutingAutoBundle stable 1.0
- PSR-4
- MediaBundle depending on LiipImagineBundle 1.0
- Initializer tweaks
- .. ?

Nice to haves:
- Testing component with ORM support
- .. ?

Originally I dreamed (http://cmf.symfony.com/news/1-1-stable-release) that we would also finally offer a smarter solution for the MenuBundle that would no longer always read the entire menu tree but nobody has been working on this ..

regards,
Lukas Kahwe Smith
sm...@pooteeweet.org

[Ben Glassman]

Media bundle's liip imagine integration is broken in general right now mostly due to some code that repeatedly adds cdn path prefixes to paths returned by liip (which should not be modified). I can try to get a PR together to get this fixed. The media bundle phpcr integration is also completely broken right now but I have a few PRs in which should fix this.

Regarding speeding up the menu bundle I seem to recall some discussions about possibly caching the transformation of phpcr nodes to menu nodes but I don't know if there were any other details discussed? This would be somewhat problematic potentially because of the events we added that are fired during creation but as long as they were fired once at the beginning of generation then we would just be caching the final menu node tree. I dont see any functionality in the knp menu bundle for caching but it seems like this is a fairly generic piece of functionality we are talking about that  would be good to add to the knp menu however development of that package seems somewhat stalled at this point. Really there are a number of things that will need to be updated once the knp menu 2.0 officially is released but its unclear when that will be. 

[dan...@dantleech.com]

On 2014-06-23 20:55, Lukas Kahwe Smith wrote:
> Aloha,
>
> I realize we currently do not have all that much lined up for 1.2 but
> it would be good to get inline again with our release plan of
> following closely with Symfony major and minor releases.
>
> What I currently see for 1.2:
> - PHPCR ODM 1.2 (end flush, fixes for multiple flushes, a few other
> bug fixes)
> - RoutingAutoBundle stable 1.0
> - PSR-4
> - MediaBundle depending on LiipImagineBundle 1.0
> - Initializer tweaks
> - .. ?
>
> Nice to haves:
> - Testing component with ORM support
> - .. ?

For our talks at the PHP Summercamp in September I suggested that, for
the CMF talk,
we might do an ORM version of Creating a Basic CMS with
RoutingAutoBundle. So I would
like to possibly try and implement stable ORM support for Routing,
MenuBundle and RoutingAutoBundle.

[Wouter de Jong]

- Testing component with ORM support

Testing component already provides fully ORM support.

I would really love to see ORM support for all CMF Key Bundles. I think the biggest block for people to *not* use the CMF is it's limited storage support.

Furthermore, I would like to add "Integrating JMSmetadata into the SeoBundle" to the nice to have list.

--
You received this message because you are subscribed to the Google Groups "symfony-cmf-devs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to symfony-cmf-devs+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[David Buchmann]

> For our talks at the PHP Summercamp in September I suggested that, for
> the CMF talk,
> we might do an ORM version of Creating a Basic CMS with
> RoutingAutoBundle. So I would
> like to possibly try and implement stable ORM support for Routing,
> MenuBundle and RoutingAutoBundle.

imho the most interesting bundle for orm support would be
SimpleCmsBundle. having less of the referencing back and forth, it
should be easier and would allow a minimal drop-in cms bundle with orm
storage.

but either way, this can also happen on the next release - september
sounds too late for me for 1.2. getting phpcr-odm and routing auto
stable should happen sooner, and then finally the symfony tutorial will
work as advertised... 1.3 can come in october or so i guess.

[David Buchmann]

> Media bundle's liip imagine integration is broken in general right now
> mostly due to some code that repeatedly adds cdn path prefixes to paths
> returned by liip (which should not be modified). I can try to get a PR
> together to get this fixed. The media bundle phpcr integration is also
> completely broken right now but I have a few PRs in which should fix this.

hm, is it broken when using the 1.0 version of LiipImagineBundle or even
for 0.9 versions?

either way, glad if you can fix things. if the currently allowed setup
is broken we probably need better tests as tests are green.

> Regarding speeding up the menu bundle I seem to recall some discussions
> about possibly caching the transformation of phpcr nodes to menu nodes
> but I don't know if there were any other details discussed? This would
> be somewhat problematic potentially because of the events we added that
> are fired during creation but as long as they were fired once at the
> beginning of generation then we would just be caching the final menu
> node tree. I dont see any functionality in the knp menu bundle for
> caching but it seems like this is a fairly generic piece of
> functionality we are talking about that would be good to add to the knp
> menu however development of that package seems somewhat stalled at this
> point. Really there are a number of things that will need to be updated
> once the knp menu 2.0 officially is released but its unclear when that
> will be.

my idea would be to cache the menu *nodes*. the events happen on
conversion from menu node to menu item. this is also when the "current"
item is determined. so the only tricky part is how to store the whole
node tree, as it will have phpcr-odm proxy elements that probably can't
load data anymore after being reawoken from caching. maybe we can make
walk the tree on the first caching and ensure they are all loaded and
detach them from phpcr-odm, and only then cache them.

[Ben Glassman]

I should clarify that it is the liip imagine and sonata media bundle that I believe is broken

--
You received this message because you are subscribed to the Google Groups "symfony-cmf-devs" group.

To unsubscribe from this group and stop receiving emails from it, send an email to symfony-cmf-de...@googlegroups.com.

[Lukas Kahwe Smith]

On 23 Jun 2014, at 22:54, Wouter de Jong <jong.de...@gmail.com> wrote:

> - Testing component with ORM support
>
> Testing component already provides fully ORM support.
>
> I would really love to see ORM support for all CMF Key Bundles. I think the biggest block for people to *not* use the CMF is it's limited storage support.
>
> Furthermore, I would like to add "Integrating JMSmetadata into the SeoBundle" to the nice to have list.

OK .. my goal would be to release no later than end of July .. ideally mid July. Could be tight .. but worst case they get merged to master right after 1.2 ..

[David Buchmann]

another topic: we currently do not test symfony 2.5 with our bundles. we
test dev-master and allow failures on it. we should add 2.5 to the
symfony versions we test. and switch from the matrix to something like
https://github.com/FriendsOfSymfony/FOSHttpCacheBundle/blob/master/.travis.yml

if the PR builds are green, its all good. but if not, we need to
investigate. doing the PR with the build matrix should be a real easy
pick, if somebody wants to help out a bit.

cheers,david

--
Liip AG // Agile Web Development // T +41 26 422 25 11
CH-1700 Fribourg // PGP 0xA581808B // www.liip.ch

[Wouter de Jong]

if the PR builds are green, its all good. but if not, we need to
investigate. doing the PR with the build matrix should be a real easy
pick, if somebody wants to help out a bit.

I'll start with it

[Lukas Kahwe Smith]

On 24 Jun 2014, at 19:05, Wouter de Jong <jong.de...@gmail.com> wrote:

> On 23.06.2014 20:55, Lukas Kahwe Smith wrote:
> > Aloha,
> >
> > I realize we currently do not have all that much lined up for 1.2 but it would be good to get inline again with our release plan of following closely with Symfony major and minor releases.
> >
> > What I currently see for 1.2:
> > - PHPCR ODM 1.2 (end flush, fixes for multiple flushes, a few other bug fixes)

we are quite far along here.

> > - RoutingAutoBundle stable 1.0

how close are we here?

> > - PSR-4

this was done .. ?

> > - MediaBundle depending on LiipImagineBundle 1.0

still open

https://github.com/symfony-cmf/MediaBundle/pull/106

> > - Initializer tweaks

https://github.com/symfony-cmf/RoutingBundle/pull/251

> > Nice to haves:
> > - Testing component with ORM support

https://github.com/symfony-cmf/Testing/pull/53

> > Originally I dreamed (http://cmf.symfony.com/news/1-1-stable-release) that we would also finally offer a smarter solution for the MenuBundle that would no longer always read the entire menu tree but nobody has been working on this ..

nothing seems to have happened there ..

—

beyond that the following have been mentioned

- update .travis.yml files to include 2.6 (and hhvm)

- implement ORM support for SimpleCmsBundle (and related Bundles)

—

I would really like to start soon with the RC process for PHPCR ODM and then try and release CMF 1.2 in august.

Wdyt?

[Daniel Leech]

On 21/07/14 14:10, Lukas Kahwe Smith wrote:
> On 24 Jun 2014, at 19:05, Wouter de Jong <jong.de...@gmail.com> wrote:
>
>> On 23.06.2014 20:55, Lukas Kahwe Smith wrote:
>>> Aloha,
>>>
>>> I realize we currently do not have all that much lined up for 1.2 but it would be good to get inline again with our release plan of following closely with Symfony major and minor releases.
>>>
>>> What I currently see for 1.2:
>>> - PHPCR ODM 1.2 (end flush, fixes for multiple flushes, a few other bug fixes)
> we are quite far along here.
>
>>> - RoutingAutoBundle stable 1.0
> how close are we here?

Very close, there are pending PRs for additional features, but the core
functionality equivilent to the original version and more. There are PRs
for all the docs - but I would still be reluctant to call it stable
at this stage - its a complicated bundle and it needs alot of testing to
deserve a "stable" tag.

Maybe it would be better to move it to beta with the 1.2 release, after
which it will have stable dependencies and so should be usable in the
mainstream.

[Lukas Kahwe Smith]

On 21 Jul 2014, at 14:42, Daniel Leech <dan...@dantleech.com> wrote:

>
> On 21/07/14 14:10, Lukas Kahwe Smith wrote:
>> On 24 Jun 2014, at 19:05, Wouter de Jong <jong.de...@gmail.com> wrote:
>>
>>> On 23.06.2014 20:55, Lukas Kahwe Smith wrote:
>>>> Aloha,
>>>>
>>>> I realize we currently do not have all that much lined up for 1.2 but it would be good to get inline again with our release plan of following closely with Symfony major and minor releases.
>>>>
>>>> What I currently see for 1.2:
>>>> - PHPCR ODM 1.2 (end flush, fixes for multiple flushes, a few other bug fixes)
>> we are quite far along here.
>>
>>>> - RoutingAutoBundle stable 1.0
>> how close are we here?
>
> Very close, there are pending PRs for additional features, but the core functionality equivilent to the original version and more. There are PRs for all the docs - but I would still be reluctant to call it stable
> at this stage - its a complicated bundle and it needs alot of testing to deserve a "stable" tag.
>
> Maybe it would be better to move it to beta with the 1.2 release, after which it will have stable dependencies and so should be usable in the mainstream.

well right now we have a serious issue with our documentation due to the state of RoutingAutoBundle. getting it to beta will somewhat solve this issue. But imho we should focus on making it stable and not in additional features. Of course finding edge cases takes time, during which one can work on features .. but those might introduce edge cases again. In the end .. if we realize that some important feature requires breaking BC, I much rather just have a 2.x release .. so in other words .. I would prioritize getting to stable ASAP over anything else.

[Wouter de Jong]

> > - RoutingAutoBundle stable 1.0

how close are we here?

This is mostly waiting on Doctrine 1.2. Apart from that:

Blockers: https://github.com/symfony-cmf/RoutingAutoBundle/issues/109, https://github.com/symfony-cmf/RoutingAutoBundle/issues/91, https://github.com/symfony-cmf/RoutingAuto/pull/5, https://github.com/symfony-cmf/RoutingAutoBundle/issues/90

Nice to haves: https://github.com/symfony-cmf/RoutingAutoBundle/issues/82

And it needs testing, a lot.

 

> > - PSR-4

this was done .. ?

Yes

 > > - Testing component with ORM support

 

https://github.com/symfony-cmf/Testing/pull/53

I'm going to test that tomorrow and merge if everything went fine. After that, Testing should support ORM just as it supports PHPCR.

- update .travis.yml files to include 2.6 (and hhvm)

I'm currently working on this. I'm adding 2.5 as a requirement to support and 2.6 as an allowed failure. I'll add hhvm too as an allowed failure, ok?

- implement ORM support for SimpleCmsBundle (and related Bundles)

That's a really big task to do in a couple of weeks :) 

[Lukas Kahwe Smith]

On 21 Jul 2014, at 14:50, Wouter de Jong <jong.de...@gmail.com> wrote:

> > > - RoutingAutoBundle stable 1.0
>
> how close are we here?
>
> This is mostly waiting on Doctrine 1.2. Apart from that:
>
> Blockers: https://github.com/symfony-cmf/RoutingAutoBundle/issues/109, https://github.com/symfony-cmf/RoutingAutoBundle/issues/91, https://github.com/symfony-cmf/RoutingAuto/pull/5, https://github.com/symfony-cmf/RoutingAutoBundle/issues/90
> Nice to haves: https://github.com/symfony-cmf/RoutingAutoBundle/issues/82
>
> And it needs testing, a lot.

ok thx

> > > - Testing component with ORM support
>
> https://github.com/symfony-cmf/Testing/pull/53
>
> I'm going to test that tomorrow and merge if everything went fine. After that, Testing should support ORM just as it supports PHPCR.

great!

> - update .travis.yml files to include 2.6 (and hhvm)
>
> I'm currently working on this. I'm adding 2.5 as a requirement to support and 2.6 as an allowed failure. I'll add hhvm too as an allowed failure, ok?

yeah

> - implement ORM support for SimpleCmsBundle (and related Bundles)
>
> That's a really big task to do in a couple of weeks :)

Yeah, does not seem to be realistic for 1.2

[David Buchmann]

>> - update .travis.yml files to include 2.6 (and hhvm)
>>
>> I'm currently working on this. I'm adding 2.5 as a requirement to support and 2.6 as an allowed failure. I'll add hhvm too as an allowed failure, ok?

hhvm is fundamentally blocked by jackalope having an issue with it
https://github.com/jackalope/jackalope/issues/232

unless somebody wants to pick this up very soon, it seems not realistic
for 1.2

>> - implement ORM support for SimpleCmsBundle (and related Bundles)
>>
>> That's a really big task to do in a couple of weeks :)
>
> Yeah, does not seem to be realistic for 1.2

sad but true.

cheers,david

[Lukas Smith]

On 22 Jul 2014, at 09:49, David Buchmann <da...@liip.ch> wrote:

>>> - update .travis.yml files to include 2.6 (and hhvm)
>>>
>>> I'm currently working on this. I'm adding 2.5 as a requirement to support and 2.6 as an allowed failure. I'll add hhvm too as an allowed failure, ok?
>
> hhvm is fundamentally blocked by jackalope having an issue with it
> https://github.com/jackalope/jackalope/issues/232
>
> unless somebody wants to pick this up very soon, it seems not realistic
> for 1.2

Jackalope with Jackrabbit and Doctrine DBAL actually work in the PHPCR benchmark suite I created. I think the issues are mostly with how we do fixture loading there .. and likely a few other issues too .. but its not "fundamentally" broken.

regards,
Lukas

[jong.de...@gmail.com]

>>>> - update .travis.yml files to include 2.6 (and hhvm)
>>>>
>>>> I'm currently working on this. I'm adding 2.5 as a requirement to support and 2.6 as an allowed failure. I'll add hhvm too as an allowed failure, ok?
>>
>> hhvm is fundamentally blocked by jackalope having an issue with it
>> https://github.com/jackalope/jackalope/issues/232
>>
>> unless somebody wants to pick this up very soon, it seems not realistic
>> for 1.2

> Jackalope with Jackrabbit and Doctrine DBAL actually work in the PHPCR benchmark suite I created. I think the issues are mostly with how we do fixture loading there .. and likely a few other issues too .. but its not "fundamentally" broken.

We can always add it as an allowed failure and see what happends. I don’t think we should make it a requirement for 1.2

[David Buchmann]

> Jackalope with Jackrabbit and Doctrine DBAL actually work in the PHPCR benchmark suite I created. I think the issues are mostly with how we do fixture loading there .. and likely a few other issues too .. but its not "fundamentally" broken.

ah, indeed. that is promising. then we really should make an effort to
get this working. would be really cool if we can say that jackalope and
the cmf work on hhvm.

if somebody feels like digging into this, please tell so. otherwise i
can try to find time. if you have any inputs lukas, please note them on
the ticket. from the nature of the failure i don't get why the benchmark
worked - unless hhvm was fixed or you don't use the broken features.

[Lukas Kahwe Smith]

On 21 Jul 2014, at 14:50, Wouter de Jong <jong.de...@gmail.com> wrote:

> > > - RoutingAutoBundle stable 1.0
>
> how close are we here?
>
> This is mostly waiting on Doctrine 1.2. Apart from that:

FYI https://github.com/doctrine/phpcr-odm/releases/tag/1.2.0-RC1

[Lukas Kahwe Smith]

On 24 Jul 2014, at 16:16, Lukas Kahwe Smith <sm...@pooteeweet.org> wrote:

> This is mostly waiting on Doctrine 1.2. Apart from that:
>
> FYI https://github.com/doctrine/phpcr-odm/releases/tag/1.2.0-RC1

There are still a few Event related tickets open but nothing that will stop a 1.2.0 even if they do not get fixed.

Aside from this we are seeing a bunch of smaller issues getting fixed, but also lots of small tickets opening and unfinished PRs.
I think we should push to set a release date and this hopefully will entice people to focus a bit more on wrapping things up :)

I therefore propose to go to RC1 on August 19th.
So the plan would be to release an RC1 of all Bundles, Components and Apps on that date.

FYI, David will be off for a month starting on the 23rd.

Again to me the main thing I would love to see get done until then is RoutingAutoBundle.

[Daniel Leech]

Big +1 :)

That will also conincide nicely with our workshop at the eZSummerCamp,
where the RoutingAutoBundle
will play a big role.

Although, I don't think we could call RoutingAuto "stable" until it has
been out in the wild for some time. So
I would prefer to leave it at 1.0-beta but after the 1.2 release it will
have stable dependencies so we can
effectively "release" it.

[David Buchmann]

> That will also conincide nicely with our workshop at the eZSummerCamp,
> where the RoutingAutoBundle
> will play a big role.

good. too bad i had to pass on that summer camp, hope i can make it next
year.

> Although, I don't think we could call RoutingAuto "stable" until it has
> been out in the wild for some time. So
> I would prefer to leave it at 1.0-beta but after the 1.2 release it will
> have stable dependencies so we can
> effectively "release" it.

we always need to sync the releases of dependant bundles to have a way
that bundles needing other newest components get a stable dependency, so
once we released the phpcr-odm and core bundle or routing bundle and
all, routing auto should run on stable dependencies.

at that point i would tag it 1.0.0 - its a 1.0 release and its normal
that things might need cleanup afterwards. we had that for most of the
cmf bundles. but it gives a clear state, and we can start a changelog
that helps to upgrade from there, and think about BC when fixing things
that pop up.

cheers,david

[Daniel Leech]

ok, that works for me then.. lets do it :)

[Lukas Kahwe Smith]

On 06 Aug 2014, at 13:34, Daniel Leech <dan...@dantleech.com> wrote:

> ok, that works for me then.. lets do it :)

great .. so we can expect RoutingAutoBundle 1.0.0-RC1 to be released on August 19th as well.

furthermore it looks like we can soon adopt SonataAdminBundle 2.3, see https://github.com/sonata-project/SonataDoctrinePhpcrAdminBundle/issues/270#issuecomment-51463424

aside from this I spend the day doing a bunch of PRs here and there and ping’ing people in open issues/PRs .. please try to answer, even by just saying no time until August 19th so that we know where we need to find other people to pick up.

[Maximilian Berghoff]

So i will start with answering

I think i won't have time until August 15th.

I would have two open PR's

- ErrorHandling - https://github.com/symfony-cmf/SeoBundle/pull/177
- AlternateLocale - https://github.com/symfony-cmf/SeoBundle/pull/175

and one issue:
- SiteMap - https://github.com/symfony-cmf/SeoBundle/issues/132

(not shure if Wouter is working on:
https://github.com/symfony-cmf/SeoBundle/issues/133)

that I wanted to finish for SeoBundle 1.1. Got questions/problems on
both PR and won't have time before August 16th - except there is a short
and easy solution.

Problem in my timeline is my current custom Project and the fact that
have an example project on my desk, which i need to get solved very
well, to be hired by an other, better, greater company, to get rid of
the current chaotic and stressing stuff, to have freetime again (for CMF
i.e.).

max

[Lukas Kahwe Smith]

On 08 Aug 2014, at 08:17, Maximilian Berghoff <maximilia...@gmx.de> wrote:

> So i will start with answering
>
> I think i won't have time until August 15th.
>
> I would have two open PR's
>
> - ErrorHandling - https://github.com/symfony-cmf/SeoBundle/pull/177
> - AlternateLocale - https://github.com/symfony-cmf/SeoBundle/pull/175
>
> and one issue:
> - SiteMap - https://github.com/symfony-cmf/SeoBundle/issues/132
>
> (not shure if Wouter is working on: https://github.com/symfony-cmf/SeoBundle/issues/133)
>
> that I wanted to finish for SeoBundle 1.1. Got questions/problems on both PR and won't have time before August 16th - except there is a short and easy solution.
>
> Problem in my timeline is my current custom Project and the fact that have an example project on my desk, which i need to get solved very well, to be hired by an other, better, greater company, to get rid of the current chaotic and stressing stuff, to have freetime again (for CMF i.e.).

Trying to group some of the open PRs and tickets ..
see also https://waffle.io/symfony-cmf/symfony-cmf

Aside from the above the following seems to be critical for RC1
https://github.com/symfony-cmf/BlockBundle/pull/205
https://github.com/symfony-cmf/RoutingAutoBundle/pull/106
https://github.com/symfony-cmf/CreateBundle/pull/117
https://github.com/symfony-cmf/symfony-cmf-docs/pull/537
https://github.com/symfony-cmf/RoutingAutoBundle/issues/121
https://github.com/symfony-cmf/TreeBrowserBundle/pull/64
https://github.com/sonata-project/SonataDoctrinePhpcrAdminBundle/pull/283
https://github.com/doctrine/DoctrinePHPCRBundle/issues/155

And the following are things to solve before we can go to stable:
https://github.com/symfony-cmf/RoutingAutoBundle/pull/119
https://github.com/symfony-cmf/standard-edition/pull/17
https://github.com/jackalope/jackalope/pull/236
https://github.com/symfony-cmf/symfony-cmf-docs/pull/524
https://github.com/doctrine/DoctrinePHPCRBundle/pull/146
https://github.com/jackalope/jackalope-doctrine-dbal/pull/210
https://github.com/jackalope/jackalope/pull/238
https://github.com/doctrine/phpcr-odm/pull/549
https://github.com/doctrine/phpcr-odm/issues/541
https://github.com/symfony-cmf/symfony-cmf-docs/issues/533
https://github.com/symfony-cmf/RoutingAutoBundle/issues/90

Finally a few nice to haves:
https://github.com/symfony-cmf/RoutingAutoBundle/pull/80
https://github.com/symfony-cmf/cmf-sandbox/pull/159
https://github.com/jackalope/jackalope-doctrine-dbal/pull/207
https://github.com/symfony-cmf/symfony-cmf-docs/pull/423
https://github.com/symfony-cmf/symfony-cmf-docs/pull/506
https://github.com/jackalope/jackalope-doctrine-dbal/issues/214
https://github.com/jackalope/jackalope-doctrine-dbal/issues/212
https://github.com/jackalope/jackalope/issues/237
https://github.com/symfony-cmf/symfony-cmf-docs/issues/544
https://github.com/symfony-cmf/CreateBundle/issues/119
https://github.com/symfony-cmf/ContentBundle/issues/115
https://github.com/jackalope/jackalope-doctrine-dbal/issues/208
https://github.com/jackalope/jackalope-jackrabbit/issues/92
https://github.com/symfony-cmf/RoutingAutoBundle/issues/110
https://github.com/symfony-cmf/BlockBundle/issues/194
https://github.com/symfony-cmf/BlockBundle/issues/192
https://github.com/symfony-cmf/BlockBundle/issues/190

[Daniel Leech]

On 17/08/14 11:20, Lukas Kahwe Smith wrote:
> On 08 Aug 2014, at 08:17, Maximilian Berghoff <maximilia...@gmx.de> wrote:
>
>> So i will start with answering
>>
>> I think i won't have time until August 15th.
>>
>> I would have two open PR's
>>
>> - ErrorHandling - https://github.com/symfony-cmf/SeoBundle/pull/177
>> - AlternateLocale - https://github.com/symfony-cmf/SeoBundle/pull/175
>>
>> and one issue:
>> - SiteMap - https://github.com/symfony-cmf/SeoBundle/issues/132
>>
>> (not shure if Wouter is working on: https://github.com/symfony-cmf/SeoBundle/issues/133)
>>
>> that I wanted to finish for SeoBundle 1.1. Got questions/problems on both PR and won't have time before August 16th - except there is a short and easy solution.
>>
>> Problem in my timeline is my current custom Project and the fact that have an example project on my desk, which i need to get solved very well, to be hired by an other, better, greater company, to get rid of the current chaotic and stressing stuff, to have freetime again (for CMF i.e.).
> Trying to group some of the open PRs and tickets ..
> see also https://waffle.io/symfony-cmf/symfony-cmf
>
> Aside from the above the following seems to be critical for RC1
> https://github.com/symfony-cmf/BlockBundle/pull/205
> https://github.com/symfony-cmf/RoutingAutoBundle/pull/106
> https://github.com/symfony-cmf/CreateBundle/pull/117
> https://github.com/symfony-cmf/symfony-cmf-docs/pull/537
> https://github.com/symfony-cmf/RoutingAutoBundle/issues/121
> https://github.com/symfony-cmf/TreeBrowserBundle/pull/64
> https://github.com/sonata-project/SonataDoctrinePhpcrAdminBundle/pull/283
> https://github.com/doctrine/DoctrinePHPCRBundle/issues/155

I don't see the above RoutingAuto issues as being "critical", they are
"nice to haves"

[Wouter de Jong]

I don't see the above RoutingAuto issues as being "critical", they are "nice to haves"

Caching is critical, since it completely refactors the MetadataFactory classes. This means a huge BC break if we do it after 1.0. The current cache solution was only meant to be a temporary fix, since I couldn't get it working in the refactor PR. And besides that, why not merge it? :)

And removing the hard PHPCR-ODM is really needed before 1.0 stable.

----

Unfortunately, I'm limited to a tablet for the coming week. So I'll not be able to work on any PR (only commenting if I have internet).

--
You received this message because you are subscribed to the Google Groups "symfony-cmf-devs" group.

To unsubscribe from this group and stop receiving emails from it, send an email to symfony-cmf-devs+unsubscribe@googlegroups.com.

[Daniel Leech]

On 17/08/14 15:54, Wouter de Jong wrote:

I don't see the above RoutingAuto issues as being "critical", they are "nice to haves"

Caching is critical, since it completely refactors the MetadataFactory classes. This means a huge BC break if we do it after 1.0. The current cache solution was only meant to be a temporary fix, since I couldn't get it working in the refactor PR. And besides that, why not merge it? :)

And removing the hard PHPCR-ODM is really needed before 1.0 stable.

Well, if you can find the time to do it, then lets put it in there. If not, I do not want to delay the release of the bundle. We have been working on it for longer than I can remember and I really want to "put it down".

I can't merge the current caching because the tests are failing.

OK for removing the hard dependency, I thought that as it was the only supported option currently
it doesn't make any difference, but then people could implement their own adapters and then the
dependency would not make sense. Lets remove that.

To unsubscribe from this group and stop receiving emails from it, send an email to symfony-cmf-de...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "symfony-cmf-devs" group.

To unsubscribe from this group and stop receiving emails from it, send an email to symfony-cmf-de...@googlegroups.com.

[Ben Glassman]

I'm not sure how worthwhile the jstree 3.0 upgrade is
https://github.com/symfony-cmf/TreeBrowserBundle/pull/64
https://github.com/sonata-project/SonataDoctrinePhpcrAdminBundle/pull/283

The reason being that the current implementation is tightly coupled to
using jstree as the frontend which is less than ideal and the 3.0
branch is different enough from the 1.0 we were using that its more of
a rewrite than a refactor. Putting in the effort to do that would seem
to be better directed towards decoupling the tree browser from a
specific implementation which is a larger project although one which i
know dan leech has already done a lot of work on.

[Lukas Kahwe Smith]

On 17 Aug 2014, at 18:02, Ben Glassman <bgla...@gmail.com> wrote:

> I'm not sure how worthwhile the jstree 3.0 upgrade is
> https://github.com/symfony-cmf/TreeBrowserBundle/pull/64
> https://github.com/sonata-project/SonataDoctrinePhpcrAdminBundle/pull/283
>
> The reason being that the current implementation is tightly coupled to
> using jstree as the frontend which is less than ideal and the 3.0
> branch is different enough from the 1.0 we were using that its more of
> a rewrite than a refactor. Putting in the effort to do that would seem
> to be better directed towards decoupling the tree browser from a
> specific implementation which is a larger project although one which i
> know dan leech has already done a lot of work on.

so we should rather close those PRs? the issues that motivated that update were fixed, right?

[Ben Glassman]

Yes the main reason why those PRs were opened were was that there was
a UI bug in the jstree 1.0 beta version being used where the drop
would not register under certain circumstances. I submitted a css fix
which is a workaround and solves it in any browser other than IE <= 8

[Lukas Kahwe Smith]

Aloha,

Progress overall seems ok.
I do want to discuss a few details with David, so likely we will only finish the releases tomorrow.
We might start some of the tagging today however.

From the issues I noted as critical for RC1 there are only 3 left:

RoutingAutoBundle caching:
https://github.com/symfony-cmf/RoutingAutoBundle/pull/106

CreateBundle workflow support (will discuss this with David tomorrow)
https://github.com/symfony-cmf/CreateBundle/pull/117

DoctrinePHPCRBundle class rename (anyone can take that one?:
https://github.com/doctrine/DoctrinePHPCRBundle/issues/155

Anything else that is critical before we go to RC1?

[Daniel Leech]

This bug RoutingAuto needs investigating before RC1:

https://github.com/symfony-cmf/RoutingAutoBundle/issues/123

[Maximilian Berghoff]

Hi,

> Aloha,
>
> Progress overall seems ok.

unfortunately not at all, i am not able to find some time to finish both
PR on SeoBundle. The work i did at the weekend, was
caused by a need in my project and while working on it. Possible to skip
SeoBundle in this version. Think no other bundles depends on it, right?

max

[Lukas Kahwe Smith]

maybe it will work by RC2 .. otherwise you can also add those new features and release them independent of the main release cycle of the CMF

[Lukas Kahwe Smith]

Aloha,

Alright, I have tagged RC’s of all components and bundles.

I have also prepared a news item:
https://github.com/symfony-cmf/symfony-cmf-website/pull/56

Let me know if I should mention some new feature there.
That being said, I think once we have more documentation, we will highlight some more minor features in subsequent news posts.

I will let things sit a bit and then I will tag RC1 for the SE and sandbox:
https://github.com/symfony-cmf/standard-edition/pull/18
https://github.com/symfony-cmf/cmf-sandbox/pull/264

[gmx Privat]

Hi,

And i found some time to get some features working for SeoBundle. Sounds a little bit egoistic, but i realized that need that features in my project next week. :-)
That said, i will finish the ErrorPages and create the SiteMap stuff over the weekend. The first is nearly ready-just one strange template issue, the second needs to be created completely.

Max

[Lukas Kahwe Smith]

Aloha,

I would like to push forward a bit more. I will do new RC’s of all repos that saw changes this week tomorrow.

PHPCR ODM:
Only needs https://github.com/doctrine/phpcr-odm/issues/541 to be done to tag 1.2.0 stable

Jackalope:
I think we will need a bit more time to do 1.2 here, I guess it will come after CMF 1.2. So right now it is not a priority.
That being said we should ensure that from now on we do not depend on specific Jackalope versions but instead do stuff like ~1.1 to allow future minor version updates. I think I did this in most places already last week.

CMF:
I created a few likely unproblematic PRs for CreateBundle and RoutingAutoBundle that I expect will be merged today.

We have a few new tickets that I created after doing RC1 related to build failures:
https://github.com/symfony-cmf/symfony-cmf/issues/205
https://github.com/symfony-cmf/Testing/issues/71
https://github.com/symfony-cmf/RoutingBundle/issues/264

BlockBundle could use some love but none of that seems critical but likely not too hard to do:
https://github.com/symfony-cmf/BlockBundle/issues/190
https://github.com/symfony-cmf/BlockBundle/issues/192
https://github.com/symfony-cmf/BlockBundle/issues/194

RoutingAutoBundle has one ticket open for 1.0:
https://github.com/symfony-cmf/RoutingAutoBundle/issues/90

We really need to push the docs side, aside from the below tickets, there are likely a few more things that need to be documented:
https://github.com/symfony-cmf/symfony-cmf-docs/pull/524
https://github.com/symfony-cmf/symfony-cmf-docs/issues/533
https://github.com/symfony-cmf/symfony-cmf-docs/pull/423
https://github.com/symfony-cmf/symfony-cmf-docs/pull/506
https://github.com/symfony-cmf/symfony-cmf-docs/issues/544
https://github.com/symfony-cmf/symfony-cmf-docs/pull/556

[Wouter J]

The RoutingAuto component and RoutingAutoBundle are ready for 1.0. All issues with the 1.0 milestone are fixed now.

To fix HHVM support for Testing, I need some help from someone, since I can't run HHVM locally. Someone has to debug what's going wrong with the doctrine dbal initialization.

The SE needs an update from the core SE before releasing stable.

Op woensdag 27 augustus 2014 10:53:17 UTC+2 schreef Lukas Kahwe Smith:

[Lukas Kahwe Smith]

Aloha,

We have two open PRs for PHPCR ODM that need to be merged:
https://github.com/doctrine/phpcr-odm/pull/555
https://github.com/doctrine/phpcr-odm/pull/553

It would also be good to have a PR for the following ticket, but I think its not such a big task:
https://github.com/doctrine/phpcr-odm/issues/557

I want to get those merged and tagged as another RC and then give at least one week before tagging that as stable.

Aside from this I have no other issues/PRs on my radar that are needed before we can go stable with CMF 1.2 .. so if I am overlooking something .. please let me know. So right now I expect the stable release to happen in the week of September 15th. There is one trouble with that David will still be on vacation and I will be on vacation that week as well. One option would be to push the release back by another week, since I will be back then. Or some regular contributors like Wouter and Dan need to take the helm for the stable release.

Note once again that Jackalope 1.2 will not be done for now. We have quite a few open tickets and PRs there that need to be wrapped up before hand.

[Daniel Leech]

On 05/09/14 10:03, Lukas Kahwe Smith wrote:
> Aloha,
>
> We have two open PRs for PHPCR ODM that need to be merged:
> https://github.com/doctrine/phpcr-odm/pull/555
> https://github.com/doctrine/phpcr-odm/pull/553
>
> It would also be good to have a PR for the following ticket, but I think its not such a big task:
> https://github.com/doctrine/phpcr-odm/issues/557
>
> I want to get those merged and tagged as another RC and then give at least one week before tagging that as stable.
>
> Aside from this I have no other issues/PRs on my radar that are needed before we can go stable with CMF 1.2 .. so if I am overlooking something .. please let me know. So right now I expect the stable release to happen in the week of September 15th. There is one trouble with that David will still be on vacation and I will be on vacation that week as well. One option would be to push the release back by another week, since I will be back then. Or some regular contributors like Wouter and Dan need to take the helm for the stable release.

If you tell me what to do I can do it. Otherwise maybe WouterJ would be
more apt, otherwise I don't think a 1 week delay is a disaster :)

[Lukas Kahwe Smith]

On 05 Sep 2014, at 10:03, Lukas Kahwe Smith <sm...@pooteeweet.org> wrote:

> Aloha,
>
> We have two open PRs for PHPCR ODM that need to be merged:
> https://github.com/doctrine/phpcr-odm/pull/555
> https://github.com/doctrine/phpcr-odm/pull/553

merged and tagged RC4

> It would also be good to have a PR for the following ticket, but I think its not such a big task:
> https://github.com/doctrine/phpcr-odm/issues/557

we are leaving this one for 1.3 for now .. though I am not sure if its even really an issue (anymore)

> I want to get those merged and tagged as another RC and then give at least one week before tagging that as stable.

so lets hope we can go stable with the current state ..

> Aside from this I have no other issues/PRs on my radar that are needed before we can go stable with CMF 1.2 .. so if I am overlooking something .. please let me know. So right now I expect the stable release to happen in the week of September 15th. There is one trouble with that David will still be on vacation and I will be on vacation that week as well. One option would be to push the release back by another week, since I will be back then. Or some regular contributors like Wouter and Dan need to take the helm for the stable release.

so I tagged everything ..

this one is hopefully fixed in 1.2.0-RC3:
https://github.com/symfony-cmf/cmf-sandbox/issues/270

this one will hopefully get fixed before the end of the week:
https://github.com/symfony-cmf/Routing/pull/116

[David Buchmann]

> this one is hopefully fixed in 1.2.0-RC3:
> https://github.com/symfony-cmf/cmf-sandbox/issues/270

indeed fixed.

> this one will hopefully get fixed before the end of the week:
> https://github.com/symfony-cmf/Routing/pull/116

if we agree its ok to drop the RouterInterface from
ChainedRouterInterface (see my last comment) i can do that sometime soon.

cheers,david

[Lukas Kahwe Smith]

Aloha,

Sorry things went silent.
We ran into some issues with the PHPCR ODM which are hopefully now fixed and I just released 1.2.0-rc5.

We still have some open tickets here:
https://github.com/doctrine/phpcr-odm/issues/557
https://github.com/doctrine/phpcr-odm/issues/569
https://github.com/doctrine/phpcr-odm/issues/444
https://github.com/doctrine/phpcr-odm/issues/382

Aside from this we have a critical task for the Routing component:
https://github.com/symfony-cmf/Routing/pull/120

A feature omission in the RoutingBundle:
https://github.com/symfony-cmf/RoutingBundle/pull/268

There are some issues with the Testing component:
https://github.com/symfony-cmf/Testing/issues/48
https://github.com/symfony-cmf/Testing/issues/36

[Lukas Kahwe Smith]

All key blockers are solved from my point of view.
I just released PHPCR ODM 1.2.0 RC6 but unless we see any new blockers, I would like to release everything (aside from Jackalope / PHPCR repos) as stable next week. So if you do merge features, they should be minor and very controlled and non controversial. Anything else will have to wait for the next release cycle.

[Nathanael Noblet]

Hey,

  Just playing around with the cmf/simplecms and was wondering if there is a reason why the symfony-cmf/standard-edition doesn't have a 1.2 tag/release?

[Lukas Kahwe Smith]

> On 08 Oct 2014, at 23:15, Nathanael Noblet <nathana...@gmail.com> wrote:
>
> Hey,
>
> Just playing around with the cmf/simplecms and was wondering if there is a reason why the symfony-cmf/standard-edition doesn't have a 1.2 tag/release?

we did two RCs:
https://github.com/symfony-cmf/standard-edition/releases/tag/1.2.0-RC2

regards,
Lukas

[Nathanael Noblet]

Hmm odd,

  I looked at the tags and saw v2.x and didn't scroll down to see those tags. Whats with all the 2.x tags?

[David Buchmann]

hi nathanael,

we forked this SE from the core symfony SE. but indeed we should
probably remove the tags from symfony standard edition, it makes no
sense to have these in the repo (and will confuse composer to no end, as
it will prefer 2.4 or 2.5 over 1.2...)

just created an issue to check if the other maintainers agree:
https://github.com/symfony-cmf/standard-edition/issues/24

cheers,david

On 09.10.2014 06:32, Nathanael Noblet wrote:
> Hmm odd,
>
> I looked at the tags and saw v2.x and didn't scroll down to see those
> tags. Whats with all the 2.x tags?
>
> On Wed, Oct 8, 2014 at 9:37 PM, Lukas Kahwe Smith <sm...@pooteeweet.org

> <mailto:sm...@pooteeweet.org>> wrote:

>
>
> > On 08 Oct 2014, at 23:15, Nathanael Noblet <nathana...@gmail.com <mailto:nathana...@gmail.com>> wrote:
> >
> > Hey,
> >
> > Just playing around with the cmf/simplecms and was wondering if there is a reason why the symfony-cmf/standard-edition doesn't have a 1.2 tag/release?
>
> we did two RCs:
> https://github.com/symfony-cmf/standard-edition/releases/tag/1.2.0-RC2
>
> regards,
> Lukas
>
> --
> You received this message because you are subscribed to the Google
> Groups "symfony-cmf-devs" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to symfony-cmf-de...@googlegroups.com

> <mailto:symfony-cmf-devs%2Bunsu...@googlegroups.com>.

> For more options, visit https://groups.google.com/d/optout.
>
>

> --
> You received this message because you are subscribed to the Google
> Groups "symfony-cmf-devs" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to symfony-cmf-de...@googlegroups.com

> <mailto:symfony-cmf-de...@googlegroups.com>.

> For more options, visit https://groups.google.com/d/optout.

--
Liip AG // Agile Web Development // T +41 26 422 25 11
CH-1700 Fribourg // PGP 0xA581808B // www.liip.ch

[Lukas Kahwe Smith]

Aloha,

So the last remaining issue before we can go to stable is:
https://github.com/symfony-cmf/MenuBundle/pull/209

Something changed in SonataAdminBundle in regards to the show view.

[Lukas Kahwe Smith]

On 13 Oct 2014, at 13:55, Lukas Kahwe Smith <sm...@pooteeweet.org> wrote:

> Aloha,
>
> So the last remaining issue before we can go to stable is:
> https://github.com/symfony-cmf/MenuBundle/pull/209
>
> Something changed in SonataAdminBundle in regards to the show view.

Ok, fixed.

There is a small follow up issue but I do not think we need to stop the release because of this:
https://github.com/sonata-project/SonataDoctrinePhpcrAdminBundle/issues/306

As such I think we can make the release tomorrow.

@WouterJ: we should then also merge the dev branch of the docs into master, right?

[David Buchmann]

>> So the last remaining issue before we can go to stable is:
>> https://github.com/symfony-cmf/MenuBundle/pull/209
>>
>> Something changed in SonataAdminBundle in regards to the show view.
>
> Ok, fixed.

and i found the problem you stumbled over and fixed it:
https://github.com/symfony-cmf/MenuBundle/pull/210

> There is a small follow up issue but I do not think we need to stop the release because of this:
> https://github.com/sonata-project/SonataDoctrinePhpcrAdminBundle/issues/306

and a fix for that as well. note that there is more to handle, but if we
see it makes basically sense we can merge and improve later, or just
consider this a bugfix that is non-blocking for the release (the show
part of sonata seems less important than the rest)

https://github.com/sonata-project/SonataDoctrinePhpcrAdminBundle/pull/307

on a side note: why did we activate show for the menu but not for the
other admins? should we remove it from menu actually? or add it to all
admins?

cheers,david

[Lukas Kahwe Smith]

On 13 Oct 2014, at 22:39, David Buchmann <da...@liip.ch> wrote:

>>> So the last remaining issue before we can go to stable is:
>>> https://github.com/symfony-cmf/MenuBundle/pull/209
>>>
>>> Something changed in SonataAdminBundle in regards to the show view.
>>
>> Ok, fixed.
>
> and i found the problem you stumbled over and fixed it:
> https://github.com/symfony-cmf/MenuBundle/pull/210
>
>> There is a small follow up issue but I do not think we need to stop the release because of this:
>> https://github.com/sonata-project/SonataDoctrinePhpcrAdminBundle/issues/306
>
> and a fix for that as well. note that there is more to handle, but if we
> see it makes basically sense we can merge and improve later, or just
> consider this a bugfix that is non-blocking for the release (the show
> part of sonata seems less important than the rest)
>
> https://github.com/sonata-project/SonataDoctrinePhpcrAdminBundle/pull/307

ok, will check both and merge and tag new RCs

> on a side note: why did we activate show for the menu but not for the
> other admins? should we remove it from menu actually? or add it to all
> admins?

no clue. i guess its mostly just relevant for when people do not have permissions to edit something?

[David Buchmann]

>> on a side note: why did we activate show for the menu but not for the
>> other admins? should we remove it from menu actually? or add it to all
>> admins?
>
> no clue. i guess its mostly just relevant for when people do not have permissions to edit something?

i guess so. which can make sense - its just that we miss translations
for the labels and we only do it for one of the admins, which is
inconsistent.

if somebody has an opinion, please tell. otherwise i will make PRs to
add it to the other admins too, so that we use that feature fully.

cheers,david

[Lukas Kahwe Smith]

Aloha,

Still waiting on feedback on some PRs:
https://github.com/sonata-project/SonataDoctrinePhpcrAdminBundle/pull/307
https://github.com/symfony-cmf/MenuBundle/pull/210

But I tested them and if no feedback is provided they will be merged and we can release ..

Unfortunately Travis CI deployed a new version of HHVM which is causing issues, the good news is that there is a solution in sight:
https://github.com/travis-ci/travis-ci/issues/2863

I would hate to release before that is cleared up.
We can then also merge the changes to the allowed failure matrix before releasing.

FYI PHPCR ODM 1.2 stable is already released.

[sm...@pooteeweet.org]

On 15 Oct 2014, at 16:14, Lukas Kahwe Smith <sm...@pooteeweet.org> wrote:

> Aloha,
>
> Still waiting on feedback on some PRs:
> https://github.com/sonata-project/SonataDoctrinePhpcrAdminBundle/pull/307
> https://github.com/symfony-cmf/MenuBundle/pull/210
>
> But I tested them and if no feedback is provided they will be merged and we can release ..
>
> Unfortunately Travis CI deployed a new version of HHVM which is causing issues, the good news is that there is a solution in sight:
> https://github.com/travis-ci/travis-ci/issues/2863
>
> I would hate to release before that is cleared up.
> We can then also merge the changes to the allowed failure matrix before releasing.

There is still not a solution for the HHVM issue.
One option would be to do some additional HHVM steps during the install to try and set an ini setting, but imho this is going in the wrong direction. It would need some work and I am currently more in a wait and see mode.

So as I do not want to delay any further, I suggest that we simply mark HHVM as allowed failure again :-/
While we are at it .. we can them remove dev-master from the allowed failures.

WDYT?

[Maximilian Berghoff]

yes would say +1 for moving hhvm to the alowed failures.

[David Buchmann]

> So as I do not want to delay any further, I suggest that we simply mark HHVM as allowed failure again :-/
> While we are at it .. we can them remove dev-master from the allowed failures.

+1 for both, yes. i can go over the repositories tonight and do that.

[Lukas Kahwe Smith]

thx!

[David Buchmann]

> i can go over the repositories tonight and do that.

i updated the .travis.yml of everything cmf i found. hope i missed
nothing, otherwise tell.

[Lukas Kahwe Smith]

tagging has begun ..

main issue to wrap things up are the 3 non WIP PRs open on the SonataDoctrinePhpcrAdminBundle:
https://github.com/sonata-project/SonataDoctrinePhpcrAdminBundle/pulls

we could just merge https://github.com/sonata-project/SonataDoctrinePhpcrAdminBundle/pull/307 and not worry about the others, but are hoping that we will get some more feedback ASAP before we tag.

once this is wrapped up we can finalize the tagging by tagging the sandbox.

[Lukas Kahwe Smith]

ok all resolved .. David is in the process of tagging the last repos ..
will then need to update the composer.json/locks in the sandbox / SE and tag those as well.

I have prepared a news item:
https://github.com/symfony-cmf/symfony-cmf-website/pull/59

if someone feels some feature should be highlighted there let me know.

@WouterJ: I propose we then also merge the “dev” branch in the docs now as well, wdyt?

[Lukas Kahwe Smith]

Aloha,

So form my point of view we are ready:
https://github.com/symfony-cmf/standard-edition/pull/18
https://github.com/symfony-cmf/cmf-sandbox/pull/264
https://github.com/symfony-cmf/symfony-cmf-docs/pull/594/files
https://github.com/symfony-cmf/symfony-cmf-website/pull/59

Anyone see a reason to not merge and tag?

[Daniel Leech]

Hmm. Found a slight problem with the Creating a Basic CMS tutorial, the
RoutingAuto intiializer is executed before
any user initializers, which prevents the final chapter of the Creating
a Basic CMS tutorial being completed.

So I will add priority support to the initializers. Would it be possible
to get that in this release if I do that this morning? :/

[gmx Privat]

I would say ok. But you should'nt introduce a BC Break as if was done when the initializer names where introduced.

Mit freundlichen Grüßen

Maximilian Berghoff


---------------------------------------
Maximilian Berghoff
Wiesenstraße 44
91617 Oberdachstetten

Mail: Maximilia...@gmx.de
Mobile: +49 151 64825096

> --
> You received this message because you are subscribed to the Google Groups "symfony-cmf-devs" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to symfony-cmf-de...@googlegroups.com.

[Daniel Leech]

I am blocked because DoctrinePHPCRBundle hangs when resolving the
dependencies.

It seems to be OK on travis, but I can neither install it on my local
machine or on my remote server.

Will try again later.

Dan

[Lukas Kahwe Smith]

Aloha,

so it is done http://cmf.symfony.com/news/1-2-stable-released

[Daniel Leech]

Excellent!

[Thomas Rabaix]

Good Job!

--
You received this message because you are subscribed to the Google Groups "symfony-cmf-devs" group.

To unsubscribe from this group and stop receiving emails from it, send an email to symfony-cmf-devs+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
Thomas Rabaix
http://rabaix.net | http://sonata-project.org

[Joschi 127]

Thanks a lot!

It works fine so far in the projects that we have already updated.

On 27.10.2014 11:21, Thomas Rabaix wrote:

Good Job!

On Sat, Oct 25, 2014 at 9:13 PM, Daniel Leech <dan...@dantleech.com> wrote:

Excellent!

On 25/10/14 20:19, Lukas Kahwe Smith wrote:

Aloha,

so it is done http://cmf.symfony.com/news/1-2-stable-released

regards,
Lukas Kahwe Smith
sm...@pooteeweet.org

--
You received this message because you are subscribed to the Google Groups "symfony-cmf-devs" group.

To unsubscribe from this group and stop receiving emails from it, send an email to symfony-cmf-de...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
Thomas Rabaix
http://rabaix.net | http://sonata-project.org

--
You received this message because you are subscribed to the Google Groups "symfony-cmf-devs" group.

To unsubscribe from this group and stop receiving emails from it, send an email to symfony-cmf-de...@googlegroups.com.