KDE Dev Platform Status

Matt Rogers mattr at kde.org
Tue Nov 27 02:42:43 CET 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Nov 26, 2007, at 12:08 PM, Thomas Zander wrote:

> On Monday 26. November 2007 17:53:17 Dirk Mueller wrote:
>> On Sunday 25 November 2007, Sebastian Kuegler wrote:
>>> We should tap into coolo's experience here. My proposal would be  
>>> to have
>>> one last BIC (but SC) monday. That should get us the critical
>>> stuff/fallout, and not break things. I hope.
>>
>> Aha. Why did we release the platform if we break BIC one last  
>> time? Either
>> we keep BC or we don`t.
>
> Why can be answered as 2 different things;
>
> 1) Because there are some showstoppers that can be fixed in a MUCH  
> better way
> when BC is ignored.
>
> 2) Because there is nobody 'out there' that will find it a really  
> big problem
> if we do break BC before we make a final release for the simple  
> reason that
> this exact released version will not be in any distro's official  
> release.
>

But we've already made a final release of the Dev Platform. *That's  
the whole point!*

> So, the real question is why not allow this for critical bugfixes.  
> (and those
> only, obviously or else we'll need one in 2 weeks again).
>

No, the real question is why can't people just show some restraint  
and live with what we got since they apparently couldn't be bothered  
to either get up and fix it before the release or let somebody know  
that they've got things they want to fix and ask for a small delay.

> ps. one such bug I'm thinking about is the kactioncollection one  
> (151421)
- --
Matt


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iD8DBQFHS3YTA6Vv5rghv0cRArj1AJ4mtU1owTU06Mg+mLQZ4YeeS+nctQCfRgkl
2hVHfLJ1YieHmbS+6Jg4Yfc=
=w0Pk
-----END PGP SIGNATURE-----


More information about the release-team mailing list