MonoGame 3.7

Releases
7

Awesome :slight_smile:

Thankā€™s for updating the PCL as well!

8

The change log is awesome :scream:
:heart_eyes:

9

Yay, mipmaps work correctly on Android now! Thanks a lot guys, great release :slight_smile:

1 Like
10

Thank you MG developers for your work on the new release. Your work is really appreciated keeping this awesome project alive. Cheers :beers:

1 Like
11

Brilliant work MG guys!:tada:

1 Like
12

Way to go guys! Keep up the good work - canā€™t wait to try out the new bits!

13

Fantastic release, you guys rock!

14

no!, they www.monogame.rocks !

1 Like
15

hahahah, very good :slight_smile:

1 Like
16

After installing 3.7 for Visual Studio, I made a new project and when I clicked on start before doing anything else I get this error.

Exception: Failed to load SDL library.

I also get the same error on existing projects.
I uninstalled 3.6 before installing 3.7. Was I supposed to do something else?

17

What is the current state of MonoGame and XNAā€™s

using Microsoft.Xna.Framework.GamerServices;
using Microsoft.Xna.Framework.Net;

As you can still run Games for Windows Live on Windows 10, but you cannot login to an online account(?). Are any of these libraries able to be ported to UWP and the like?

20

Starting in Monogame with great news :smiley:

21

Great work, everyone! :clap:

(Hey @Tom, just noticed this announcement still isnā€™t a ā€œNewsā€ item on the main website!)
#MissingATrick :wink:

1 Like
22

Considering how little news we have, weā€™ve talked about removing that page in favor of the Twitter account.

1 Like
23

That is what iā€™d like to do. Just havenā€™t had the time to refactor the code on the home page to do that.

Was also considering maybe pulling posts here from Discourse as news posts.

Anything other than old Wordpress blog junk.

3 Likes
24

Hi!

Iā€™m pretty new to MonoGame, and it looks awesome so far. Well done!

Iā€™m quite impressed by the amount of issues included in the 3.7 release. I wonder whether releases are too big though. Iā€™ve noticed it takes 1-1.5 years to release a minor version. Would it make sense to release more often? I know that we can work from the develop branch, but having official releases is usually helpful, and I feel like making them more often would be a good thing, even if they are smaller of course.

2 Likes
25

Just noticed that there is an update, will definitely check!

Please put this in HEADLINE page so that others will know monogame is still alive and kicking :slight_smile:

26

Thanks a lot guys, I really appreciate your work!

27

Hi @srodrigoDev.

I agreeā€¦ it would be better to release more often. This has been our goal for a few years nowā€¦ we just havenā€™t been able to meet it.

Mostly the issue is not knowing if the develop branch is stable enough to replace the current stable release. In theory it should beā€¦ but 99% of the testing is Windows PC builds and very few people test the mobile, UWP, or Mac/Linux backends.

We are making that better in a few ways.

First by focusing on getting more automated testing into the build servers and run those tests on more platforms.
This is hard to do rightā€¦ but weā€™re trying to push that forward little by little.

Second we are starting to push out development builds periodically on NuGet which tells us how many people actually at least tried using that develop build for a particular platform. Like i know now that 68 people used the iOS version of MonoGame 3.7.0.1681-develop ā€¦ knowing that gives us confidence that it isnā€™t completely untested.

Last and most important i am having to learn not to care so much. If MG is buggy when we release it isnā€™t my personal fault. It is an open source project and how good it is or isnā€™t is a reflection more on the community than me personally. Worst case if it is really buggy there are a dozen older versions on NuGet or we can push a fix in a minor release. What we cannot do any longer is wait to ship.

1 Like
28

Thanks @Tom, that makes a lot of sense. I had the feeling that I didnā€™t have the context needed behind the current approach. And I think, given the small team behind MonoGame, itā€™s a very reasonable approach, specially for less used platforms, as you mentioned.

I agree that increasing the automated test coverage could definitely help. In any case, I wouldnā€™t be extremely concern about breaking changes. The reason is that, with smaller releases, itā€™s easier to feel more confident about the stability of the development branch, and also itā€™s probably easier to manually test when the automated tests suite canā€™t help, as there are far less things to test. Smaller releases are also a good ā€œcheck pointā€ in case there is something broken, as users could revert back without loosing much functionality.

I also agree with getting the community more involved. As an idea, I wonder if releasing a release candidate version could help? Iā€™m not even sure if this is done already, as I landed here a few weeks ago. But maybe that way it would help both getting users more involved in testing (people usually jump into new oficial versions more than particular commits on the current development branch), and also being more confident with releasing more often.

Also, itā€™s important to remind users to report bugs, instead of trying to fix them ourselves. I remember reading something about this about MonoGame somewhereā€¦

2 Likes