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

New release of NEST #53

Closed
kreczko opened this issue May 15, 2020 · 3 comments
Closed

New release of NEST #53

kreczko opened this issue May 15, 2020 · 3 comments

Comments

@kreczko
Copy link
Contributor

kreczko commented May 15, 2020

Dear all,

I have to admit I am not aware of the NEST versioning policy, so please let me know.

NEST uses the format of .. scheme for versioning, which usually means relatively frequent releases (which I am a fan of). However, the last release is already 10 months old - all the new and improved bits are only available in master.

Would it be possible to please release a new version? At LZ we have developers burning to use the latest features and bug fixes:
v2.0.1...master

@mszydagis
Copy link
Collaborator

hi Luke, you must have missed somehow my numerous (verbal only though, not written) announcements at multiple LZ phone meetings the past few weeks: We (including/especially me) are working around the clock towards a new release. A pre-release beta-test version is coming out in 2 weeks for people to do checks with, like compatibility with LZ software, etc.

@kreczko
Copy link
Contributor Author

kreczko commented May 15, 2020

Awesome thanks!

Indeed, I must have missed them, my memory has not been the best lately.

Looking forward to the new version

@mszydagis
Copy link
Collaborator

One thing that is slowing things down, but that you will be appreciate immensely I am sure: a whole suite of validation plots to make sure nothing gets broken by accident during new releases :)

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