[ros-dev] 0.3.12 TODO list
caemyr at gmail.com
Fri Sep 17 13:53:16 UTC 2010
This is why i prefer alternative approach:
2010/9/17 Adam Kachwalla <geekdundee at gmail.com>
> (wow... there are a HELL of a lot of bugs... 666 to be precise!)
> On Fri, 17 Sep 2010 21:15:49 +1000, Javier Agustìn Fernàndez Arroyo <
> elhoir at gmail.com> wrote:
>> On Fri, Sep 17, 2010 at 1:06 PM, Adam Kachwalla <geekdundee at gmail.com
>> I have a question: where is the list of unresolved issues?
>>> On Fri, 17 Sep 2010 21:01:30 +1000, Aleksey Bragin <aleksey at reactos.org>
>>> As for existing 0.3.12-milestone entries in the BugZilla, I think they
>>> fully make sense because vast majority of them are regressions, and most
>>> them already have one or another solution ready.
>>> Please allow a few more days of the trunk feature freeze, until the list
>>> unresolved 0.3.12 issues is empty. I know how much annoying that is, but
>>> it's for the good of the project.
>>> Aleksey Bragin.
>>> On Sep 14, 2010, at 9:41 PM, Olaf Siejka wrote:
>>> As we progress into regression fixing, we are now in the good moment to
>>> decide upon upcoming release. It would be great if we could manage with
>>> 0.3.12 for the October Chemnitz event, where we are invited again to
>>> participate, not to mention that its the time for such release.
>>> Right now, in my opinion we should decide without futher delay on the
>>> - reviewing the REGRESSION list, this is - to confirm entries with 0.3.12
>>> milestone already set, as well as doublecheck the rest, to see if any
>>> be promoted to said milestone. This is the action of most utter
>>> as there is no way to know how much time will be spent on futher
>>> testing and fixing them;
>>> - decide upon bugs originated with last ole/comctl sync - are we haxing
>>> them locally, risking another winesync or perhaps reverting?
>>> - reviewing patches stored at http://www.reactos.org/wiki/Bug_Filters as
>>> well as deciding if any should be adapted for current release.
>>> Those actions, first of them especially, should be performed as swift as
>>> possible, else we might risk considerable delay and nervous finish before
>>> the Chemnitz.
>>> Give a man a fish and he will eat for a day.
>>> Teach a man to fish and he will eat for a lifetime.
>>> Give a man religion and he will die praying for a fish.
>>> Ros-dev mailing list
>>> Ros-dev at reactos.org
> Give a man a fish and he will eat for a day.
> Teach a man to fish and he will eat for a lifetime.
> Give a man religion and he will die praying for a fish.
> Ros-dev mailing list
> Ros-dev at reactos.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ros-dev