[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-core-devel
Subject: Re: makefile -f Makefile.cvs aborts with compile_kpilot does not
From: Unai Garro <Unai.Garro () ee ! ed ! ac ! uk>
Date: 2004-01-18 16:53:29
Message-ID: 200401181653.36129.Unai.Garro () ee ! ed ! ac ! uk
[Download RAW message or body]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>
> How about using a little common sense at least?
> For about three weeks all development in kdepim took part in a separate
> branch. All new features were added there. Now all kdepim developers need
> to merge their commits from osnabrueck_branch to HEAD.
Excuse me,but I can't say you're really right, or other pim devels don't think
the same way.
I went to #kontact to complain about some build bugs in HEAD, and I asked why
nobody tested if HEAD built, being HEAD that was to be released, not
osnabrueck. HEAD was really broken when I cvs up'ed.
Somebody replied that a few devels did actually test HEAD instead of
osnabrueck. And everybody seemed to agree that osnabrueck wasn't going to be
out.
AFAICT, osnabrueck_branch breaks the freeze rules adding new features (like
spamassassin stuff).
I'm not sure what was merged back to HEAD, but new features shouldn't be. And
if not, the rest has_not_been_really_tested in HEAD. Only in the other branch
with new features, and who knows who persons testing.
Just my 2 cents
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFACroKWWqN9n50+ToRAgjOAKCuPYj4f8EjTKaadI5o9CxnDMJ9AQCfQZ8w
ROVoTH8W94bodC0GRY1nlzo=
=YlJJ
-----END PGP SIGNATURE-----
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic