Protected branches were implemented for GIT 2 years ago, why it still
hasnt been implemented for SVN?

Am actually quite suprised how can this be missed from the list of features. All your SVN competitors like Assembla, Сloudforge, Beanstalkapp, XP-dev, SourceRepo have protected branches or access levels.
And it would take only few days to implement cause svn has built-in access control.

Am asking cause thats the only features that holds us from migration to Deveo.

In deveo there is currently no way to determine if a code review will end up with a merge conflict or not. There is also no way to poll for branches that have code reviews.

My feature suggestion would be that on the Deveo side you would automatically merge the target and destination branches and store the results somewhere like refs/pull/000/head and refs/pull/000/merge where the head would be the target branch and the merge would be a up to date merged version.

This would fix the two biggest issues atleast I myself have with deveo. Not being able to tell whether or not merging a code review will end up in a merge conflict before actually pressing the merge button and secondly not being able to properly run continuous integration builds merged versions of branches that are up for code review.

Currently if you would want to run continuous integration on the merged version of the code and use Deveo you would have to build all the feature branches (even ones without code reviews) every time something is pushed to master.

In deveo there is currently no way to determine if a code review will end up with a merge conflict or not. There is also no way to poll for branches that have code reviews.

My feature suggestion would be that on the Deveo side you would automatically merge the target and destination branches and store the results somewhere like refs/pull/000/head and refs/pull/000/merge where the head would be the target branch and the merge would be a up to date merged version.

This would fix the two biggest issues atleast I myself have with deveo. Not being able to tell…

It would be great if entire repositories could be downloaded and uploaded (obviously this is for svn and not git). This would allow existing repositories to be easily moved to deveo without loosing history and would allow backups (something that's been a requirement for any hosts for at least one company I work with).

I understand it may be expensive to do this immediately on demand, but could be a scheduled task pushing or pulling from ftp, amazon s3, dropbox, etc.

Download could be a scheduled (weekly, daily) tasks or triggered to run once. Uploads only make sense if you trigger it to create a new repository.

It would be great if entire repositories could be downloaded and uploaded (obviously this is for svn and not git). This would allow existing repositories to be easily moved to deveo without loosing history and would allow backups (something that's been a requirement for any hosts for at least one company I work with).

I understand it may be expensive to do this immediately on demand, but could be a scheduled task pushing or pulling from ftp, amazon s3, dropbox, etc.

Download could be a scheduled (weekly, daily) tasks or triggered to run once. Uploads only make sense if you…

I'd like to see a possibility to test a new hook. E.g. testing a git commit hook is currently done with pushing a dummy commit, which is not nice.
Also some log of what happened with the hook firing would be nice to see in user space.

As DevOps, I'd like to be able to create new permission groups e.g. (Guest, Master, Administrator, Developer, MY_DEVELOPER_GROUP) and set my custom permissions for it.
e.g.
Like preset groups here
https://app.deveo.com/docs/user/projects/I'd like to see my custom group.

It would solve problem that we want to let developers create/destroy repositories, however they wouldn't be able to commit to protected branches and/or avoid code reviews if we made them admins (as was suggested).

Currently (as of release 3.7.0) the "Discussion" tab in a Code Review does not seem to show the content of a comment if the line in question has been modified by a subsequent commit. There does not seem to be an option to actually view the text of the comment?

It would be nice if it would be possible to edit README.md file in deveo, like in GitHub and Bitbucket. That possibility could be configurable per project, since atleast bigger companies most likely won't need such feature. GitHub and Bitbucket let user edit any txt file, but I do not see that so necessary.

Right now you can add image attachment to issues. That involves taking a screenshot, opening an image editor, pasting, saving a file, naming it, switching to the issue, adding the attachment and finding the file. The new flow would improve to: screenshot, switch to issue, paste. As for feasibilty, many other issue trackers (assembla, fogbuzz) and Web apps (gmail, slack) have this functionality.

The LargeFiles extension works pretty seamlessly with hg, requires no dedicated extra services like the GitHub-developed git alternative, and works exactly as users expect, over the same transport layer.

I'd love to see Assembla-style integration between tickets and repository (in my case, svn) commit comments. Basically search the commit comment for "<keyword> #<num>", where <num> is a ticket number, and <keyword> is either a ticket status or "Re". When this is found, then the whole commit comment is attached as a comment on the ticket (with a link to the commit); and if <keyword> is a ticket status, then also change the status of the ticket to whatever that status is.

So for example, if my comment is "Splines now properly reticulated, Test #42." then ticket #42 gets this (plus commit link) as a comment, and its status changed to "Test". If my commit comment is "Re #123, frobnors now partially cromulated", then ticket #123 gets this as a comment (with commit link), but the status is unchanged.

(As Assembla is now screwing over their long-time customers, you have a chance to pick up a whole lot of new users! But this is pretty much a must-have feature for us.)

I'd love to see Assembla-style integration between tickets and repository (in my case, svn) commit comments. Basically search the commit comment for "<keyword> #<num>", where <num> is a ticket number, and <keyword> is either a ticket status or "Re". When this is found, then the whole commit comment is attached as a comment on the ticket (with a link to the commit); and if <keyword> is a ticket status, then also change the status of the ticket to whatever that status is.

So for example, if my comment is "Splines now properly reticulated, Test #42." then ticket #42 gets this…

When a SSH communication key arrangement is first made, the communication program asks if you want to trust the server's key with a fingerprint that is shown on screen. Usually the user doesn't have the information, so they just accept it, risking a man-in-the-middle attack.

If Deveo's protected web site showed fingerprints of the keys they use for SSH communications on their servers, users could really verify the correctness of the connection.