On Mon, 29 Jun 2009, Gustavo Sverzut Barbieri wrote:

> On Mon, Jun 29, 2009 at 10:15 AM, Vincent Torri<vto...@univ-evry.fr> wrote:
>>
>>
>> On Mon, 29 Jun 2009, Cedric BAIL wrote:
>>
>>> Hi every one,
>>>
>>> Around 23th of July, we are currently planning to do another round of
>>> snapshot. If you look at http://trac.enlightenment.org/e/wiki/Release,
>>> you will notice that Eina's TODO list is empty. I just would like to
>>> see patch from dieb to improve the logging API to come in before the
>>> release. But anyway, it's time for the last serie of reviews, tests,
>>> comments, add documentation before 1.0.0.
>>
>> the most important thing is to be sure that the API is correct. Most of
>> them are fixed, but i have opened a ticket for that.
>>
>> even if the TODO list is empty, there are some opened tickets for eina in
>> trac.
>>
>>> So people, I am requesting your help here. Take any file, look at the
>>> code, documentation, compile, tests and see if anything is wrong, make
>>> no sense or just should be improved. Fill the trac, or ping me on irc
>>> or by mail about any issue regarding Eina. I hope we could release it
>>> for the end of July.
>>
>> About documentation, as french people wrote it, it is certainly full of
>> spelling and grammar mistakes (like in these 2 mails, I think...). So we
>> need spelling and grammar fixators :-)
>
> These two points are even more reason to make this release happen.
> We'll get more engaged into fixing bugs and reviewing api/docs.

I do not agree. If we make a release, we *must not change* the API after. 
Adding is ok. Changing is not. That's why i think that we must be sure 
that we will not change the current api after the release.

about bugs, of course, we can fix them before or after. Better is before 
:)

Vincent

------------------------------------------------------------------------------
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to