Questions about development version and giving feedback

[VisitingPlayer]

Hi there!

Like I guess many people I'm also exited for SuperTuxKart to recieve a big improvement with the work on SuperTuxKart Evolution.

Recently, I wanted to test some of the new things out, to get a view of the current development. So I build the development version according to the instructions as mentioned in this post. 

Looking at some of the new tracks and game ideas was interesting. I have already started to like the new Fort Magma map. But I also noticed some issues. Some are to be expected in a development version, like some parts of the map not being fully done. But there are other issues I think could be worth mentioning. For example, on the bridge section relatively at the start of that map, it is possible to get stuck at the skeleton and then having issues progressing, as resets also tend to place you in difficult spots to continue.

Now, I do understand that this is all work in progress and still missing several iterations of improvements. 

What prompted me to write this post was however when I noticed the asset repository had it's last update three months ago. Which seems a bit odd, considering that I doubt development just stopped for that long.

So, I wanted to ask the question:
If I wanted to have the most up-to-date state of development, is the GitHub repository for the assets still the right place to look? Or have the Evolution assets since moved to the SVN repository (or another place for that matter). 
Also, suppose I play around in a development build and find an issue with the tracks, like the one mentioned above with Fort Magma's skeleton, where should they be discussed? Or should I maybe just let you work on it for now until some official alpha?

[Alayan]

Hello!

If I wanted to have the most up-to-date state of development, is the GitHub repository for the assets still the right place to look? Or have the Evolution assets since moved to the SVN repository (or another place for that matter).

Yes, that's still the place to look at. Once the Evolution branch is merged into the master branch, we are probably going to rely on the SVN more directly.

The fact that you don't see updates on either repo comes from the fact that many changes happening behind the scenes to old & new tracks have not been pushed on a public repo yet.

Also, suppose I play around in a development build and find an issue with the tracks, like the one mentioned above with Fort Magma's skeleton, where should they be discussed? Or should I maybe just let you work on it for now until some official alpha?

I would suggest having a small document in which you write down issues you notice for now, but waiting around for an official alpha/beta to test if those are still applicable, and then telling us what those issues are, either here on the forum or via a ticket on GitHub.

An exception would be tracks that are already released in 1.5 (or its gift package), where I don't think you need to wait to report relevant issues, as those tracks are not WIPs. Although don't bother with Snow Peak, Fort Magma, Scotland and Minigolf, as those tracks are going to be either removed or completely redone.