Points For My Clarification About 5.7

Permalink
Hello All

This post is just to get some clarification on a few points about 5.7.
The points may come across as negative but I am hoping there will be some positive reply's which will clear up my confusion.

1. Will it be possible to upgrade from 5.6.x to 5.7.
I have read that this may not be possible, which in essence means that I will not be able to upgrade my existing sites and they will have to stay on their current version unless the sites are rebuilt (not a practical solution unless the client wants to pay again).

2. Existing add-ons will not work with 5.7.
Can anyone advise me if this is true and how many add-ons are 5.7 ready?

3. Will 5.7 be launched with a limited number of add-ons or will the launch be delayed until a suitable number of add-ons have been upgraded?

4. Will the add-ons be split in the Marketplace pre 5.7 and post 5.7 to avoid confusion for non technical users?

5. Will the How To's and forum posts be split in a similar way?

6. Will the core be investing any time to providing meaningful documentation for 5.7?

It appears from some of the posts I have read that 5.7 is a totally new beast and that the core team are looking at this as a 'migration' not an 'upgrade'.
This is all well and good but does that not bring you right back to square one again with C5? In essence chuck everything you built away and use this new version.
If that is the case there are many newer CMS in the market in a similar or more advanced position that will take away potential users from C5 which would now be a start up CMS.
All of the work done by the core team and the developers for add-ons has to be restarted from scratch and that makes C5 a lot less attractive as it now has no usable history or historical resource, 5.7 is just a new kid in a big class.

Again I am sorry if these appears to be negative comments/questions but I hope that the answers back will help me decide to either look for a new CMS with a decent add-on pool and resources or stick with 5.6.X until 5.7 matures.

I am really hoping I have just grabbed the wrong end of the stick with all this and just missed the post saying every thing is fine and there will be no dramas :)

madeforspace
 
drbiskit replied on at Permalink Reply
drbiskit
I've just been reading another post, which while not answering all your questions, does deal with some useful points...
http://www.concrete5.org/community/forums/5-7-discussion/5.7-upgrad...
madeforspace replied on at Permalink Reply
madeforspace
Thanks for sharing the post, I had not seen that.
So by the sound of it it may well take time to migrate each site and effort which equates to money for most developers :(
Great to see the concept of long term support for 5.6 being proposed. fingers crossed on that one.
I guess it's wait and see about the add-on and possibly even themes.
Remo replied on at Permalink Reply
Remo
2. I've ported a few of my add-ons and generally - if your add-on is simple, no fancy page attribute with defaults stuff going on, it's pretty easy to port. Change a few class names, add a couple of namespaces and you're good to go. No clue how many people will do that. Right now, we can't upload a 5.7 add-on to the marketplace and I guess that makes sense since 5.7 is still in flux. I think it might make sense to have the ability to publish 5.7 add-ons before 5.7 is stable to fill the marketplace. The API would have to be stable though..

6. I obviously can't talk for the core team, but I really hope that we as a community will be able to send pull requests. There are so many issues, undocumented helper functions, typos and similar things. I've stopped reporting them because the whole thing is out-dated. We should really try to do this better with 5.7