When saving a read-only buffer with "Save as" under another name, the buffer remains read-only after the save. In my opinion, it is pointless to keep read-only flag for a newly created file. After all we have just wrote the file, why should it be read-only after writing? I advise to reset read-only flag, when saving under a different name.
The reason why the document was flagged as read-only hasn't changed; basically kate saved an exact copy of the read-only file, if you decide to edit it anyway, you'll have to disable the read-only mode from the Tools menu.
Victor I've just tested with kate from the latest git master and I cannot reproduce the issue. I assume by read only you mean user/group/other set to read only. I set one of my files to this and then used save as and I was able to save changes in the "saved as" file. Can you please retest and confirm if this is still an issue for you.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!