Just a note that, with a manual SQL workaround, this issue has been
deprioritized to critical and reassigned to 1.3.

Chris

On Thu, 26 May 2011 09:37:57 -0600 Christopher Brooks
<[email protected]> wrote:

> Hi,
> 
> I'm afraid I don't have a proposal, I'm just trying to solicit
> discussion on what expectations are.  At the moment I would prefer to
> ignore upgrade and just chalk it up to being in a phase of rampant
> innovation.
> 
> Then down the road I would probably be in favour of standardizing on
> the media package - that is, media package zip files should be
> backwards compatible, rest endpoints should be backwards compatible,
> and that's it.
> 
> I look forward to hearing more from others...
> 
> Chris
> 
> > I've read a lot of opinions here, but no proposals yet for getting
> > from point A to point B.  When we have a large, cross cutting
> > project such as this, we need to first understand the scope, then
> > plan, then execute.  I hear that many of us are anxious to execute,
> > but at this point, we don't even understand the scope of what's
> > needed to make migration possible.
> > 
> > I'm looking forward to reading a detailed proposal, such as [1],
> > that describes the scope of the changes necessary, any dependencies,
> > committed resources (developers, designers, QA, etc), and the
> > timeline for implementing version migration.  Once such a proposal
> > is on the table, we can vet it against the authz and distribution
> > related tasks that have already been scheduled for a 1.3 release.
> > 
> > [1]
> > http://opencast.jira.com/wiki/display/MH/iTunesU+and+Youtube+Distribution+Project
> > 
> > Josh
> > 
> > On May 26, 2011, at 1:54 AM, Wunden Tobias wrote:
> > 
> > > Hi Rüdiger,
> > > 
> > > I couldn't agree more with your assessment. Not providing an
> > > upgrade path is unacceptable for a piece of enterprise software
> > > like Matterhorn. We can still claim to be young, but that won't
> > > hold for lang and doesn't buy as anything, certainly not adopters.
> > > 
> > > My proposal is to focus on upgrade strategies in 1.3, but not hold
> > > back 1.2 because of the current lack thereof. The problem we are
> > > looking at right now is only *one* of many possible in an upgrade
> > > scenario, so if we fix the workflow ids, there's likely other
> > > database issues that will show up next.
> > > 
> > > Tobias
> > > 
> > > On 26.05.2011, at 10:43, Ruediger Rolf wrote:
> > > 
> > >> I created it as a release blocker because I think it is one. Our
> > >> system currently is very ungraceful to early adopters (like us in
> > >> Osnabrück here) because the is no quick update from one release
> > >> to the other. But there was the promise that we could at least
> > >> reingest (and reprocess) all existing media. Currently we can not
> > >> even do this.
> > >> 
> > >> I will for sure not use or install 1.2 because of the missing
> > >> simple upgrade (without reprocessing) it would be impossible to
> > >> upgrade within a semester. And until our next semester 1.3 or
> > >> even 1.4 should be available. So I don't mind when we change
> > >> this. But in the meantime we should warn users that there is no
> > >> upgrade possibility (at least not without manually refactoring
> > >> every mediapackage) from 1.1 to 1.2 or even later versions. And
> > >> even if I refactor the mediapackages I may run into problems
> > >> because the URLs of the files and the engage player that I may
> > >> have linked somewhere, will have changed.
> > >> 
> > >> As Olaf pointed out some weeks ago, that we don't have the
> > >> possibility for the easy upgrade is hard to explain, but that
> > >> there is not even a chance of upgrading for a regular user is not
> > >> to explain at all I guess.
> > >> 
> > >> Regards 
> > >> Rüdiger
> > >> 
> > >> Am 25.05.2011 13:47, schrieb Rubén Pérez:
> > >>> Should it be a release blocker?
> > >>> 
> > >>> Short answer: YES, ABSOLUTELY
> > >>> 
> > >>> Long answer: I cannot think of a serious mature system that does
> > >>> not allow their users to upgrade versions keeping the data they
> > >>> already had on it. Matterhorn does NOT. Therefore, I infer that
> > >>> it is either not serious or not mature. I can not imagine how we
> > >>> can seriously expect any institution to adopt matterhorn knowing
> > >>> they will have to reprocess their whole collection if they want
> > >>> to upgrade the system. And this is more important than ANY
> > >>> feature anyone could want to upgrade for.
> > >>> 
> > >>> Regards,
> > >>> Rubén
> > >>> 
> > >>> 2011/5/24 Christopher Brooks <[email protected]>
> > >>> We can't reingest previous media into a new system as discussed
> > >>> in the team meeting (MH-7769).  Nejcs is looking at a work
> > >>> around but in the meantime I would like to pose the question as
> > >>> to whether this should be an RB.  In short I'm asking whether
> > >>> it is the expectation of a minor version that media packages
> > >>> from another system could be ingested.
> > >>> 
> > >>> Comments welcome...
> > >>> 
> > >>> Chris
> > >>> 
> > >>> --
> > >>> Christopher Brooks, BSc, MSc
> > >>> ARIES Laboratory, University of Saskatchewan
> > >>> 
> > >>> Web: http://www.cs.usask.ca/~cab938
> > >>> Phone: 1.306.966.1442
> > >>> Mail: Advanced Research in Intelligent Educational Systems
> > >>> Laboratory Department of Computer Science
> > >>>    University of Saskatchewan
> > >>>    176 Thorvaldson Building
> > >>>    110 Science Place
> > >>>    Saskatoon, SK
> > >>>    S7N 5C9
> > >>> _______________________________________________
> > >>> Matterhorn mailing list
> > >>> [email protected]
> > >>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
> > >>> 
> > >>> 
> > >>> To unsubscribe please email
> > >>> [email protected]
> > >>> _______________________________________________
> > >>> 
> > >>> 
> > >>> _______________________________________________
> > >>> Matterhorn mailing list
> > >>> 
> > >>> [email protected]
> > >>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
> > >>> 
> > >>> 
> > >>> 
> > >>> To unsubscribe please email
> > >>> 
> > >>> [email protected]
> > >>> 
> > >>> _______________________________________________
> > >>> 
> > >> 
> > >> 
> > >> -- 
> > >> 
> > >> ________________________________________________
> > >> Rüdiger Rolf, M.A.
> > >> Universität Osnabrück - Zentrum virtUOS
> > >> Heger-Tor-Wall 12, 49069 Osnabrück
> > >> Telefon: (0541) 969-6511 - Fax: (0541) 969-16511
> > >> E-Mail: 
> > >> [email protected]
> > >> 
> > >> Internet: 
> > >> www.virtuos.uni-osnabrueck.de     
> > >> _______________________________________________
> > >> Matterhorn mailing list
> > >> [email protected]
> > >> http://lists.opencastproject.org/mailman/listinfo/matterhorn
> > >> 
> > >> 
> > >> To unsubscribe please email
> > >> [email protected]
> > >> _______________________________________________
> > > 
> > > _______________________________________________
> > > Matterhorn mailing list
> > > [email protected]
> > > http://lists.opencastproject.org/mailman/listinfo/matterhorn
> > > 
> > > 
> > > To unsubscribe please email
> > > [email protected]
> > > _______________________________________________
> > 
> > _______________________________________________
> > Matterhorn mailing list
> > [email protected]
> > http://lists.opencastproject.org/mailman/listinfo/matterhorn
> > 
> > 
> > To unsubscribe please email
> > [email protected]
> > _______________________________________________
> 
> 
> 



-- 
Christopher Brooks, BSc, MSc
ARIES Laboratory, University of Saskatchewan

Web: http://www.cs.usask.ca/~cab938
Phone: 1.306.966.1442
Mail: Advanced Research in Intelligent Educational Systems Laboratory
     Department of Computer Science
     University of Saskatchewan
     176 Thorvaldson Building
     110 Science Place
     Saskatoon, SK
     S7N 5C9
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to