As we are about to cut a release candidate for 1.2 within this week, I was 
wondering what would happen to all the remaining 1.2 stories. So I went through 
them, moved some to 1.3 and removed the fix version for many of them but listed 
them below so they don't get lost. Most of the stories were unassigned and 
without specific tasks anyway. 

Feel free to assign new fix versions for them, but please remember that there 
needs to be commitment from someone to get it done first. Also, don't forget 
that we have 3 weeks to get it done, I would assume that these 3 weeks start on 
June 1st. I noticed that some people were using 1.2 as a kind of backlog for 
"everything related to x that needs to get done soon". I propose to use tags 
and/or components instead of versions.

Please note that there are many tasks and bugs that need to be rescheduled, 
too, and I would like to invite everybody to take a look at them, it's still 
more than 100 for 1.2!

Removed fixed version:
===

MH-7190 - As a configurer, I need to set whether recordings with no series will 
be open or closed by default

MH-7099 - As an admin, I need to manually order my episodes, so they appear 
correctly

MH-6966 - As an adopter/configurer, I need to know what hardware is required to 
run Matterhorn for a small and moderately sized deployment.

MH-6965 - As an adopter/configurer, I want a clear understanding what streaming 
options work with Matterhorn and their performance with the Engage Tools.

MH-7190 - As a configurer, I need to set whether recordings with no series will 
be open or closed by default

MH-6918 - As an admin, I want to see (and be able to edit) only recordings that 
I am responsible for

MH-6917 - As a configurer/sys admin/administrator, I want to monitor the status 
of the overall system

MH-6916 - As an administrator, I want to attach comments or notes to the media 
package so that in a shared working enviroment co-workers can relate to this 
information for further workflows/processing

MH-6915 - Refined trimming, trim excerpts

MH-6914 - As an administrator, I want to make use of my distributed environment 
and have failed workflows change over to another server

MH-6912 - As an administrator, I want basic distribution channel statistics for 
my delivered media

MH-6910 - As an administrator, I want to see and manage (sort, order, search) 
all the DC metadata files so I can re-use them for either adjustments or re-use 
(metadata templates)

MH-6909 - As an administrator, I want to see and manage (sort, order, search) 
all the track files ingested in order to re-ingest them

MH-6903 - As an admin, I need to specify that any piece of metadata become a 
tag or an rss feed

MH-6902 - As an administrator, if I am distributing to iTunes, I need to be 
able to select from a list of iTunes categories

MH-6864 - As an admin, I want to be kept abreast of the progress of lengthy 
activities that are happening in the background

MH-6855 - As an administration, I need to see the processing queue

MH-6836 - As an configurer, I need to configure automated error handling in 
workflow definitions

MH-5842 - As an admin, I need to republish my media with captions

MH-5526 - We need VM images for easy testing

MH-5459 - As an admin, when I update a series, its distributed recordings 
series metadata should be updated.

MH-5393 - As an administrator, I need to set a delay on the publishing of a 
recording so that the instructor is comfortable with webcasting his class

MH-5387 - Improve Engage Visual Design (Conceptual Framework)

MH-5341 - As a configurer, I want to persist "controlled vocabularies" via a 
metadata service, so the my UI's can use enumerated lists.

MH-4817 - As an administrator I need to know what distribution channels 
succeeded regardless of whether the workflow succeeded

MH-4627 - As an admin, I need to recover from a lecture that failed to start 
capturing

MH-4626 - As an admin, I need to recover from a lecture that failed while 
capturing.

MH-4406 - As an admin, if my media package is missing required metadata, I want 
the opportunity to add it via a hold state.

MH-4207 - As an admin, I want to know when capture agent last sent a status and 
whether it is still online.

MH-4090 - As an administrator I need to be able to edit the metadata for a 
series

MH-4081 - As an admin, I want to specify which distribution channels I want to 
deliver content to.

MH-3639 - As an administrator, I need to know about the successes of a previous 
instance (parent workflow) of a (partially) failed recording

MH-3367 - As an administrator, I need to ingest manually captured media for a 
scheduled recording

MH-3283 - As an administrator, I need to be able to add values for the full set 
of metadata specified as "Opencast Core"

MH-3074 - As an admin, I want to be alerted when there are problems with 
capture agents or recordings

MH-2811 - As an Admin, I need to republish recordings to Matterhorn Media 
Module with updated media and metadata.

MH-2711 - As an administrator, I need to be able to view (with a single click) 
a recording in its distributed state, so I can be confident it has been 
distributed successfully

MH-2673 - As an administrator, I want to know the status of the capture agents 
that will be used for upcoming recordings

MH-2669 - As an administrator, I need to schedule a capture agent to start 
capturing now

MH-2647 - As an administrator, I want to filter my Recordings page to show only 
recordings for a specific date range

MH-2580 - As an administrator I want to know what recordings are coming up for 
a particular capture agent

MH-2578 - As an administrator, I need to see what inputs are being captured for 
a particular recording

MH-1925 - As an administrator, I need to know (when scheduling) if my choice of 
inputs impacts my potential distribution channels

MH-1256 - As an administrator I need to schedule a course or an individual 
recording for manual submission
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to