Home/ Questions/Q 7631845
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-31T06:27:41+00:00

i am working on project in delphi 7 and Tortoise svn the project is

  • 0

i am working on project in delphi 7 and Tortoise svn the project is a sort of a survey tool.
we are current starting development on a new version of it that would be myproject 1.8 and in 2 months time we will start with myproject 2.0.

Note : we had inherited the already existing svn. so it not our design

Scenario:
I have just a single folder in my c:\ that is c:\project\myproject\ , we are a startup so we didnt start with the project, we started handling from myproject 1.5..but now myproject 1.5 code has disapeared and turned in myproject 1.6..so when we started with myproject 1.7 we made a folder c:\project\myproject\NV1.6Code and copied the whole code into that folder and started with myproject 1.7…now i have no idea how to maintain the sub versions like myproject 1.7.1, myproject 1.7.2 or `myproject 1.6.4 in our current state.

Now we are just about to start with myproject 1.8 and we do not know how to start with it in the subversion control
as then myproject 2.0 will also come soon.

Structure:
Path : C:\projects\myproject

As you can see in the picture..the NV1.6code directory has version 1.6 code and all the directories outside are the version 1.7 code..

Not a Good Idea?
i don thin this will be a good idea

AIM: How do i make the above mess proper?
please help me how do i make the best use of tortoise SVN in my case to maintain
version

  1. myproject version 1.6 ( then the subversion like 1.6.1 , 1.6.2, 1.6.3)
  2. myproject version 1.7 ( then the subversion like 1.7.1 , 1.7.2, 1.7.3)
  3. myproject version 1.8 ( then the subversion like 1.8.1 , 1.8.2, 1.8.3)
  4. then the future version myproject version 2.0
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    There are two ways to do this: using the branch or tag feature.

    In general, I like using tag for specifying a release point and development continues on in a relatively linear fashion (1.6 goes to 1.7, 1.7 to 1.8, etc.)

    However, if for some reason say you released 1.6 and main development went to 1.7, but you wanted to keep making small changes to 1.6 (like 1.6.1, 1.6.2, etc.) it may be beneficial to create a branch.

    It’s also perfectly fine to use both features together.

    • 0