What about Components in new release ?

[joomleb]

Reading FAQ point 8:

8. When will you create a new release?

As soon as the dust settles, and we finalize our short-term plan. The next release will be based on the existing 4.5.3 code and will be fully compatible just like previous releases. There is currently no set release date.

I have some questions:

Is there a release time idea for the "first release" ? (days, weeks, months)
What about some of the most importants components ?
Do Anyone Know if their administrators have commented yet what's happening ?

PHP-Shop
Community Builder
Sipleboard Forum

Is there an idea about features will be included on this "new release" ?

Many Thanks to all
Bye, Emiliano

[keliix06]

To get a good idea of what the first release will look like check out the 4.5.3 cvs from mamboforge.net. There was still a good list of bugs to get through before a stable release can be made.

[bohn002]

well i cant speak for them but i cant think they will be a big fan of mr lamont. unless he tries to sway them with some cash, but i really dont think they would be that low.(component makers not lamont)

[Riba]

Few of us are in this for cash anyway.

[bohn002]

nice hat! friend or hat?

[progster]

We will just keep developing simpleboard and it will support what was going to be 4.5.3 . After that we'll see

[eyezberg]

Community Builder (as far as I heard..): team is working on test-team candidate 9 at this very moment, working towards RC2.. don't worry
Once 4.5.3 is out, you'll find it so much better you'll want to play around it for some time before you start to think about CMTs, honest!

[Websmurf]

I can say for phpbb/yanc/occasion manager that we will support OSM and Mambo.

we'll see what happens after 4.5.3

[idigital]

Miro's release of Mambo 4.5.3 Beta brings up an odd situation here though... What if Miro take a 3PD CMT and include it into the core of their CMS as a feature? Not a lot we can do about it as far as open source goes...

Seems like that's what's happened to MosCE, he's openly stated his support for OSM and that he won't be developing it further for Miro's branch, then it's included into the core of the Beta release.

Sets a nasty precedent for Miro to further absorb the 3PD community's work into their CMS, and with a standard open source license there's nothing that can be done. Possibly Creative Commons licensing would allow an open source license with a provisor that Miro aren't to include it into their Mambo. I don't know. Seems wrong either way.

I'm considering the concept of including code into further developments that would either prevent it working in Miro's Mambo, or bring up a link to the new project, or some such...

Really an odd situation here, I think. I wonder where happynoodleboy is?

[omerten]

I will continue develop for OSMs and not care about what miro does. I'm pretty sure they won't include my spaghetti code into the core, but if they do so it's their fault
Support, new features etc... will of course only be provided for OSM-users. It's already hard to maintain components for different OSM-releases, hence I guess nobody can expect that I'll additionally support a completely different CMS in the future.

regards,

Oli

[lonemamber]

Really an odd situation here, I think. I wonder where happynoodleboy is?

Why, seems he was here all along, pardner. Mosey over and have a read of the fireside chat I've just had with him, good natured pilgrim that he is.

Thankye kindly for your concern,

The Lone Mamber