[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:55:18
[Download RAW message or body]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Yes, I hadn't thought of that ;-)
>> -----Original Message-----
>> From: David Faure [mailto:david@mandrakesoft.com]
>> Sent: 30 May 2001 09:18
>> To: koffice@max.tat.physik.uni-tuebingen.de
>> Subject: Re: KOffice release schedule updated
>>
>>
>> On Wednesday 30 May 2001 11:14, Michael Ansley \(UK\) wrote:
>> > 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.
>>
>> Yes, we'll probably do that. After 1.1-final, I'd say.
>> That's how we always
>> did it in KDE itself as well. If you branch earlier, then
>> you encourage people
>> to work on new stuff instead of bugfixing things for the
>> upcoming release ;-)
>>
>> --
>> 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/AwUBOxTDNnympNV/C086EQIS6QCfT6PFPfkevZWpzNzxFbQNyPJxHE0AniLL
ihcDJ5IgOXuFXPXln/5tYd0L
=0dzr
-----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>Yes, I hadn't thought of that ;-)</FONT>
</P>
<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 09:18</FONT> <BR><FONT SIZE=2>>> \
To: koffice@max.tat.physik.uni-tuebingen.de</FONT> <BR><FONT SIZE=2>>> Subject: \
Re: KOffice release schedule updated</FONT> <BR><FONT SIZE=2>>> </FONT>
<BR><FONT SIZE=2>>> </FONT>
<BR><FONT SIZE=2>>> On Wednesday 30 May 2001 11:14, Michael Ansley \(UK\) \
wrote:</FONT> <BR><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</FONT> <BR><FONT SIZE=2>>> > the \
HEAD? During the 1.1 freeze there are likely to be</FONT> <BR><FONT \
SIZE=2>>> > developers working on new stuff that could still be integrated. \
</FONT> <BR><FONT SIZE=2>>> > The </FONT>
<BR><FONT SIZE=2>>> only extra</FONT>
<BR><FONT SIZE=2>>> > work is that any patches must be applied to both the \
1.1 </FONT> <BR><FONT SIZE=2>>> branch, and</FONT>
<BR><FONT SIZE=2>>> > the HEAD. Of course, it may make sense to branch \
only after RC1</FONT> <BR><FONT SIZE=2>>> > is released, in order to \
minimise any double patching.</FONT> <BR><FONT SIZE=2>>> </FONT>
<BR><FONT SIZE=2>>> Yes, we'll probably do that. After 1.1-final, I'd say. \
</FONT> <BR><FONT SIZE=2>>> That's how we always</FONT>
<BR><FONT SIZE=2>>> did it in KDE itself as well. If you branch earlier, then \
</FONT> <BR><FONT SIZE=2>>> you encourage people</FONT>
<BR><FONT SIZE=2>>> to work on new stuff instead of bugfixing things for the \
</FONT> <BR><FONT SIZE=2>>> upcoming release ;-)</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/AwUBOxTDNnympNV/C086EQIS6QCfT6PFPfkevZWpzNzxFbQNyPJxHE0AniLL</FONT>
<BR><FONT SIZE=2>ihcDJ5IgOXuFXPXln/5tYd0L</FONT>
<BR><FONT SIZE=2>=0dzr</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