0
 Followers
1
 Like

Extend the support Tag format in LifeTime

Lifetime
New

Currently, in Lifetime, as far as I know, it's only possible to tag an application with the format "[Major].[Minor](.[Revision])", but, except for the Major and Minor, it is not easy to apply it to our development.

Example, we have Application A with version 2.0.1 and Application B with version 2.0.1.

App A depends on App B

Someone changes something on App B and only needs to republish (without opening modules) the App A.

During the night, a solution runs, and unexpectedly creates versions of modules for App A.


So, now we have App B tagged with 2.0.1 and App A with 2.0.1+

Lifetime makes us tag App A to 2.0.2, but nothing was changed except for the platform that created a nes version of the module.

If we had the chance to tag to 2.0.1.1, then it would be easier for us to track down the releases.

So, I suggest to extend the tag format to at least one more level


Thank you,

Nelson

 

Created on 23 Nov 2018
Comments (1)

Changed the category to Lifetime


Hi Nelson,


Thanks for sharing your idea.


Please give me more details regarding this topics:

  1. "Application B with version 2.0.1." (...) "Someone changes something on App B"(...) "now we have App B tagged with 2.0.1".  I should have the App B with 2.0.1+ after changes.
  2. "During the night, a solution runs, and unexpectedly creates versions of modules for App A." Can you please give us more details? The solution is in the Service Center which is creating a new module version?


Thank you!

views
127
Followers
0