Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#1090 closed task (fixed)

Introduce FirstReleasedIn annotation

Reported by: Nicklas Nordborg Owned by:
Priority: major Milestone: Relax v1.4
Component: net.sf.basedb.relax Keywords:
Cc:

Description

It would be nice to know in which release an item was first included. It should be simple enough to define an annotation type FirstReleasedIn that is automatically set on new items by the release importer. If possible, it would be nice to have this annotation as an enumeration that is automatically updated with new release versions during the import.

Existing items need to be updated manually.

Change History (8)

comment:1 by Nicklas Nordborg, 6 years ago

(In [5176]) References #1090: Introduce FirstReleasedIn annotation

The FirstReleasedIn annotation type is now created by the installer. It is initially populated with existing release versions: 2.3, 2.4, 3.0, 3.1, 4.0

comment:2 by Nicklas Nordborg, 6 years ago

(In [5177]) References #1090: Introduce FirstReleasedIn annotation

Added the FirstReleasedIn annotation type to all categories.

comment:3 by Nicklas Nordborg, 6 years ago

(In [5178]) References #1090: Introduce FirstReleasedIn annotation

The release importer now adds the current release version to FirstReleasedIn if it is not already included.

comment:4 by Nicklas Nordborg, 6 years ago

(In [5179]) References #1090: Introduce FirstReleasedIn annotation

The FirstReleasedIn annotation is now set for new items.

comment:5 by Nicklas Nordborg, 6 years ago

(In [5180]) References #1090: Introduce FirstReleasedIn annotation

Removed unused code.

comment:6 by Nicklas Nordborg, 6 years ago

Resolution: fixed
Status: newclosed

comment:7 by Nicklas Nordborg, 6 years ago

(In [5239]) References #1090: Introduce FirstReleasedIn annotation

The cohort exporter should export the FirstReleasedIn annotation.

comment:8 by Nicklas Nordborg, 6 years ago

(In [5245]) References #1090: Introduce FirstReleasedIn annotation

The FirstReleasedIn annotation should not be exported by the Level3 exporter since it will be set by the regular importer on the Level3 server.

Note: See TracTickets for help on using tickets.