Re: The nature of the Bonobo freeze.
- From: Maciej Stachowiak <mjs eazel com>
- To: Miguel de Icaza <miguel helixcode com>
- Cc: gnome-components-list gnome org
- Subject: Re: The nature of the Bonobo freeze.
- Date: 22 Oct 2000 15:51:00 -0700
Miguel de Icaza <miguel helixcode com> writes:
>
> The freeze we had agreed on was an API freeze, not a bug fix freeze,
> nor an improvement freeze. That was the extent of the promise we made
> because Eazel insisted on a promise.
>
> My list includes only bug fixes, and the only API breakage from the
> Nautilus perspective is the few lines that need to be removed from
> your code (streams).
>
> Then again, as I said, software releases slip as I said before, so I
> am not sure that promising anything in the context of software release
> schedules makes any sense.
>
> It strikes me as odd to have to `promise' something in the context of
> software releases. If the software is not ready, I can not release
> the code. I do not want to see Bonobo 1.0 be another GNOME 1.0, I
> learned from the past mistakes.
>
> Now, as I said before, I told Andy on the phone that we would change
> the Stream interface, we just did not have the time to put Dietmar's
> changes in on schedule. Too bad, because they were really important.
>
> It is not like I have `deceived and betrayed' anyone here. I am just
> doing my job.
Are you saying you did not mean your promise?
>
> I do not know why you insist on this branch. Until the software is
> ready to be branched, it will not be branched.
A branch is used to give an outlet for unstable changes that are not
needed for the release. If there is not a branch, there is a risk of
such changes getting checked in on the stable version.
- Maciej
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]