Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Status of "Release Candidate March 2018" #224

Closed
araujokth opened this issue Mar 4, 2020 · 2 comments
Closed

Status of "Release Candidate March 2018" #224

araujokth opened this issue Mar 4, 2020 · 2 comments

Comments

@araujokth
Copy link

I was wondering what was the status of the "Release Candidate March 2018" PR #55, as if you are planning to release it in the near future, or this is just a dead branch which is no longer in your plans to be released? I was trying to understand why the PR had not been successful as well as it says tests and checks failed but there is no details on what has failed.

Regarding the further testing that you mention in the PR, is there something in particular you think should be tested which you could use some help with?

I was also wondering about the comment made on the TODO list "Investigate and fix slightly deteriorated performance of map alignment and merging", as I could not find any details about where these problems were detected?

Thanks for the help!

@mfehr
Copy link
Contributor

mfehr commented Mar 4, 2020

Hi @araujokth
That's a good question. There are two major things that prevented us at that time from merging this candidate. The first is that we would need to check and update all tutorials, update some of the data we offer alongside them. It changes some things a bit, as documented in the PR description. So if we did that we better be sure this version is worth the effort. The second issue is that we noticed that one of the tutorial wouldn't work as well anymore (the multi-session, staircase), the alignment wouldn't work properly anymore with the same commands and we couldn't find an explanation that made sense within the time we had available. Hence we were hesitant to merge it.
Since until recently we were developing in a private copy we simply didn't have the resources to stop, transfer the changes, address these things, test that we still get the numbers in the paper, update the doc and wiki, properly assign version numbers, etc. And since people were actively using master, which performed well and they didn't seem to mind it wasn't a priority. And then... well time flies.
We switched to the public version now, at least for the core (develop branch), so this will get easier and might happen, or not.
I know this isn't a very satisfying answer, but that's how it is :)

@araujokth
Copy link
Author

Thanks for the quick reply @mfehr ! I totally understand the dilemma :) So basically no plans yet if and when you guys will make another release right?

Just let me know if I can be of any help for testing, etc.!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants