I do not believe that we should strictly adhere to the 6 month release schedule, particularly when monumental changes are being made and are yet to be finished. I, for one, constantly encounter limitations and bugs in Vivid. Such problems I would expect in a pre-Alpha release, not in one that is one week from being released
.
If I were a developer working on Vivid, I would not be happy with the current state of its preparedness. In all fairness to the developers, I think that, if a release is to be made this month, it should be scaled back to a slightly modified version of Utopic.
I definitely do not want to see KDE with egg on its face this time round. So I would urge those who have influence over release decisions to seriously consider the consequences of releasing Vivid in its current state and look at alternatives
.
.If I were a developer working on Vivid, I would not be happy with the current state of its preparedness. In all fairness to the developers, I think that, if a release is to be made this month, it should be scaled back to a slightly modified version of Utopic.
I definitely do not want to see KDE with egg on its face this time round. So I would urge those who have influence over release decisions to seriously consider the consequences of releasing Vivid in its current state and look at alternatives
.












as I have now found that the jpg files that I was accessing were 0B long. I must have made the monumental mistake of not doing a "safely remove" when I copied the files onto a USB stick. So I am pleased to say that all is well with that aspect of Vivid.
Comment