Logos 4 Roadmap and Migration from 3.0
Would it be possible to have a proposed roadmap for Logos detailing what function is scheduled for 4.1, 4.2, etc. I think that this will help those users who require specific features plan their migration from 3 to 4.
Also I would be interested to understand what the recommended approach to the migration is i.e. should we stick with Logos 3.0 until the shipping version of Logos 4.x contains all that we need/want or should we run 3.0 and 4.x in parallel? If we choose the second scenario will there be tools that help us share our data between versions? For example notes would lose their immediacy if when working in version 3 you had to start version 4 to capture some ideas/thoughts.
Is it also safe to assume that all new resources will ship in Logos 3 and Logos 4 format until Logos 4 has all of the functionality of 3.0f and that when running 4.0 and 3.0 in parallel all licensed resources will be available to both platforms.
God Bless
Graham
Pastor - NTCOG Basingstoke
Comments
-
Would it be possible to have a proposed roadmap for Logos detailing what function is scheduled for 4.1, 4.2, etc. I think that this will help those users who require specific features plan their migration from 3 to 4.
Also I would be interested to understand what the recommended approach to the migration is i.e. should we stick with Logos 3.0 until the shipping version of Logos 4.x contains all that we need/want or should we run 3.0 and 4.x in parallel? If we choose the second scenario will there be tools that help us share our data between versions? For example notes would lose their immediacy if when working in version 3 you had to start version 4 to capture some ideas/thoughts.
Is it also safe to assume that all new resources will ship in Logos 3 and Logos 4 format until Logos 4 has all of the functionality of 3.0f and that when running 4.0 and 3.0 in parallel all licensed resources will be available to both platforms.
This would be helpful if we could get a rough mud map. I'm not expecting date or anything like that, but just a feel of what exactly is going to be brought in to 4.0 in later versions and in what order. I also respect that this would be a 'fluid' document at this point in time. Even if at this point it was a simple clear idenfification of what is in 3.0 that won't be in 4.0 release and whether or not it will be included in a future 4.0 release. If not an indication of what, if any, Logos sees as the alternative for that feature that is not being carried over. Once 4.0 is out the door maybe then the mud map could be updated to show what we can expect to see in 4.1 and so the process would continue...
Migration of things like notes from 3.0 to 4.0 I expect would be a one off conversion and I am not looking for something to sync between the two versions. I would expect to do all my notetaking in 4.0 once it is released. I can see where this will cause for users, and probably a lot more issues for others than it will for me but at the same time a sync tool may pull Logos away from what I really want them to focus on i.e. 4.0 because of time needed to develop, maintain and support such a tool - if it really could be done with minimal impact then it would be great cause it will cause some grief.
On user documents other questions are yet to be answered on the handling of things like user created timelines, parrallel passages etc that were set up in 3.0. Will this be supportted on any level in 4.0 ... since I haven't seen what 'timelines' means in 4.0 due to not getting it with beta 1, and yet to explore what 4.0 offers in the area of parraellel passages.
0 -
