From: <bar...@t-...> - 2002-12-02 23:50:29
|
hi there, > > a quick glance at the calendar should remind us all that we have somehow > > managed to reach December 2002, the target date announced for the 1.0 > > release in our famous xine teaser trailer. i've never authorized that date but who knows, maybe xine will really make it to 1.0 this month though i'll only believe it when i see it. > > Fortunately, things actually look like xine could become stable this > > month: A glance at the TODO file shows "only" bugfixes and smaller > > enhancements. There are a few new features in the "optional" list, but > > even those are only limited to certain modules. there are some tasks which need to be done which are not found in the todo list: - fix the homepage - fix documentation are two of them. i think the new homepage, in it's half-finished state is really embarrassing - i'm thinking about setting an ultimatum here - if nobody fixes it until next week i'll fix it - and my fix will look remarkably like the old homepage which might not have been as stylish as the new one but at least it was closer to html and it was working and manageable. > > Bottom line: The public API seems stable and, after Michael's post plugin > > commit, feature-complete. though the api is far from being feature-complete it is hopefully at least extensible enough to serve the needs for the near future. > > Therefore, I propose a "feature chill" after the next release, which means > > that only those features mentioned in the TODO file should be added. > > Any ojections? not sure what a feature chill is but i think it doesn't make that much sense. if you want a feature freeze i propose to create a stable branch in cvs on that date so those developers who work on "progressive" stuff can continue their work. besides that i think at least new plugins should be allowed to be added. of course the time for big architecture changes is over now. cheers, guenter -- Basic research is what I'm doing when I don't know what I'm doing. - Warnher Von Braun |