>> 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.
> Will this be a 1.3 blocker or is it possible that we start the same dicussion
> when we want to release it and this will be moved somewhere till eternity? I
> mean it's absolutely unusal to have no update path between minor releases and
> everybody should know that (and the big QA effort) before we start developing
> this software.
Nils, what I am trying to say is that most people seem to be thinking of an
upgrade path as a feature.
<rant>
While drafting the new governance proposal, an obligation on the developers to
have changes and commits take upgradeability into account (next to providing
quality of code, testing etc.) was removed. This to me is another indicator
that many of us are (sadly) still going for features rather than for enterprise
attributes such as stability, robustness or upgradeability. I am confident that
this will change as soon as more committing institutions feel the pain of going
through update scenarios.
</rant>
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.
Tobias
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________