here:

http://www.reactos.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ReactOS&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&rep_platform=x86+Hardware&op_sys=ReactOS&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Importance&field0-0-0=noop&type0-0-0=noop&value0-0-0=

On Fri, Sep 17, 2010 at 1:06 PM, Adam Kachwalla <[email protected]>wrote:

> I have a question: where is the list of unresolved issues?
>
> On Fri, 17 Sep 2010 21:01:30 +1000, Aleksey Bragin <[email protected]>
> wrote:
>
> 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 of
> them already have one or another solution ready.
>
> Please allow a few more days of the trunk feature freeze, until the list of
> unresolved 0.3.12 issues is empty. I know how much annoying that is, but
> it's for the good of the project.
>
> WBR,
> 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 the
> 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
> following:
> - 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 should
> be promoted to said milestone. This is the action of most utter importance,
> as there is no way to know how much time will be spent on futher research,
> 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
> [email protected]
> http://www.reactos.org/mailman/listinfo/ros-dev
>
_______________________________________________
Ros-dev mailing list
[email protected]
http://www.reactos.org/mailman/listinfo/ros-dev

Reply via email to