<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 11/13/2009 05:09 PM, Farzad Sehat wrote:
<blockquote
cite="mid:88cbf3720911130809w73f5fa1er4b5f3c0679db40d9@mail.gmail.com"
type="cite">
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
</blockquote>
<div>I absolutely agree with this point of view, our community is not
big enough and moreover <br>
there is a lot of work to be done in the documentation. 2 release per
year is too much and <br>
we have to favour quality.<br>
As Xavier said we have to freeze the stable 2 or 3 month before release
in order to have a high <br>
quality release.<br>
The key feature is to make regular and complete report to benoit about
the feature each member is developping.<br>
This way benoit can merge them more easely and more efficiently to the
master branch and moreover he can merge <br>
to the stable branch more often. Indeed a good communication about all
developping features let Ben to work <br>
better and to have fewer bug when freezing the stable.</div>
</blockquote>
<br>
Ok, perhaps big releases is not such a good idea, i'm willing to admit
that.<br>
<br>
But I think we should, at least internally, have more than one release
a year. Those wouldn't be much publicized, and will be only for Lisaac
enthusiasts. I don't think we can yet produce high quality releases
(the language itself doesn't yet meet my criteria of quality). But I
think we should be more dynamic. Without doing much, we can create a
momentum that could carry us much further.<br>
<br>
It's also important for us psychologically to see things moving. If we
can say that 3 month before, the compiler was missing this and that
feature but now, it's available. It helps us keep the faith in what we
do and keep moving.<br>
<br>
<br>
<br>
Also, that's a little off topic here, but I think we should include in
the source directory a changelog file. Each new release will be added
in it, and each new feature as well. Features should make reference to
git commits so those who want to review them (Ben?) can see what
exactly has been done. Any other commit should be trivial enough.<br>
<br>
<br>
Mildred<br>
<pre class="moz-signature" cols="72">--
Mildred Ki'Lya
╭───────── ｍｉｌｄｒｅｄ５９３＠ｏｎｌｉｎｅ．ｆｒ ──────────
│ Jabber, GoogleTalk: <a class="moz-txt-link-rfc2396E" href="mailto:mildred@jabber.fr"><mildred@jabber.fr></a>
│ Website: <a class="moz-txt-link-rfc2396E" href="http://ki.lya.online.fr"><http://ki.lya.online.fr></a> GPG ID: 9A7D 2E2B
│ Fingerprint: 197C A7E6 645B 4299 6D37 684B 6F9D A8D6 9A7D 2E2B
</pre>
</body>
</html>