Roadmap
-
FS-lite
See #9818 for a more detailed description.
Demo 1 (January)
- Import and visualization of all data directly from original files using Bio-Formats
- including support for big images and HCS data
- Downloading of original files
- Linux-only
Demo 2 - #10310 (February)
- Sprint whiteboard
- Support for Windows
- UI feedback during upload
- Server-side paths shown in Web and Insight UIs.
- Added tile support to trestle
- Improved delete functionality
- Tagged as "v.5.0.0-alpha1": ice33 and ice34
- Limitations:
- change group functionality has been removed for alpha1
- NDPI should be avoided
- You will need to create a new database; no upgrade script is available
Demo 3 (April)
- Sprint whiteboard
- Github milestone
- Rendering speed-up by caching Bio-Formats setId state (#10535)
- Capture server-side import logs (#9827/#10676)
- Reworking of checksums from the client to the DB
- On-the-fly generation of the original_metadata.txt info
- Import "time remaining" estimate
- Tagged as "v.5.0.0-alpha2" (no builds)
- Limitations:
- change group functionality still disabled
- You will need to create a new database; no upgrade script is available
Demo 4.1 - #10771 (May)
- Sprint whiteboard
- Github milestone
- Re-enabled chgrp
- Chgrp and delete updated to work with multi-image filesets (MIFs)
- Tagged as "v.5.0.0-alpha3": ice33 and ice34. See also: snapshots the 5.0.0-alpha3 snapshots.
- Limitations:
- You will need to create a new database; no upgrade script is available
- Performance issues during chgrp and delete.
Demo 4.2 - #10863 (May)
- Sprint whiteboard
- Github milestone
- delete/chgrp of MIF
- Adjust workflow (client)
- Performance review (server)
- Turn off MIF display introduced in Web
- Import workflow review:
- add upload/processing steps
- Improve UI and feedbacks.
- Tagged as "v.5.0.0-alpha4" ice33 and ice34. See also: snapshots the 5.0.0-alpha4 snapshots.
- Limitations:
- Cancellation of folder import.
- Log files display.
- Submit server log with failed import.
- MIF chgrp/delete not supported in insight.
Demo 4.3 - Big push (June)
- Sprint whiteboard
- Submit to QA
- MIF delete/chgrp. Check before.
- Plate import focus
- Bug fixing
- Limitations:
- Export as OME-TIFF broken
- Black thumbnails (insight) after apply to All
- Move/delete of Big plates
Demo 4.4 - Bug Fixing (June)
-
Sprint: FS Demo 2
Ended 4 months ago (from 02/01/13 00:00:00 to 02/27/13 15:00:00)
Go to the Sprint Backlog for this sprint or visit the ome page for statistics and team details
-
Sprint: FS Demo 3
Ended 2 months ago (from 03/15/13 00:00:00 to 04/19/13 15:00:00)
Go to the Sprint Backlog for this sprint or visit the ome page for statistics and team details
- solidification of the model, with a goal of having all schema changes in by the end of March;
- configurable checksum values;
- upload-and-forget imports in which all uploads take place before metadata goes in;
- server-side caching of rendering services, tiles, reader state, etc.;
- proper server-side log-file handling of imports;
- and re-enabling original_metadata download
Along with working on the multi-fileset issues discussed during demo 2.
-
Sprint: FS demo 4.x
Due in 12 days (from 04/19/13 00:00:00 to 07/01/13 19:00:00)
Go to the Sprint Backlog for this sprint or visit the ome page for statistics and team details
Backlog for demo 4.
0%
- Number of storie:
- Completed:
- 0
- In Progress:
- 1
- Open:
- 0
- Total:
- 1
-
Sprint: FS demo 4.1
Ended 6 weeks ago (from 04/30/13 00:00:00 to 05/10/13 00:00:00)
Go to the Sprint Backlog for this sprint or visit the ome page for statistics and team details
-
Sprint: FS demo 4.2
Ended 4 weeks ago (from 05/10/13 09:00:00 to 05/24/13 13:00:00)
Go to the Sprint Backlog for this sprint or visit the ome page for statistics and team details
-
Sprint: FS Demo 4.3
Ended 12 days ago (from 05/24/13 00:00:00 to 06/07/13 18:00:00)
Go to the Sprint Backlog for this sprint or visit the ome page for statistics and team details
Final push before the code freeze
-
Sprint: FS demo 4.4
Due in 5 days (from 06/07/13 00:00:00 to 06/25/13 00:00:00)
Go to the Sprint Backlog for this sprint or visit the ome page for statistics and team details
0%
- Number of storie:
- Completed:
- 0
- In Progress:
- 3
- Open:
- 0
- Total:
- 3
-
Next release in the 4.4 series after milestone:OMERO-4.4.9
-
Sprint: 2013-05-07 (8)
Ended 6 weeks ago (from 04/09/13 15:00:00 to 05/07/13 15:00:00)
Go to the Sprint Backlog for this sprint or visit the ome page for statistics and team details
-
Sprint: Blocker 4.4.9 (1)
Due in 12 days (from 05/09/13 00:00:00 to 07/01/13 15:00:00)
Go to the Sprint Backlog for this sprint or visit the ome page for statistics and team details
Blocker and critical bugs should be fixed in that sprint. Focus is still FS
-
-
Omero tickets that are waiting on external/third-party tickets. These tend to get rescheduled over and over again, and don't really have a home. This is their home.
-
- Before coming out of Beta:
- Produce a list of all libraries used with licenses
- Completely removing Pixels collections
- Getting rid of "Beta"
- What version number to use?
- Metadata, Delete, Permissions, "Temporary image" gone
- Before coming out of Beta:
-
Originally merged with milestone:Unscheduled (5-29-09)
Re-opened as a holding place for 4.4.0 tickets so that they won't get lost in "Unscheduled". After that, we'll go through "Unscheduled" and find the most important tickets and move them either here or to a concrete milestone.
-
-
4.4 series backlog. This "continuous milestone" is a container similar to the "Unscheduled" milestone but for work that is intended during the 4.4 series. See the various specific milestones for this release:
- milestone:OMERO-4.4
- milestone:OMERO-4.4.1
- milestone:OMERO-4.4.2
- milestone:OMERO-4.4.3
- milestone:OMERO-4.4.4
- 4.4.5 and 4.4.6 were released without separate trac milestones. See the github milestones:
- milestone:OMERO-4.4.7
- milestone:OMERO-4.4.8
The OMERO-4.4 line is dedicated to providing and supporting a stable, defined line of OMERO development, where several improvements can be delivered to the community alongside a stable API. In other words, the OMERO 4.4.x API will be retained and supported, as these updates are made, which will guarantee that external software that uses OMERO should not break. API additions may be made, but no API-breaking changes will occur. As appropriate, probably at intervals of ~3 months, we will release point releases (e.g., OMERO-4.4.5, -4.4.6, etc.) that combine completed functional improvements and bug fixes.
-
This Milestone is a separate placeholder for for the testing framework that shall be put into place for each release. The Milestone also addresses the ongoing improvements for the testing scenarios and general development for the process.
-
This milestone is a general placeholder for things that don't yet have a particular milestone associated with them.
The notes below serves as a general (and mutable) list of upcoming goals. Be sure to also look at OmeroNotes for more ideas on things to be implemented.
- Multiple server support in client
- Clustering support for improved up-time
- Names for rendering settings
- Improved search
- auto-upgrade of clients (JWS, IcePatch?, ...)
- original file archiving
- possibly unneeded with server-side import and bioformats offsets
- Next language binding: .NET, Objective-C
- Re-import functionality
- Preferences for Client
- Preferences for Server
- Real Analysis : wnd-charm, farsight, etc.
- Some simple out-of-the-box analysis: segmentation, registration, ...
- HDF
- Matlab
- WWW FAQ
- Improve community : Forums and possibly converting mailing list. Jabber server, etc.
- Flexibility of dimension order
- XZ slices
- Multifield support
- Versioned metadata : Use of Envers, rolling back student mistakes, etc.
- Parsing protocols into RDF
- ImageJ screencast
- Thumbnails in wiki/markup
- Storing all key-value pairs parsed by Bio-Formats
- ImageHistory? for series
- Streaming import
-
The purpose of this rolling milestone is to act as a placeholder for gathering information on the existing use of the software, the users and their workflows for the upcoming milestone work.
The information from this milestone has been put into place to serve the development process in two ways.
- 1) To aid/support the requirements for the start of each milestone of development.
- 2) To provide supporting software feedback reviews - information that needs to be accounted for during a development process.
The OMERO process page covers both these aspects further see Generic Process Process template.
-
This milestone is for activities/collaborations that we are currently putting in place
