Tagged release?

[dtzWill]

It's awesome seeing the constant improvements you're making!

I maintain a downstream packaging of this, and just wanted to chat/ask about plans for a release? Or is it recommended to follow master?

Thanks!

[ceeac]

Hi!

Yes, for releases I recommend to follow master. I am using the gitflow model for branch management, so 0.4.0 will be tagged in master upon release. However, I am against a release in the near future for several reasons:

1. There are still a number of bugs that need to be fixed. Most prominently, the SPARC decoder is currently broken (Though I am not sure if it will be used much in relation to the x86 decoder)
2. When there is a release, it should imo be a somehow "official" one. I have not yet decided on how to approach this matter, as upstream seems to be unmaintained last time I checked, and also because I wanted to some more refactoring/documentation/unit testing work first.

[dtzWill]

Okay, that all sounds great! Thanks for the thoughtful response and project management, I'll keep following master for the time being and thanks for your continued work!

[ceeac]

@dtzWill just a heads-up: Boomerang is now maintained at BoomerangDecompiler/boomerang. Also, there is going to be a release soon-ish (most likely this year).

[dtzWill]

Great! And thank you for letting me know, I'll update accordingly and keep an eye on development over there!

…

On Thu, 25 Oct 2018 06:09:56 -0700, ceeac ***@***.***> wrote: @dtzWill just a heads-up: Boomerang is now maintained at BoomerangDecompiler/boomerang. Also, there is going to be a release soon-ish (most likely this year). -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #1 (comment) part: text/html