Project

General

Profile

Actions
Copy link

Feature #42391

closed

Make version number increase optional

Added by Oliver Salzburg about 12 years ago. Updated about 12 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
Extension Manager
Target version:
-
Start date:
2012-10-25
Due date:
% Done:

100%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

I don't understand why a TER upload enforces a version number increase.
This leads to the fact that our TER uploads always have incorrect version numbers.

Actions
Copy link
 #1

Updated by Ingo Renner about 12 years ago

  • Status changed from New to Rejected
  • % Done changed from 0 to 100

Hi Oliver,

Every new upload means a change and thus requires a new version number. We already head people uploading different versions of an extensions (= changed code) under the same version number. That is really hard to track. In the end it's just a number.

Here's some more explanation on version numbering that might help you to understand the concepts: http://en.wikipedia.org/wiki/Software_versioning

Actions
Copy link

Also available in: Atom PDF