--===============2030530229==
Content-Type: multipart/signed;
  boundary="nextPart2925099.YfNGcbsK9h";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

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

On Wednesday 22 February 2006 15:26, Sander Koning wrote:
> Raphael Langerhorst wrote on 2006-02-22 12:50 +0100 regarding KOffice=20
documentation changes during freeze:
> > * Do not allow ANY message documentation changes during documentation
> > freeze * Have two doc freeze dates: one for content, and a later one for
> > fixes. Sth like: 5 weeks before release is documentation content freeze
> > (bugfixes allowed) and 2-3 weeks before release is total freeze, no
> > bugfixes allowed. As release we should use the RC1 as this should be...
> > "the release as it should be".
> >
> > Any opinions? If I don't get any reply I would suggest to go for option
> > 2, and I'll (hopefully) take care that we get this down in the next
> > release schedule.
>
> I'm in favour. Make the freeze dates clear and reasonable, and I think th=
at
> no-one will object. At least, I hope so ;)

Yes, let's codify it this way.

=2D-=20
Boudewijn Rempt=20
http://www.valdyas.org/fading/index.cgi

--nextPart2925099.YfNGcbsK9h
Content-Type: application/pgp-signature

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

iD8DBQBD/Iy8daCcgCmN5d8RAqMcAJ9vMB7jmI4gl7/p3eTX6OK1Fs5uuwCfZmLk
9bPs6cfXOXBmALXrBsAPtcA=
=lAZP
-----END PGP SIGNATURE-----

--nextPart2925099.YfNGcbsK9h--

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

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel

--===============2030530229==--