Although the 2.x web client might be there for some time (but how long before sunsetting?), but the fact that development is frozen is enough of concerns for existing users. That means existing users get themselves into a dead end.
And the fact that the stores are incompatible just make the whole thing even harder to swallow. And "having a rethink in this exact area" means, is the rethink over or just starting?
And what is the decision on that?
And as you said, people have probably done a lot of customization and extensions already. Does it mean that, we are either stuck with a shelved product, or take the pain to re-develop again all those customizations in a new environment, with all the cost of development, training, testing, learning curve… ?
Too many questions unanswered after half a day of trying out the new 3.0.
And the fact that the stores are incompatible just make the whole thing even harder to swallow. And "having a rethink in this exact area" means, is the rethink over or just starting?
And what is the decision on that?And as you said, people have probably done a lot of customization and extensions already. Does it mean that, we are either stuck with a shelved product, or take the pain to re-develop again all those customizations in a new environment, with all the cost of development, training, testing, learning curve… ?
Too many questions unanswered after half a day of trying out the new 3.0.
Although the 2.x web client might be there for some time (but how long before sunsetting?), but the fact that development is frozen is enough of concerns for existing users. That means existing users get themselves into a dead end.Nobody said development was frozen. We have a naming problem at the moment - there will be two web clients: JSF and Slingshot. Obviously they can't both be the "Web Client" but they both exist and are being worked on. More effort is being poured into Slingshot, but there are also people working on the JSF client.
And the fact that the stores are incompatible just make the whole thing even harder to swallow. And "having a rethink in this exact area" means, is the rethink over or just starting?The stores aren't incompatible at all. You can already create FTP and CIFS interfaces to SiteStore purely through configuration. APIs can access both stores. The only issue is that the current JSF client can't access it, because it was never designed with that in mind. Doesn't mean it's incompatible though.
And as you said, people have probably done a lot of customization and extensions already. Does it mean that, we are either stuck with a shelved product, or take the pain to re-develop again all those customizations in a new environment, with all the cost of development, training, testing, learning curve… ?No, of course not.
… 3.0 … latest nightly build dates back to 17 june.Are you looking in the correct place? http://dev.alfresco.com/downloads/nightly/dist/
Haha, rscheele dude, why did you have to post just before another build coming out
I'd say more "alpha" at this stage :wink:
This is a bit of a concern for me. We are currently planning for a test of Alfresco, coincidentally, we are planning for the test phase A to start on 31st July.
I already have a test system running with 2.1 but I am finding some of it's limitations a bit too discouraging, particularly in light of a new version coming out on an uncertain but close date that is (by the sounds of things) not easily transitioned to from 2.1, the features planned for 3.0 are much more in line with what we are looking for.
The questions I am asking myself, and that are causing me to feel a fair bit of strain with my colleagues
are:1. Is it worth deploying a 2.1 or 2.9 Alfresco installation, getting everyone used to the system, creating documentation for training, scheduling time from other departments, ordering hardware, creating spaces / rules / permissions /customisations, all with software that is a dead end.
2. Can the 3.0 dev build provide enough stability for a limited test as it currently stands?
3. Will the 3.0 release be ready when we need it to be (Phase B of the test starts 11/8 when we bring in other departments and try real world scenarios)
Basically, if the current 3.0 build is usable without having to have someone babysit the server then I'm all for starting with that, providing there is at least a good chance it will be ready roughly when it's supposed to be. I'm not trying to pressure anyone, just want to know is all so that I can plan properly
Thank you very much for your time,
Alan
