On 27.05.11 09:22, Tobias Wunden wrote:
Again, I am not at all proposing to drop design and implementation
work on proper upgrade functionality. All I am saying is that
currently, the upgrade path is seen as a feature, and features can be
dropped from a release. As long as nobody is willing to put in the
effort and make that functionality happen, declaring the lack thereof
as a release blocker is not changing anything but holding up the
release forever.
I understood but I disagree. Like edit metadata, an update path is from
my 8 years experience of open source lecture recording system
development and operation (sometimes also consulting) for most potential
adopters a basic functionality and not a feature.
But as always in the area of strategic things, there're more always more
than one oppinion and we will only see in the long run who's right.
Nils
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________