Re: [ros-dev] 0.3.0 RC1 Update

[Murphy, Ged (Bolton)]

Brandon Turner wrote:
> I have added a debug bootcd build of RC1 to sourceforge. 
> So anyone out there looking to get there hands one for 
> troubleshooting 0.3.0 can hop on there and grab it.

We've had this up for 3 weeks now.
Changes to trunk have been so heavy since we branched 0.3, we effectively
now have two _very_ different versions of ReactOS .... heh

Maybe our release process needs reviewing slightly ;)

Ged.

[Brandon Turner]

Well... there was a lot of changes _before_ we even branched.  We 
branched at an earlier version of trunk then head.  So we knew they were 
going to be really different.  You cant look at the release process in 
the view of time/commits because it is about being stable and meeting 
your goals. As far as I know, once the blocker is fixed, we will move 
into code freeze and I will release RC2.  A small time period will go by 
where as our wiki says "for the QA team to do a final sanity check of 
the release" and then I will do the final release.  Perhaps I am 
mistaken on the process and missed the time I should have made another 
release.  If this is the case please feel free to let me know what I can 
do to resolve the the problem.

Brandon

Murphy, Ged (Bolton) wrote:
> Brandon Turner wrote:
> > I have added a debug bootcd build of RC1 to sourceforge. 
> > So anyone out there looking to get there hands one for 
> > troubleshooting 0.3.0 can hop on there and grab it.
>
> We've had this up for 3 weeks now.
> Changes to trunk have been so heavy since we branched 0.3, we effectively
> now have two _very_ different versions of ReactOS .... heh
>
> Maybe our release process needs reviewing slightly ;)
>
> Ged.
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

[Magnus Olsen]

RC1 is not ready 
for moment OpenGL is broken (MESA3D) and it is on Alex todo list
to fix Context switch in ntoskrnl.

We need that fix to 0.3.0 and we also need fixing abi word working again 
and a redraw problem with windows. Other wise 0.3.0 will look as crap
from user point of view.

This problem must be fixed before 0.3.0 being release. or next rc2

----- Original Message ----- 
From: "Murphy, Ged (Bolton)" [e-mail]
To: "'ReactOS Development List'" [e-mail]
Sent: Monday, July 10, 2006 4:04 PM
Subject: Re: [ros-dev] 0.3.0 RC1 Update
> Brandon Turner wrote:
> > I have added a debug bootcd build of RC1 to sourceforge. 
> > So anyone out there looking to get there hands one for 
> > troubleshooting 0.3.0 can hop on there and grab it.
>
> We've had this up for 3 weeks now.
> Changes to trunk have been so heavy since we branched 0.3, we effectively
> now have two _very_ different versions of ReactOS .... heh
>
> Maybe our release process needs reviewing slightly ;)
>
> Ged.
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

[Alex Ionescu]

Magnus Olsen wrote:
> RC1 is not ready 
> for moment OpenGL is broken (MESA3D) and it is on Alex todo list
> to fix Context switch in ntoskrnl.

It is?

Best regards,
Alex Ionescu

[WaxDragon]

I know these have been your personal blockers, but Fireball told me
weeks ago that we will not hold up 0.3.0 for Abiword.  Personally, I
am not going to hold up 0.3.0 for broken OpenGL.  I've purposely
slowed this release cycle to allow fixes to be merged.  The only bug
I'm concerned about right now is the broken links in the start menu,
which I think is even fixed in trunk.  Nothing else can really be
addressed at this point.

Anyone with comments? Anyone actually tested 0.3.0?

WD

