This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C0E8E8.DD9B5458 Content-Type: text/plain; charset="iso-8859-1" -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is the KOffice development team in the habit of creating a maintenance branch? If so, at which point is 1.1 branched from the HEAD? During the 1.1 freeze there are likely to be developers working on new stuff that could still be integrated. The only extra work is that any patches must be applied to both the 1.1 branch, and the HEAD. Of course, it may make sense to branch only after RC1 is released, in order to minimise any double patching. Just some thoughts... MikeA >> -----Original Message----- >> From: David Faure [mailto:david@mandrakesoft.com] >> Sent: 30 May 2001 08:55 >> To: koffice@kde.org; koffice-devel@kde.org; kde-i18n-doc@kde.org >> Subject: KOffice release schedule updated >> >> >> Here's a proposal for the schedule of the next koffice releases : >> (also available on >> http://developer.kde.org/development-versions/koffice-1.1-rel >> ease-plan.html) >> >> This schedule plans a beta 3, a release candidate, and then >> 1.1-final, >> with a translated-message freeze of ... hmm, 2 months (maybe >> that's longer >> than necessary ?). >> >> KOffice 1.1 Beta 3 >> ============== >> >> * Monday June 11 >> The HEAD branch of KOffice is frozen : no new features, bugfixes >> commits only, no commit that modifies an application's behaviour, >> and **message freeze**. This freeze will last till the release of >> KOffice 1.1! >> >> * Monday June 18 >> The HEAD branch of CVS is tagged KOFFICE_1_1_BETA3, and >> tarballs are made. >> They are made public immediately, and given to packagers for >> creation of binary packages. >> >> * Monday June 25 >> Announce KOffice 1.1 Beta 3 >> >> KOffice 1.1 Release Candidate >> ======================== >> >> * Monday July 9 >> KOffice goes into deep-freeze. All commits should be posted for >> review first. >> >> * Monday July 16 >> The HEAD branch of CVS is tagged KOFFICE_1_1_RC1, and >> tarballs are made. >> They are made public immediately, and given to packagers for >> creation of binary packages. >> >> * Monday July 23 >> Announce KOffice 1.1 Release Candidate >> >> KOffice 1.1 final >> ============= >> >> * Sunday August 5 >> Last day for translations, documentation, icons and critical >> bugfixes commits. >> >> * Monday August 6 >> The HEAD branch of CVS is tagged KDE_2_2_RELEASE and the day >> is spent testing >> the release a final time. >> >> * Tuesday August 7 >> The tarballs are made and released to the packagers. >> >> The rest of the week is spent testing the tarballs, >> packaging and writing the >> announcement and changelog. >> >> * Friday August 10 >> The source and binary packages are uploaded to ftp.kde.org >> to give some time >> for the mirrors to get them. >> >> * Monday August 13 >> Announce KOffice 1.1. >> >> Feedback welcome ! >> >> -- >> David FAURE, david@mandrakesoft.com, faure@kde.org >> http://perso.mandrakesoft.com/~david/, http://www.konqueror.org/ >> KDE, Making The Future of Computing Available Today >> -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 6.5.3 for non-commercial use iQA/AwUBOxS5iHympNV/C086EQKqnQCg/e72+DmiQ2CRE2HIYah21imOZRsAn1SO RIZOP+PS32YeZdJhnufKTbAM =yoHX -----END PGP SIGNATURE----- ------_=_NextPart_001_01C0E8E8.DD9B5458 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: KOffice release schedule updated

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Is the KOffice development team in the habit of creating = a
maintenance branch?  If so, at which point is 1.1 b= ranched from the
HEAD?  During the 1.1 freeze there are likely to be= developers
working on new stuff that could still be integrated.&nbs= p; The only extra
work is that any patches must be applied to both the 1.1= branch, and
the HEAD.  Of course, it may make sense to branch o= nly after RC1 is
released, in order to minimise any double patching.

Just some thoughts...


MikeA


