- Moderator
- #11
Look simple enough. Tested by Seb and HomeY, so do you feel this is ready to merge?
It's ready to merge for sure
When all fixes ready to merge will be ready, i would say to take decision about 'safe / showstopper etc.' and go to merge
Look simple enough. Tested by Seb and HomeY, so do you feel this is ready to merge?
Look simple enough. Tested by Seb and HomeY, so do you feel this is ready to merge?
It's ready to merge for sure
When all fixes ready to merge will be ready, i would say to take decision about 'safe / showstopper etc.' and go to merge![]()
So that automatically means it's being included in v1.3.1 after the Final is out.Well, there's no way this is a show-stopper. MP is a fullscreen program.
So that automatically means it's being included in v1.3.1 after the Final is out.Well, there's no way this is a show-stopper. MP is a fullscreen program.
Just noticed i clicked the wrong version in Mantis (had 1.3.0 as target) so updated to 1.3.1
The Code Freeze period would be the right time for that i assume. And all outstanding 'Ready for Testing' issues we have in Mantis now, which aren't going in the Final, should automatically go in the 1.3.1 Maintenance Release.At some point what we need to do is clear out 1.3.1 and 1.4.0 of anything that is not complete and ready for testing.