Can a feature be superseded by more than one new feature?

[Carlsson, Joakim (Nexer AB)]

Hi I have feature that is done and deployed.

Let's say deployed in version1.0.

It will be an extension of it for in version2.0. So a new feature is created that contains specific requirements for version 2.0.

Meanwhile, a third feature is under development that shall be applied in version3.0.

So:

Feature1 - version1

Feature2 - version2

Feature3 - version3

The requirements in F2 and F3 are independent of each other. The features 2 and 3 are worked on in parallell but for different deploy-versions. Eventually in the future they will be conformed into a version4.0.

Q: Is it ok to let Feature1 to be superseded by Feature2 AND Feature3? Or, must it be a chain? I.e F1 --> is superseded by F2 --> is superseded by F3?

/Br Joakim

[Nikola Perisic]

Hi @Carlsson, Joakim (Nexer AB) 

You have the option to merge two versions into one, if this is something that you want to accomplish.

[Carlsson, Joakim (Nexer AB)]

Hi Nikola and Thanks :-)

I can perform merge manually quite easily if so. What I was wondering was whether you should always have a chain of supserseded feature? Or if it is ok to have one feature superseded by two other ones?

A chain sounds more clean and logical. But practical reasons due different timetables cause problems with that.

[Nikola Perisic]

@Carlsson, Joakim (Nexer AB) 

This depends on what you are trying to accomplish.