HW:RM’s Future Development Goes Public
With the release of HW:RM 2.1 the process for future patches is going to be MUCH different. In addition, HW:RM Multiplayer is no longer Beta - so this forum will be renamed shortly.
Moving forward patches will be developed in full view of the public. How will that work?
- There’s now a public build of the upcoming patch accessible via Steam
– In the Properties dialog for HW:RM on Steam, go to the Betas tab, and in the lower box type:ilovehomeworld
– This will unlock a ‘patch_preview’ build that you can change to. You may need to restart Steam to see the actual item in the upper drop-down list. - These forums contain a list of changes in, or intended for, the next patch.
- In addition an ongoing list of known issues is kept here, open for discussion.
Rules / Guidelines
- Feel free to start a topic for an issue that you have. Once a topic can be cleanly converted into an issue it will be edited to reflect the exact issue being tracked, given a number, and added to the global issues list. It may at that point end up in a build changelist. Please do not number your own issues, it will quickly become confusing, and result in Moderator action.
- Once a preview build is underway we’ll work to add things when possible (fixing issue A makes fixing issue B very easy, etc), and the lists will be reflected to show the current state of development.
- A build’s changelist has various states for each entry:
– Pending - The item MAY be addressed in the build if possible. This can mean that development research is required, or we’re waiting for community feedback, etc.
– In Progress - The item is intended to be resolved, and may not yet have been.
– Maybe Fixed - The issue is resolved, but needs verification. If it was an uncommon or hard to catch issue, this status may stick around until a number of people have failed to replicate the issue, or it is clearly resolved.
– Resolved - The issue has been verified as resolved. - Once a changelist is complete (or nearly so), we’ll work with internal QA to determine when it can be given adequate review and a release date.
- The cadence/timing of patches moving from preview to public will not be fast except in unusual circumstances (major exploit, etc). A few weeks to a few months should not be unusual.
- The frequency with which the preview is updated will vary, but ideally should be a few times a week.