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.
Hi everyone.
I know I have'nt been there for a while, and won't be soon. As for the "blue icons" problem, it is fixed in yarotows. If you want to release, you'd better revert r48008, which introduced the regression. I'm really sorrry I can not do it myself and prvide a patch to anyone with commit access.
Kind regards, hoping I will be back anytime soon. Jérôme.
Message du 14/09/10 19:41 De : "Olaf Siejka" A : "ReactOS Development List" Copie à : Objet : [ros-dev] 0.3.12 TODO list
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. > [ (pas de nom de fichier) (0.1 Ko) ]
Une messagerie gratuite, garantie à vie et des services en plus, ça vous tente ? Je crée ma boîte mail www.laposte.net
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.
I have a question: where is the list of unresolved issues?
On Fri, 17 Sep 2010 21:01:30 +1000, Aleksey Bragin aleksey@reactos.org 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.
here:
http://www.reactos.org/bugzilla/buglist.cgi?query_format=advanced&short_...
On Fri, Sep 17, 2010 at 1:06 PM, Adam Kachwalla geekdundee@gmail.comwrote:
I have a question: where is the list of unresolved issues?
On Fri, 17 Sep 2010 21:01:30 +1000, Aleksey Bragin aleksey@reactos.org 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 Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Thanks...
(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@gmail.com wrote:
here:
http://www.reactos.org/bugzilla/buglist.cgi?query_format=advanced&short_...
On Fri, Sep 17, 2010 at 1:06 PM, Adam Kachwalla geekdundee@gmail.comwrote:
I have a question: where is the list of unresolved issues?
On Fri, 17 Sep 2010 21:01:30 +1000, Aleksey Bragin aleksey@reactos.org 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 Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
This is why i prefer alternative approach: http://www.reactos.org/wiki/Bug_Filters http://www.reactos.org/wiki/Buglist
Regards
2010/9/17 Adam Kachwalla geekdundee@gmail.com
Thanks...
(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@gmail.com> wrote:
here:
http://www.reactos.org/bugzilla/buglist.cgi?query_format=advanced&short_...
On Fri, Sep 17, 2010 at 1:06 PM, Adam Kachwalla <geekdundee@gmail.com
wrote:
I have a question: where is the list of unresolved issues?
On Fri, 17 Sep 2010 21:01:30 +1000, Aleksey Bragin aleksey@reactos.org 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 Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
-- 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@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
-
Adam Kachwalla -
Aleksey Bragin -
Javier Agustìn Fernàndez Arroyo -
jerome.gardou -
Olaf Siejka