Please don't confuse a real alpha with the popularized open betas that are just glorified demos. Bugs like these are incredibly common in alphas and while they need to be reported the goal of an alpha is to try and finalize content and make sure the build is stable. Once the content is final then the quality changes start and this is when beta begins. Features can still be added throughout the beta but if the build stability gets worse these are reverted. Bugs are rarely resolved in alphas unless they affect build stability, otherwise they are logged and fixed once the build enters beta (or at least that was how we did it).

In the case of Martyr, the release build failed certification for one of the console versions but the build is as close to final as possible. This build is not the same as the closed alpha build that PC currently has. Also, the latest update for the alpha was more than likely not even current and was probably compiled from an older build and given to the early supporters to hold them over until release. As the release date was delayed by a month the newly announced beta is simply another way to appease the supporters and gain some additional feedback before release.

You do realize that this is still an alpha build, right? At least wait until the beta build releases on the 21st before crying about an outdated build. If it is still broken then you can call the devs incompetent but alpha phases are for stability, not bug sweeps.