Changes between Initial Version and Version 1 of Ticket #540
- Timestamp:
- Feb 6, 2014, 3:03:36 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #540
-
Property
Status
changed from
new
toassigned
-
Property
Milestone
changed from
Reggie v2.x
toReggie v2.15
-
Property
Status
changed from
-
Ticket #540 – Description
initial v1 1 1 BASE 3.3 include a lot of `JavaScript` changes which may affect the functionality in Reggie. Before releasing a Reggie version for BASE 3.3, we need to verify that all wizards works as expected. Issues that are found should either be fixed as part of this ticket or (depending on the amount of work needed) a new ticket should be created. 2 2 3 Also note that there are already some tickets for taking advantage of new functionality in BASE 3.3. 3 The first step is to make sure that Reggie works with both BASE 3.2 and BASE 3.3 (assuming that Content-Security-Policy has been relaxed on the BASE 3.3 server). 4 5 If Reggie 2.15 is released before BASE 3.3 we don't have to worry about upgrading to BASE 3.3. 6 7 Only if BASE 3.3 is released before Reggie 2.15 we can consider taking advantage of new functionality in BASE 3.3. 8 9 There are already some tickets for taking advantage of new functionality in BASE 3.3. 4 10 5 11 * #515: Store sequence for barcodes as annotations on tags