This is all that stands in the way of getting 0.3.0 out the door. As soon as we can config the network adapters via the dialog, we can branch and start bug hunting. This would also be a good time to enlist some more testers under the Munger wing ;)
I'm going to have a look at this tonight, but I've had a look before and IIRC, I had trouble hunting the bug down. It would be good if someone with a bit more experience in this area could have a look.
I think Gé was working on this before Christmas, so I'm hopefully gonna catch up with him tonight via IM, as I'm not sure if he's subscribed to ros-dev anymore.
We've been promising this for about 18 months now. I know a hell of a lot of work has been done in other areas (in fact, the jump from 0.3 to 0.4 should be relatively small as much of the 0.4 work is done), but we need to deliver.
After all the recent goings on, getting 0.3.0 would be a nice boost for the project, in terms of both morale and PR. Is anyone willing to help?
Ged.
************************************************************************ The information contained in this message or any of its attachments is confidential and is intended for the exclusive use of the addressee. The information may also be legally privileged. The views expressed may not be company policy, but the personal views of the originator. If you are not the addressee, any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited. If you have received this message in error, please contact postmaster@exideuk.co.uk mailto:postmaster@exideuk.co.uk and then delete this message.
Exide Technologies is an industrial and transportation battery producer and recycler with operations in 89 countries. Further information can be found at www.exide.com
Murphy, Ged (Bolton) a écrit :
This is all that stands in the way of getting 0.3.0 out the door. As soon as we can config the network adapters via the dialog, we can branch and start bug hunting. This would also be a good time to enlist some more testers under the Munger wing ;)
I'm going to have a look at this tonight, but I've had a look before and IIRC, I had trouble hunting the bug down. It would be good if someone with a bit more experience in this area could have a look.
I think Gé was working on this before Christmas, so I'm hopefully gonna catch up with him tonight via IM, as I'm not sure if he's subscribed to ros-dev anymore.
We've been promising this for about 18 months now. I know a hell of a lot of work has been done in other areas (in fact, the jump from 0.3 to 0.4 should be relatively small as much of the 0.4 work is done), but we need to deliver.
After all the recent goings on, getting 0.3.0 would be a nice boost for the project, in terms of both morale and PR. Is anyone willing to help?
Ged.
Hello,
I used to maintien a test page ( Ros in Real box - Networking ..) as "Munger" I'll update it for this purpose.
There is a link to it in the Wiki/Tester section -->> /http://www.reactos.org/wiki/index.php/People_of_ReactOS
Regards Gge
ncpaWhat's needed for 0.3: 1. Go through bugzilla, review all opened bugs, and give them appropriate status. As of now we have 291 open bug, ~18 have 'critical' status. 2. Complete http://www.reactos.org/wiki/index.php/0.3.x/0.3.0 , ensuring it works in current SVN head (notices that it work[ed] in 0.2.9 are good, however regressions might happen) 3. Merge Wine 0.9.11 changes in the tree 4. Implement at least something, best - everything from this page: http://www.reactos.org/wiki/index.php/Alex%27s_0.3.0_%27User_Wow_Factor%27_I... 5. Perform some load-testing on real hardware, like Gge is doing, so that all those stuff not only "works" but works for hours.
Only after these steps I can be sure 0.3 is ready.
I do not see a release of a half-working thing with regressions as a good for PR. People await a lot from the major release. We must give them what they deserve ;)
WBR, Aleksey Bragin. ----- Original Message ----- From: Murphy, Ged (Bolton) To: 'ReactOS Development List' Sent: Tuesday, April 04, 2006 12:42 PM Subject: [ros-dev] ncpa
This is all that stands in the way of getting 0.3.0 out the door. As soon as we can config the network adapters via the dialog, we can branch and start bug hunting. This would also be a good time to enlist some more testers under the Munger wing ;)
I'm going to have a look at this tonight, but I've had a look before and IIRC, I had trouble hunting the bug down. It would be good if someone with a bit more experience in this area could have a look.
I think Gé was working on this before Christmas, so I'm hopefully gonna catch up with him tonight via IM, as I'm not sure if he's subscribed to ros-dev anymore.
We've been promising this for about 18 months now. I know a hell of a lot of work has been done in other areas (in fact, the jump from 0.3 to 0.4 should be relatively small as much of the 0.4 work is done), but we need to deliver.
After all the recent goings on, getting 0.3.0 would be a nice boost for the project, in terms of both morale and PR. Is anyone willing to help?
Ged.
************************************************************************ The information contained in this message or any of its attachments is confidential and is intended for the exclusive use of the addressee. The information may also be legally privileged. The views expressed may not be company policy, but the personal views of the originator. If you are not the addressee, any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited. If you have received this message in error, please contact postmaster@exideuk.co.uk mailto:postmaster@exideuk.co.uk and then delete this message.
Exide Technologies is an industrial and transportation battery producer and recycler with operations in 89 countries. Further information can be found at www.exide.com
------------------------------------------------------------------------------
_______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
On 4/4/06, Aleksey Bragin aleksey@studiocerebral.com wrote:
What's needed for 0.3:
- Go through bugzilla, review all opened bugs, and give them appropriate
status. As of now we have 291 open bug, ~18 have 'critical' status.
I will review BZ.
- Complete
http://www.reactos.org/wiki/index.php/0.3.x/0.3.0 , ensuring it works in current SVN head (notices that it work[ed] in 0.2.9 are good, however regressions might happen) 3. Merge Wine 0.9.11 changes in the tree 4. Implement at least something, best - everything from this page: http://www.reactos.org/wiki/index.php/Alex%27s_0.3.0_%27User_Wow_Factor%27_I... 5. Perform some load-testing on real hardware, like Gge is doing, so that all those stuff not only "works" but works for hours.
I can dig out the rosbox. I usually do hardware testing after doing inital testing under VMs.
Only after these steps I can be sure 0.3 is ready.
I do not see a release of a half-working thing with regressions as a good for PR. People await a lot from the major release. We must give them what they deserve ;)
WBR, Aleksey Bragin.
----- Original Message ----- From: Murphy, Ged (Bolton) To: 'ReactOS Development List' Sent: Tuesday, April 04, 2006 12:42 PM Subject: [ros-dev] ncpa
This is all that stands in the way of getting 0.3.0 out the door. As soon as we can config the network adapters via the dialog, we can branch and start bug hunting. This would also be a good time to enlist some more testers under the Munger wing ;)
I'm going to have a look at this tonight, but I've had a look before and IIRC, I had trouble hunting the bug down. It would be good if someone with a bit more experience in this area could have a look.
I think Gé was working on this before Christmas, so I'm hopefully gonna catch up with him tonight via IM, as I'm not sure if he's subscribed to ros-dev anymore.
We've been promising this for about 18 months now. I know a hell of a lot of work has been done in other areas (in fact, the jump from 0.3 to 0.4 should be relatively small as much of the 0.4 work is done), but we need to deliver.
After all the recent goings on, getting 0.3.0 would be a nice boost for the project, in terms of both morale and PR. Is anyone willing to help?
Ged.
The information contained in this message or any of its attachments is confidential and is intended for the exclusive use of the addressee. The information may also be legally privileged. The views expressed may not be company policy, but the personal views of the originator. If you are not the addressee, any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited. If you have received this message in error, please contact postmaster@exideuk.co.uk mailto:postmaster@exideuk.co.uk and then delete this message.
Exide Technologies is an industrial and transportation battery producer and recycler with operations in 89 countries. Further information can be found at www.exide.com
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
-- <Bizzeh> it even has a panda that pops out of your case and mauls people who ask stupid questions
As long is there an honest effort towards 0.3.0, I will be more than happy to help out. I'm still pretty familiar with the open bugs and what was working in 0.2.9.
On 4/4/06, Murphy, Ged (Bolton) MurphyG@cmpbatteries.co.uk wrote:
This is all that stands in the way of getting 0.3.0 out the door. As soon as we can config the network adapters via the dialog, we can branch and start bug hunting. This would also be a good time to enlist some more testers under the Munger wing ;)
I'm going to have a look at this tonight, but I've had a look before and IIRC, I had trouble hunting the bug down. It would be good if someone with a bit more experience in this area could have a look.
I think Gé was working on this before Christmas, so I'm hopefully gonna catch up with him tonight via IM, as I'm not sure if he's subscribed to ros-dev anymore.
We've been promising this for about 18 months now. I know a hell of a lot of work has been done in other areas (in fact, the jump from 0.3 to 0.4 should be relatively small as much of the 0.4 work is done), but we need to deliver.
After all the recent goings on, getting 0.3.0 would be a nice boost for the project, in terms of both morale and PR. Is anyone willing to help?
Ged.
The information contained in this message or any of its attachments is confidential and is intended for the exclusive use of the addressee. The information may also be legally privileged. The views expressed may not be company policy, but the personal views of the originator. If you are not the addressee, any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited. If you have received this message in error, please contact postmaster@exideuk.co.uk mailto:postmaster@exideuk.co.uk and then delete this message.
Exide Technologies is an industrial and transportation battery producer and recycler with operations in 89 countries. Further information can be found at www.exide.com
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
-- <Bizzeh> it even has a panda that pops out of your case and mauls people who ask stupid questions
Hi! WaxDragon wrote:
As long is there an honest effort towards 0.3.0, I will be more than happy to help out. I'm still pretty familiar with the open bugs and what was working in 0.2.9.
I hope the noise factor is close to null! I'm ready to start back up and get this project rocken again! Bite tung! Bite tung! Hand over mouth!
8^D James
-
Aleksey Bragin -
Gge -
James Tabor -
Murphy, Ged (Bolton) -
Saveliy Tretiakov -
WaxDragon