On 7/10/06, Magnus Olsen [e-mail] wrote:
> RC1 is not ready
> for moment OpenGL is broken (MESA3D) and it is on Alex todo list
> to fix Context switch in ntoskrnl.
>
> We need that fix to 0.3.0 and we also need fixing abi word working again
> and a redraw problem with windows. Other wise 0.3.0 will look as crap
> from user point of view.
>
> This problem must be fixed before 0.3.0 being release. or next rc2
>
> ----- Original Message -----
> From: "Murphy, Ged (Bolton)" [e-mail]
> To: "'ReactOS Development List'" [e-mail]
> Sent: Monday, July 10, 2006 4:04 PM
> Subject: Re: [ros-dev] 0.3.0 RC1 Update
> > Brandon Turner wrote:
> > > I have added a debug bootcd build of RC1 to sourceforge.
> > > So anyone out there looking to get there hands one for
> > > troubleshooting 0.3.0 can hop on there and grab it.
> >
> > We've had this up for 3 weeks now.
> > Changes to trunk have been so heavy since we branched 0.3, we effectively
> > now have two _very_ different versions of ReactOS .... heh
> >
> > Maybe our release process needs reviewing slightly ;)
> >
> > Ged.
> >
> > Ros-dev mailing list
> > [e-mail]
> > http://www.reactos.org/mailman/listinfo/ros-dev
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev
-- 
<GedMurphy> why does the size matter?

[Aleksey Bragin]

I think we have a quick-fix for this bug committed to trunk by Magnus.

Are there any real major bugs in 0.3 RC1 besides this?

I tried the release certainly, not really extensive testing, but my  
test apps worked on it. Would like to hear others feedback too.

WBR,
Aleksey Bragin.

On Jul 10, 2006, at 9:25 PM, WaxDragon wrote:
> I know these have been your personal blockers, but Fireball told me
> weeks ago that we will not hold up 0.3.0 for Abiword.  Personally, I
> am not going to hold up 0.3.0 for broken OpenGL.  I've purposely
> slowed this release cycle to allow fixes to be merged.  The only bug
> I'm concerned about right now is the broken links in the start menu,
> which I think is even fixed in trunk.  Nothing else can really be
> addressed at this point.
>
> Anyone with comments? Anyone actually tested 0.3.0?
>
> WD

[WaxDragon]

On 7/10/06, Aleksey Bragin [e-mail] wrote:
> I think we have a quick-fix for this bug committed to trunk by Magnus.
>
> Are there any real major bugs in 0.3 RC1 besides this?

The release build of RC1 gets a bootvid.sys failure under two VMWare
instances I tested on.  Both were on linux, one was Workstation 5.5.1
and the other was VMWare Player.  I did test VMWare on a windows host
and RC1 worked fine.  The workaround was to add a serial port and
enable serial debugging on the one particular boot that failed.  I was
not going to block the release since it has an odd invocation, and
it's fixed in trunk now.

While doing regression testing, I could not find where the problem was
intrduced, but the NDK commit seemed to have fixed it.

All the other bugs and crashes I encountered during testing are the
usual stability issues that are being worked on.
> I tried the release certainly, not really extensive testing, but my
> test apps worked on it. Would like to hear others feedback too.
>
> WBR,
> Aleksey Bragin.
>
> On Jul 10, 2006, at 9:25 PM, WaxDragon wrote:
> > I know these have been your personal blockers, but Fireball told me
> > weeks ago that we will not hold up 0.3.0 for Abiword.  Personally, I
> > am not going to hold up 0.3.0 for broken OpenGL.  I've purposely
> > slowed this release cycle to allow fixes to be merged.  The only bug
> > I'm concerned about right now is the broken links in the start menu,
> > which I think is even fixed in trunk.  Nothing else can really be
> > addressed at this point.
> >
> > Anyone with comments? Anyone actually tested 0.3.0?
> >
> > WD
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev
-- 
<GedMurphy> why does the size matter?

[Aleksey Bragin]

Ok good, I think it's fair to trade off this, especially because this  
is fixed in trunk (-> fixed in the next release).

Also it makes people await next release more eager :-)

WBR,
Aleksey Bragin.

On Jul 10, 2006, at 11:42 PM, WaxDragon wrote:
> On 7/10/06, Aleksey Bragin [e-mail] wrote:
> > I think we have a quick-fix for this bug committed to trunk by  
> > Magnus.
> >
> > Are there any real major bugs in 0.3 RC1 besides this?
>
> The release build of RC1 gets a bootvid.sys failure under two VMWare
> instances I tested on.  Both were on linux, one was Workstation 5.5.1
> and the other was VMWare Player.  I did test VMWare on a windows host
> and RC1 worked fine.  The workaround was to add a serial port and
> enable serial debugging on the one particular boot that failed.  I was
> not going to block the release since it has an odd invocation, and
> it's fixed in trunk now.
>
> While doing regression testing, I could not find where the problem was
> intrduced, but the NDK commit seemed to have fixed it.
>
> All the other bugs and crashes I encountered during testing are the
> usual stability issues that are being worked on.