>> -----Original Message-----
>> From: David Faure [mailto:david@mandrakesoft.com]
>> Sent: 30 May 2001 08:55
>> To: koffice@kde.org; koffice-devel@kde.org; kde= -i18n-doc@kde.org
>> Subject: KOffice release schedule updated
>>
>>
>> Here's a proposal for the schedule of the next = koffice releases :
>> (also available on
>> http://developer.kde.org/devel= opment-versions/koffice-1.1-rel
>> ease-plan.html)
>>
>> This schedule plans a beta 3, a release candida= te, and then
>> 1.1-final,
>> with a translated-message freeze of ... hmm, 2 = months (maybe
>> that's longer
>> than necessary ?).
>>
>> KOffice 1.1 Beta 3
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> 
>> * Monday June 11
>> The HEAD branch of KOffice is frozen : no new f= eatures, bugfixes
>> commits only, no commit that modifies an applic= ation's behaviour,
>> and **message freeze**. This freeze will last t= ill the release of
>> KOffice 1.1!
>> 
>> * Monday June 18
>> The HEAD branch of CVS is tagged KOFFICE_1_1_BE= TA3, and
>> tarballs are made.
>> They are made public immediately, and given to = packagers for
>> creation of binary packages.
>> 
>> * Monday June 25
>> Announce KOffice 1.1 Beta 3
>> 
>> KOffice 1.1 Release Candidate
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D
>> 
>> * Monday July 9
>> KOffice goes into deep-freeze. All commits shou= ld be posted for
>> review first.
>> 
>> * Monday July 16
>> The HEAD branch of CVS is tagged KOFFICE_1_1_RC= 1, and
>> tarballs are made.
>> They are made public immediately, and given to = packagers for
>> creation of binary packages.
>> 
>> * Monday July 23
>> Announce KOffice 1.1 Release Candidate
>> 
>> KOffice 1.1 final
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> 
>> * Sunday August 5
>> Last day for translations, documentation, icons= and critical
>> bugfixes commits.
>> 
>> * Monday August 6
>> The HEAD branch of CVS is tagged KDE_2_2_RELEAS= E and the day
>> is spent testing
>> the release a final time.
>> 
>> * Tuesday August 7
>> The tarballs are made and released to the packa= gers.
>> 
>> The rest of the week is spent testing the tarba= lls,
>> packaging and writing the
>> announcement and changelog.
>> 
>> * Friday August 10
>> The source and binary packages are uploaded to = ftp.kde.org
>> to give some time
>> for the mirrors to get them.
>>
>> * Monday August 13
>> Announce KOffice 1.1.
>>
>> Feedback welcome !
>>
>> --
>> David FAURE, david@mandrakesoft.com, faure@kde.= org
>> http://perso.mandrakesoft.com/~david/, http://www.konqueror.org/<= /FONT>
>> KDE, Making The Future of Computing Available T= oday
>>

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>

iQA/AwUBOxS5iHympNV/C086EQKqnQCg/e72+DmiQ2CRE2HIYah21imOZ= RsAn1SO
RIZOP+PS32YeZdJhnufKTbAM
=3DyoHX
-----END PGP SIGNATURE-----



_________________________________________________________________________ This e-mail and any attachments are confidential and may also be privileged= and/or copyright
material of Intec Telecom Systems PLC (or its affiliated companies). If yo= u are not an
intended or authorised recipient of this e-mail or have received it in erro= r, please delete
it immediately and notify the sender by e-mail. In such a case, reading, r= eproducing,
printing or further dissemination of this e-mail is strictly prohibited and= may be unlawful.
Intec Telecom Systems PLC. does not represent or warrant that an attachment= hereto is free
from computer viruses or other defects. The opinions expressed in this e-ma= il and any
attachments may be those of the author and are not necessarily those of Int= ec Telecom
Systems PLC.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
__________________________________________________________________________<= BR> ------_=_NextPart_001_01C0E8E8.DD9B5458--