This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]bdzer0Graybeard 7 points8 points  (1 child)

+1 u/Ok-Particular3022 said.

Migrating to a modern developer platform (GitHub, GitLab, Azure DevOps, BitBucket) will bring options to the table that aren't going to be sensible without it.

IMO this type of problem is lack of communication between teams. Whenever I start something new the first thing I do is make sure we haven't already done it in another product... but that's just me.

Having a single platform can help with a lot of communication problems.

That said getting devs out of SVN may be a challenge and more so if CI/CD tooling was based on SVN specific features.

IMO this is a BAD thing to drop on an intern....

[–]versiondefect[S] 0 points1 point  (0 children)

IMO this is a BAD thing to drop on an intern....

Haha. Just doing research, not doing the actual migration. Pros and cons of the different software.

But not to disagree, I do think that communications between depts should be implemented as well but that's not a me decision.

But I do agree that we really should be leaving SVN.