On 2008-09-11, Dirk Mueller wrote:
> ...
> I think what is missing here is regular snapshots of things that should be 
> used for /trunk development, and a timeline on when they're required (e.g. 
> only on mondays). 

I the mean time, until a thorough policy is fleshed out, would it
be possible to have a simple single file easily parsable list of
dependencies and their associated versions inside KDE trunk?

--markc
_______________________________________________
release-team mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/release-team

Reply via email to