Community > ReactOS Newsletter Archive > ReactOS Newsletter: Volume 1, Issue 9
Volume 1, Issue 9
- Issue 9 of the Newsletter has landed
- What is the 'Software Life Cycle'?
- Step 1: Pre-Alpha
- Step 2: Alpha
- Stage 3: Beta
- Stage 4: Release Candidate
- Step 5: Version 1.0
- How far is ReactOS from Version 1.0?
- SVN: The Week that Was
- Added to Build
- Changes to 0.2.9 Branch Only
- Advapi32
- API Status List
- CMD
- CPL
- CRT
- Devmgr
- Drivers
- Explorer
- Kernel32
- New
- Press/Media
- RosCMS
- Content Edit Interface
- Login Function
- Website Status Page
- User Accounts Admin Interface Page
- SetupAPI
- Shell32
- SMSS
- Techbot (IRC)
- Vendor Drops
- Vendor Imports
- WineCalc
- USB
- User32
- XML Files
- Next Week?
byon
topIssue 9 of the Newsletter has landed
There are very few things that irritate me. Windows XP playing havock with my mouse cursor ranks among them. Thus, a reformat and reload ensues. And to top it all off, I have a PSU that's as dodgy as an SCO-Endorsed Lawsuit. For some strange reason, one of my Hard Drives will have its power drop out, which causes my drive to spin down, that acts like a domino toppling, and causes my system to hang. Very weird, and it's partly the reason I haven't been able to do a lot. Dignostics, losing your work every time it freezes isn't is very time consuming.
So, what's going down this week? A little explanation of where ReactOS is on the "Software Life Cycle", with my usual wit, and tasteless humor thrown in for good measure.
topWhat is the 'Software Life Cycle'?
Glad you asked. Each piece of Software that's made by a competent set of software engineers, follows a Life Cycle, that gives the End User a (very generic) idea of how mature and stable the software is.
topStep 1: Pre-Alpha
Pre-Alpha is the collection of Ideas, the plannng of how to write the code, and in some cases, the writing of the Coding Framework, if what you are writing is complex. Now, while ReactOS, on our own front page, is listed as "Pre-Alpha", I'm going to have to disagree on that point.
topStep 2: Alpha
This is how ReactOS should be described right now, in my humble opinon. Alpha is the writing of the Core Code, and where most of the releases will only be of interest to Software Engineers, Developers, and a handful of enthusiasts. In Alpha, much of the software is incomplete, and in most cases, has more holes than an OJ Simpson Alibi. As with all Alpha Software, ReactOS carries the maxim, "Use at your own risk". Alpha Software can be made into Periodic releases, i.e. Alpha 1, Alpha 2, etc, to indicate how far the Alpha Stage has progressed.
topStage 3: Beta
This is the stage of interest to most, and occurs when the Software has reached a modest level of Stabilty, and Functionality. In this Stage, Feedback is often sought from many public angles, especially with such complex software as an Operating System. Beta Software can also be made into Periodic releases, i.e. Beta 1, Beta 2, etc, to indicate how far the Beta Process has gone.
topStage 4: Release Candidate
While this is a stage in it's own right, it can also apply for Alpha and Beta Releases, too. In a Release Candidate, the code undergoes what is called "Feature Freeze". That means any new code that deals with new features or functionlity that is submitted to Trunk, is not backported to the Version Branch.
Further down the cycle of RC's (You can have quite a few, I seem to recall seeing one on Betanews that was RC16 at one point), the code in the Branch used to house the Release Candidate will undergo what is called "Code Freeze". This is a total stop to code backports, with the exception of bug fixes relating to "Blocker" Bugs. Blocker Bugs are Bugs that are deemed so critical, that a decision has been made to delay the release, until the bug is fixed to a satisfactory standard.
topStep 5: Version 1.0
The much-coveted Version 1.0 release. Attained when it is decided that all the criteria set have been passed, and it is deemed Stable enough for a Public Release.
topHow far is ReactOS from Version 1.0?
This question is asked a lot. In fact, the only other projects where this question is asked a lot concern Microsoft, and Duke Nukem Forever.
ReactOS is scheduled to go until 0.5.x, and if all criteria are met, hop straight to 1.0 However, if new projects are deemed fir to be included, 0.6.x might be on the cards. Or, it could be bumped to a later ReactOS release.
Working Subsyatems could be a fixture for a 2.0.0 release, for example.
topSVN: The Week that Was
Another Week. Another Was. This is the Week that Was.
topAdded to Build
- oleacc
Changes to 0.2.9 Branch Only
- Default Resolution now 800x600x8 (Not sure if reverted or not)
- Add static entries for PCnet and NE2000 network cards (VMware/QEmu resp.) so networking is available on the LiveCD
- Version Changed to RC2
Advapi32
- Implemented QueryServiceConfigW
API Status List
- Ole32 Removed
- OleAut32 Removed
- Shell32 Removed
- Winmm Removed
CMD
- 'type/p','dir/p','dir/s', and 'dir/p/s' commands now fixed with CTRL+C
CPL
- Property sheet now fits in 640x480
CRT
- C++ Exception Handling Fixed
Devmgr
- Rename IsDeviceEnabled to IsDeviceStarted
Drivers
- New Generic Floppy Disk Controller Driver
- Serial Port Driver now uses correct default baud rate
Explorer
- Disable the Printer submenu folder in Start Menu "Settings"
Kernel32
- GUI Process now detached from console
- Implemented GetVolumeNameForVolumeMountPointW
New
- GetFirefox Utility (To replace iBrowser acquiring it)
Press/Media
- Initial presentation for MIT 100 Laptop Added
RosCMS
top
Content Edit Interface
- Content type bug fixed
Login Function
- Add a link to the "too many sessions" error message -> this link allow user to delete their old sessions (and reset their password)
Website Status Page
- fix the language detection routine
- fixed translation date
- add day counter and "date colors"
User Accounts Admin Interface Page
- improve the navigation
SetupAPI
- Implemented DICS_FLAG_CONFIGSPECIFIC case in SetupDiOpenDevRegKey
- Implemented DICS_FLAG_CONFIGSPECIFIC and DIREG_DEV cases in SetupDiCreateDevRegKeyW
- Implemented SetupDiInstallClassExA
- Implemented SetupDiInstallClassExW (partially)
- Implemented SetupDiGetActualSectionToInstallExA/W
- Implemented SetupDiGetDeviceInfoListClass
- Implemented SetupDiChangeState
- Implemented SetupDiSetClassInstallParamsW
- Implemented internal function ResetDevice()
- Implemented CM_Disable_DevNode[_Ex]
- Implemented CM_Enable_DevNode[_Ex]
- Implemented CM_Reenumerate_DevNode[_Ex]
- Implemented CM_Run_Detection[_Ex]
- Implemented StringTableAddStringEx
- Implemented StringTableLookUpStringEx
- Install "ClassInstall32.Services" section in SetupDiInstallClassExW
- Parse 'Include' and 'Needs' directives in SetupInstallFromInfSectionW and when installing services
- Added stub for SetupDiChangeState
Shell32
- Don't wait 10 seconds after starting an app via a .lnk shortcut file
SMSS
- Implemented system handling of page file creation sizes, Later Reverted
Techbot (IRC)
- Implemented "!bug
" command
Vendor Drops
- WINE 0.9.3
- Dxdiagn from WINE
Vendor Imports
- Imm32 from WINE
- Dxdiagn from WINE
WineCalc
- Hex->Dec, Bin->Dec, and Oct->Dec conversions now work correctly
USB
- Minimize differences between UHCI and OHCI
User32
- Implemented LB_INSERTSTRING_UPPER
- Implemented LB_INSERTSTRING_LOWER
- Implemented LB_ADDSTRING_UPPER
- Implemented LB_ADDSTRING_LOWER
XML Files
- AllowWarnings = True, so Explorer, iBrowser, and Telnet can be built with dbg=0
Next Week?
It's Christmas! I think a Boxing Day issue would suit better, and next week, I'll be explaining how even a Eye-Dee-Ten-Tee User can download, compile, and Install their very own copy of ReactOS, straight from the SVN Trunk.
Until Next Week.. Happy Compiling!
Stuart "TwoTailedFox" Robbins
ReactOS Weekly Newsletter Editor
top