[Magnus Olsen]

WaxDragon
The broken Context switch will break allot program that using
FPU,MMX,SSE,3DNOW.
Context swtich are to save cpu state before it goes to k mode and restore it
when it comes
to user mode. If it does not working as it should it will bsod or crash alot
of apps, Not only
OpenGL. It is marjor  regress in my eyes. and we should not release ReactOS
with this
regress. It will look not good for enduser eyes when hey this apps have stop
working Why
it using MMX, or Hey this apps does not working why it using FPU. and so on

----- Original Message ----- 
From: "WaxDragon" [e-mail]
To: "ReactOS Development List" [e-mail]
Sent: Monday, July 10, 2006 7:25 PM
Subject: Re: [ros-dev] 0.3.0 RC1 Update
> I know these have been your personal blockers, but Fireball told me
> weeks ago that we will not hold up 0.3.0 for Abiword.  Personally, I
> am not going to hold up 0.3.0 for broken OpenGL.  I've purposely
> slowed this release cycle to allow fixes to be merged.  The only bug
> I'm concerned about right now is the broken links in the start menu,
> which I think is even fixed in trunk.  Nothing else can really be
> addressed at this point.
>
> Anyone with comments? Anyone actually tested 0.3.0?
>
> WD
>
> On 7/10/06, Magnus Olsen [e-mail] wrote:
> > RC1 is not ready
> > for moment OpenGL is broken (MESA3D) and it is on Alex todo list
> > to fix Context switch in ntoskrnl.
> >
> > We need that fix to 0.3.0 and we also need fixing abi word working again
> > and a redraw problem with windows. Other wise 0.3.0 will look as crap
> > from user point of view.
> >
> > This problem must be fixed before 0.3.0 being release. or next rc2
> >
> > ----- Original Message -----
> > From: "Murphy, Ged (Bolton)" [e-mail]
> > To: "'ReactOS Development List'" [e-mail]
> > Sent: Monday, July 10, 2006 4:04 PM
> > Subject: Re: [ros-dev] 0.3.0 RC1 Update
> > > Brandon Turner wrote:
> > > > I have added a debug bootcd build of RC1 to sourceforge.
> > > > So anyone out there looking to get there hands one for
> > > > troubleshooting 0.3.0 can hop on there and grab it.
> > >
> > > We've had this up for 3 weeks now.
> > > Changes to trunk have been so heavy since we branched 0.3, we

effectively
> > > now have two _very_ different versions of ReactOS .... heh
> > >
> > > Maybe our release process needs reviewing slightly ;)
> > >
> > > Ged.
> > >
> > > Ros-dev mailing list
> > > [e-mail]
> > > http://www.reactos.org/mailman/listinfo/ros-dev
> >
> > Ros-dev mailing list
> > [e-mail]
> > http://www.reactos.org/mailman/listinfo/ros-dev
>
> -- 
> <GedMurphy> why does the size matter?
> _______________________________________________
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

[Ged Murphy]

Magnus Olsen wrote:
> WaxDragon
> The broken Context switch will break allot program that using
> FPU,MMX,SSE,3DNOW.
> Context swtich are to save cpu state before it goes to k mode and restore it
> when it comes
> to user mode. If it does not working as it should it will bsod or crash alot
> of apps, Not only
> OpenGL. It is marjor  regress in my eyes. and we should not release ReactOS
> with this
> regress. It will look not good for enduser eyes when hey this apps have stop
> working Why
> it using MMX, or Hey this apps does not working why it using FPU. and so on

If this is fixed in HEAD, why don't we just release 0.3.0 now and branch 
for 0.3.1.
More than enough work has been done to justify 0.3.1 and we could have 
it out in a few weeks.

0.3.0 RC1 has been out for almost a month now, and nobody has complained 
about any major bugs.

Ged