gideon alpha 4...

[Caleb Tennis]

> so what about announcing a tar.bz2 package of gideon once a week, which is
> guaranteed to build, so that people don´t accidently checkout a "broken"
> cvs version just between two commits from somebody, which belong together,
> that doesn´t compile.

One thing that may work as well is to keep a floating cvs tag, like 
latest_stable, or something like that, that gets updated regularly to 
something that's known to work.  Packages could be based off of that tag, as 
well.

> as i am on a gentoo system, the "release" process is as much as adapting a
> single text file in less than two minutes, so i guess there is no need to
> bother the real packagers with this.

yeah, I'm a gentoo user too.  Perhaps an ebuild based on Dan Armak's kde-cvs 
ebuild set would be a good starting point?

> of course i don´t have any voting rights on a feature freeze, but i´ll tell
> you my opinion anyways ;-)

Every opinion counts!

> i think gideon should go on progressing exactly as it is now, without the
> burden of a feature freeze, where nobody can commit new stuff for a longer
> time, i think the stability is taken care of, as people are using gideon on
> a day to day base.

We'll go until everyone is happy with the current feature set or kde head goes 
into feature freeze, whichever comes first.

Caleb