--===============0259385350==
Content-Type: multipart/signed;
	boundary="nextPart2161764.57YajEQKvk";
	 protocol="application/pgp-signature";
	 micalg=pgp-sha1


--nextPart2161764.57YajEQKvk
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Thursday 13 December 2007 18:25:16 Aaron J. Seigo wrote:
> > After 4.1, we should probably experiment with the 6 month release
> > schedule that seems to be working for other projects,
>
> for certain values of "working". for at least one major project, there
> was an immediate and noticeable decline in both mailing list traffic and
> commit rates when a 6 month cycle was adopted.

I would expect that when more developers start to become comfortable with=20
distributed srm systems (like git) this starts to be easier and we can=20
avoid such problems.
Therefor I think we should let the progress of people pushing their stuff=20
into repos, as they want, drive the strictness of our release schedule. And=
=20
vice versa.

In other words; let people get comfortable with the techniques and=20
technology to enable this much easier at a similar pace as we move to more=
=20
strict time-based releases.

=2D-=20
Thomas Zander

--nextPart2161764.57YajEQKvk
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBHYXmECojCW6H2z/QRAuo1AJ9DEB9WGZdv8s5lWBmxpO9iGdEVLACfT58f
Ic/xDtroHOGFgljL9LUaBYI=
=pHHX
-----END PGP SIGNATURE-----

--nextPart2161764.57YajEQKvk--

--===============0259385350==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

--===============0259385350==--