Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • 3
    The best approach is to have v1 and v2 of the API as two separate deploys, with two separate code bases. Anything else is going to be a massive pain, so there isn't really a 'better' way to do this. Not doing it is the better way of doing it. Can you explain a little why you can't do it. What are the limitations here? Is this code you maintain? Or are you just a single developer working on a team that maintains this? Commented Aug 19, 2016 at 10:19
  • 1
    @CormacMulhall You are right, I'm only one of the developers working on this repo and I'm not the guy who can make this decision of splitting v1 and v2 code. Commented Aug 19, 2016 at 12:41
  • 1
    I then would stick with just naming the packages with the version number, and keeping the classes clear of that information. The programmers are going to already have to be so aware that the code base has two versions in it that you don't need to point this out in the class names. Commented Aug 19, 2016 at 12:48