[prev in list] [next in list] [prev in thread] [next in thread]
List: koffice
Subject: RE: KOffice release schedule updated
From: "Michael Ansley \(UK\)" <Michael.Ansley () intec-telecom-systems ! com>
Date: 2001-05-30 9:14:01
[Download RAW message or body]
-----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 <http://www.pgp.com>
iQA/AwUBOxS5iHympNV/C086EQKqnQCg/e72+DmiQ2CRE2HIYah21imOZRsAn1SO
RIZOP+PS32YeZdJhnufKTbAM
=yoHX
-----END PGP SIGNATURE-----
[Attachment #3 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2650.12">
<TITLE>RE: KOffice release schedule updated</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>-----BEGIN PGP SIGNED MESSAGE-----</FONT>
<BR><FONT SIZE=2>Hash: SHA1</FONT>
</P>
<P><FONT SIZE=2>Is the KOffice development team in the habit of creating a</FONT>
<BR><FONT SIZE=2>maintenance branch? If so, at which point is 1.1 branched from \
the</FONT> <BR><FONT SIZE=2>HEAD? During the 1.1 freeze there are likely to be \
developers</FONT> <BR><FONT SIZE=2>working on new stuff that could still be \
integrated. The only extra</FONT> <BR><FONT SIZE=2>work is that any patches \
must be applied to both the 1.1 branch, and</FONT> <BR><FONT SIZE=2>the HEAD. \
Of course, it may make sense to branch only after RC1 is</FONT> <BR><FONT \
SIZE=2>released, in order to minimise any double patching.</FONT> </P>
<P><FONT SIZE=2>Just some thoughts...</FONT>
</P>
<BR>
<P><FONT SIZE=2>MikeA</FONT>
</P>
<BR>
<P><FONT SIZE=2>>> -----Original Message-----</FONT>
<BR><FONT SIZE=2>>> From: David Faure [<A \
HREF="mailto:david@mandrakesoft.com">mailto:david@mandrakesoft.com</A>]</FONT> \
<BR><FONT SIZE=2>>> Sent: 30 May 2001 08:55</FONT> <BR><FONT SIZE=2>>> \
To: koffice@kde.org; koffice-devel@kde.org; kde-i18n-doc@kde.org</FONT> <BR><FONT \
SIZE=2>>> Subject: KOffice release schedule updated</FONT> <BR><FONT \
SIZE=2>>> </FONT> <BR><FONT SIZE=2>>> </FONT>
<BR><FONT SIZE=2>>> Here's a proposal for the schedule of the next koffice \
releases :</FONT> <BR><FONT SIZE=2>>> (also available on </FONT>
<BR><FONT SIZE=2>>> <A \
HREF="http://developer.kde.org/development-versions/koffice-1.1-rel" \
TARGET="_blank">http://developer.kde.org/development-versions/koffice-1.1-rel</A></FONT>
<BR><FONT SIZE=2>>> ease-plan.html)</FONT>
<BR><FONT SIZE=2>>> </FONT>
<BR><FONT SIZE=2>>> This schedule plans a beta 3, a release candidate, and then \
</FONT> <BR><FONT SIZE=2>>> 1.1-final,</FONT>
<BR><FONT SIZE=2>>> with a translated-message freeze of ... hmm, 2 months \
(maybe </FONT> <BR><FONT SIZE=2>>> that's longer</FONT>
<BR><FONT SIZE=2>>> than necessary ?).</FONT>
<BR><FONT SIZE=2>>> </FONT>
<BR><FONT SIZE=2>>> KOffice 1.1 Beta 3</FONT>
<BR><FONT SIZE=2>>> ==============</FONT>
<BR><FONT SIZE=2>>> </FONT>
<BR><FONT SIZE=2>>> * Monday June 11</FONT>
<BR><FONT SIZE=2>>> The HEAD branch of KOffice is frozen : no new features, \
bugfixes</FONT> <BR><FONT SIZE=2>>> commits only, no commit that modifies an \
application's behaviour,</FONT> <BR><FONT SIZE=2>>> and **message freeze**. \
This freeze will last till the release of</FONT> <BR><FONT SIZE=2>>> KOffice \
1.1!</FONT> <BR><FONT SIZE=2>>> </FONT>
<BR><FONT SIZE=2>>> * Monday June 18</FONT>
<BR><FONT SIZE=2>>> The HEAD branch of CVS is tagged KOFFICE_1_1_BETA3, and \
</FONT> <BR><FONT SIZE=2>>> tarballs are made.</FONT>
<BR><FONT SIZE=2>>> They are made public immediately, and given to packagers \
for</FONT> <BR><FONT SIZE=2>>> creation of binary packages.</FONT>
<BR><FONT SIZE=2>>> </FONT>
<BR><FONT SIZE=2>>> * Monday June 25</FONT>
<BR><FONT SIZE=2>>> Announce KOffice 1.1 Beta 3</FONT>
<BR><FONT SIZE=2>>> </FONT>
<BR><FONT SIZE=2>>> KOffice 1.1 Release Candidate</FONT>
<BR><FONT SIZE=2>>> ========================</FONT>
<BR><FONT SIZE=2>>> </FONT>
<BR><FONT SIZE=2>>> * Monday July 9</FONT>
<BR><FONT SIZE=2>>> KOffice goes into deep-freeze. All commits should be posted \
for</FONT> <BR><FONT SIZE=2>>> review first.</FONT>
<BR><FONT SIZE=2>>> </FONT>
<BR><FONT SIZE=2>>> * Monday July 16</FONT>
<BR><FONT SIZE=2>>> The HEAD branch of CVS is tagged KOFFICE_1_1_RC1, and \
</FONT> <BR><FONT SIZE=2>>> tarballs are made.</FONT>
<BR><FONT SIZE=2>>> They are made public immediately, and given to packagers \
for</FONT> <BR><FONT SIZE=2>>> creation of binary packages.</FONT>
<BR><FONT SIZE=2>>> </FONT>
<BR><FONT SIZE=2>>> * Monday July 23</FONT>
<BR><FONT SIZE=2>>> Announce KOffice 1.1 Release Candidate</FONT>
<BR><FONT SIZE=2>>> </FONT>
<BR><FONT SIZE=2>>> KOffice 1.1 final</FONT>
<BR><FONT SIZE=2>>> =============</FONT>
<BR><FONT SIZE=2>>> </FONT>
<BR><FONT SIZE=2>>> * Sunday August 5</FONT>
<BR><FONT SIZE=2>>> Last day for translations, documentation, icons and \
critical</FONT> <BR><FONT SIZE=2>>> bugfixes commits.</FONT>
<BR><FONT SIZE=2>>> </FONT>
<BR><FONT SIZE=2>>> * Monday August 6</FONT>
<BR><FONT SIZE=2>>> The HEAD branch of CVS is tagged KDE_2_2_RELEASE and the \
day </FONT> <BR><FONT SIZE=2>>> is spent testing</FONT>
<BR><FONT SIZE=2>>> the release a final time.</FONT>
<BR><FONT SIZE=2>>> </FONT>
<BR><FONT SIZE=2>>> * Tuesday August 7</FONT>
<BR><FONT SIZE=2>>> The tarballs are made and released to the packagers.</FONT>
<BR><FONT SIZE=2>>> </FONT>
<BR><FONT SIZE=2>>> The rest of the week is spent testing the tarballs, </FONT>
<BR><FONT SIZE=2>>> packaging and writing the</FONT>
<BR><FONT SIZE=2>>> announcement and changelog.</FONT>
<BR><FONT SIZE=2>>> </FONT>
<BR><FONT SIZE=2>>> * Friday August 10</FONT>
<BR><FONT SIZE=2>>> The source and binary packages are uploaded to ftp.kde.org \
</FONT> <BR><FONT SIZE=2>>> to give some time</FONT>
<BR><FONT SIZE=2>>> for the mirrors to get them.</FONT>
<BR><FONT SIZE=2>>> </FONT>
<BR><FONT SIZE=2>>> * Monday August 13</FONT>
<BR><FONT SIZE=2>>> Announce KOffice 1.1.</FONT>
<BR><FONT SIZE=2>>> </FONT>
<BR><FONT SIZE=2>>> Feedback welcome !</FONT>
<BR><FONT SIZE=2>>> </FONT>
<BR><FONT SIZE=2>>> -- </FONT>
<BR><FONT SIZE=2>>> David FAURE, david@mandrakesoft.com, faure@kde.org</FONT>
<BR><FONT SIZE=2>>> <A HREF="http://perso.mandrakesoft.com/~david/" \
TARGET="_blank">http://perso.mandrakesoft.com/~david/</A>, <A \
HREF="http://www.konqueror.org/" TARGET="_blank">http://www.konqueror.org/</A></FONT> \
<BR><FONT SIZE=2>>> KDE, Making The Future of Computing Available Today</FONT> \
<BR><FONT SIZE=2>>> </FONT> </P>
<P><FONT SIZE=2>-----BEGIN PGP SIGNATURE-----</FONT>
<BR><FONT SIZE=2>Version: PGPfreeware 6.5.3 for non-commercial use <<A \
HREF="http://www.pgp.com" TARGET="_blank">http://www.pgp.com</A>></FONT> </P>
<P><FONT SIZE=2>iQA/AwUBOxS5iHympNV/C086EQKqnQCg/e72+DmiQ2CRE2HIYah21imOZRsAn1SO</FONT>
<BR><FONT SIZE=2>RIZOP+PS32YeZdJhnufKTbAM</FONT>
<BR><FONT SIZE=2>=yoHX</FONT>
<BR><FONT SIZE=2>-----END PGP SIGNATURE-----</FONT>
</P>
<CODE><FONT SIZE=3><BR>
<BR>
_________________________________________________________________________<BR>
This e-mail and any attachments are confidential and may also be privileged and/or \
copyright <BR> material of Intec Telecom Systems PLC (or its affiliated companies). \
If you are not an <BR> intended or authorised recipient of this e-mail or have \
received it in error, please delete <BR> it immediately and notify the sender by \
e-mail. In such a case, reading, reproducing, <BR> printing or further dissemination \
of this e-mail is strictly prohibited and may be unlawful. <BR> Intec Telecom Systems \
PLC. does not represent or warrant that an attachment hereto is free <BR> from \
computer viruses or other defects. The opinions expressed in this e-mail and any <BR> \
attachments may be those of the author and are not necessarily those of Intec Telecom \
<BR> Systems PLC. <BR>
<BR>
This footnote also confirms that this email message has been swept by<BR>
MIMEsweeper for the presence of computer viruses. <BR>
__________________________________________________________________________<BR>
</FONT></CODE></BODY>
</HTML>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic