Too much in one go
Permalink
Having been playing with 5.7 WIP it feels like too much in one go. Not from a UI point of view, but that there are other new features inside also lurking with bugs.
So, an alternate process:
- Take all the non-ui features currently appearing in 5.7: redactor, gathering, discussion, conversation, asset management .... etc.
- Release them with 5.6.3, making whatever core enhancements are necessary to support them.
- Get these stable with further point releases of 5.6.3.1, 5.6.3.2 etc.
Then, once all the real functionality is stable and risk-free, add the new interface for the 5.7 release.
Advantages:
- We don't get all the newness and associated bugs in one go.
- The scope of bugs is limited by each step.
- New functionality can be hardened by real world use before the new UI is added.
- We get the most useful aspects of the new functionality sooner.
- When 5.7 is subsequently released it will have a more stable starting point.
Disadvantage:
- Extra steps always appear to add work (even if in the long run they may reduce work).
So, an alternate process:
- Take all the non-ui features currently appearing in 5.7: redactor, gathering, discussion, conversation, asset management .... etc.
- Release them with 5.6.3, making whatever core enhancements are necessary to support them.
- Get these stable with further point releases of 5.6.3.1, 5.6.3.2 etc.
Then, once all the real functionality is stable and risk-free, add the new interface for the 5.7 release.
Advantages:
- We don't get all the newness and associated bugs in one go.
- The scope of bugs is limited by each step.
- New functionality can be hardened by real world use before the new UI is added.
- We get the most useful aspects of the new functionality sooner.
- When 5.7 is subsequently released it will have a more stable starting point.
Disadvantage:
- Extra steps always appear to add work (even if in the long run they may reduce work).
Hm, this is an interesting idea. It might also make the transition/upgrade to 5.7 easier if it was more gradual. I haven't really looked around the 5.7 code much yet so I have no idea how difficult this would be for the team (or if it's even possible), but it sounds like a pretty decent idea to me.
My two cents here :
doing so would also make 5.7 enthusiasts happy since they would get more of the new features to see in stable releases. Actually a few fellow are actively waiting (if that's even possible) for some of 5.7 features to come out.
doing so would also make 5.7 enthusiasts happy since they would get more of the new features to see in stable releases. Actually a few fellow are actively waiting (if that's even possible) for some of 5.7 features to come out.
Well I can see the appeal of making baby steps, so I get why one might wonder down this lane. Moreover, we have occasionally cherry picked things that we've got working in 5.7 branches back into private 5.6 branches for client work (i'm thinking of SSO and topics).
Sadly, I don't see this as being a great plan when you start thinking about details. Case in point, redactor and gathering are both highly dependent on the new UI stuff. Conversations need to work the the featured data type and page types and stuff. It's all pretty deeply interconnected.
Looking at deep changes vs. cosmetic ones, really the big stuff here is the page type rethink. Its not like we're reworking permissions (5.6) or other heavy stuff. I don't see an easy way to pull out the page type rethink without also doing the composer and UI changes...
So yes, love the idea of interim steps in life, no I don't see an easy way for us to use that approach to save effort here.
Sadly, I don't see this as being a great plan when you start thinking about details. Case in point, redactor and gathering are both highly dependent on the new UI stuff. Conversations need to work the the featured data type and page types and stuff. It's all pretty deeply interconnected.
Looking at deep changes vs. cosmetic ones, really the big stuff here is the page type rethink. Its not like we're reworking permissions (5.6) or other heavy stuff. I don't see an easy way to pull out the page type rethink without also doing the composer and UI changes...
So yes, love the idea of interim steps in life, no I don't see an easy way for us to use that approach to save effort here.
What is happening with gatherings since this video was made?
I see the permission for it (in Task Permissions) on the dashboard, but do not see any installable blocks or ways to actually set things up.
I see the permission for it (in Task Permissions) on the dashboard, but do not see any installable blocks or ways to actually set things up.
even the job is still there..
so will this come back or should somebody remove the unused stuff?
so will this come back or should somebody remove the unused stuff?
