What is Refactoring in the context of software versioning?

[Noorul Hameed]

Dear Author,
A Refactor method means Restructuring of logical structure in code.

For e.g. Software Version 1, and Version 2 are produced.
Method: Change of 1 class in Version 2 only.
Suppose in Version 2

class AA

needs to be existed as

class AAAA

How should it be applied for version 1 & 2 and its dependencies too?
Simply i need to confirm,
Does it mean class AA in Version 1 too?

Thank you

[Tim Cooke]

Any code change results in a new version. Even if the only change was the renaming a method that has no functional impact on the product behaviour it would result in a new version.

[Tim Cooke]

I should clarify on what I define as a version.

When you build your application into a deployable artefact, such as a jar in the case of a Java application, that is a versionable artefact.

For example

I build my code and call the resulting jar Version 1.0

I make a bunch of changes to my code

I build my code and call the resulting jar Version 2.0

Does that answer your question?

[Campbell Ritchie]

Tim Cooke wrote:. . .
I build my code and call the resulting jar Version 1.0

I make very few changes to my code

I build my code and call the resulting jar Version 1.01

Or something like that.

[Tim Cooke]

Ah well now we're getting into a separate topic of versioning schemes. I like to use Semantic Versioning.

[Noorul Hameed]

Tim Cooke wrote:I should clarify on what I define as a version.

Does that answer your question?

Yes