When inviting a person to a session with a SVN shared project, the negotiation can't be successful, when the invitee tries to checkout the project as a new one.
--- old+++ new@@ -1 +1 @@-When inviting a person to a session with a SVN shared project, the negotiation can't be successfull, when the invitee tries to checkout the project as a new one.+When inviting a person to a session with a SVN shared project, the negotiation can't be successful, when the invitee tries to checkout the project as a new one.
status: closed-accepted --> open-accepted
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK, I see. Here's my ad-hoc guideline, effective immediately:
A new Saros version should not introduce new bugs. So it should not be released if the version-to-be-released includes a bug that was not present in the previous Saros release.
That's why I wanted to know since when this bug is around: Is it included in branch release/14.10.31 and introduced after release/13.12.6? If yes, the fix should go on branch release/14.10.31. If not, the fix is postponed to a later release.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Regression. Thank you for reporting this issue as it has not been found during the UAT.
Diff:
Indeed, SVN was not tested during the UAT.
@Stefan: Was the status "closed-accepted" intentional?
Can anyone confirm that this problem was not present in 13.12.6?
Yes I close this bug as we have no guideline on how to handle regressions for versions that are either unreleased or still under development.
OK, I see. Here's my ad-hoc guideline, effective immediately:
That's why I wanted to know since when this bug is around: Is it included in branch release/14.10.31 and introduced after release/13.12.6? If yes, the fix should go on branch release/14.10.31. If not, the fix is postponed to a later release.
Feature got removed.