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

Release Hy 1.0a1 #2032

Merged
merged 1 commit into from
Apr 12, 2021
Merged

Release Hy 1.0a1 #2032

merged 1 commit into from
Apr 12, 2021

Conversation

Kodiologist
Copy link
Member

Typically I do a release every six months, but Hy has been moving so fast now (which I'm quite pleased about, I hasten to add—excellent work, folks) that I'd like to do an earlier release to help ease the pain of transition. Probably there will be another one around the middle of 2021.

I need two approvals from @hylang/core to do this. If I get them, I'll clean up NEWS and make the release.

@peaceamongworlds
Copy link
Contributor

Given that we might be able to complete all of the 1.0 features in the normal release timeframe, would it not make sense to hold of a new release until then? I think that we started this discussion in #2008.

Or maybe we could have a release only with the new bug fixes (looking at the recent prs: #2028, #2024, #2020 etc) and not any of the breaking features (#1975 seems like a big one)? Then we could put of all the breaking features until 1.0, so that users didn't have to re-write their code twice.

I don't really have a strong opinion about this though, so I'm willing to be convinced either way.

@Kodiologist
Copy link
Member Author

Given that we might be able to complete all of the 1.0 features in the normal release timeframe

I don't think that's realistically going to happen.

Or maybe we could have a release only with the new bug fixes

I don't want to manage multiple lines of development before 1.0.

@Kodiologist
Copy link
Member Author

@allison-casey @scauligi Can I get your input here?

@scauligi
Copy link
Member

scauligi commented Apr 8, 2021

Considering the amount of major changes (and upcoming changes), I think it makes more sense to release as an alpha pre-release 1.0a1 instead of 0.21.

@Kodiologist
Copy link
Member Author

Wouldn't that imply something near feature-completeness, or that we'll release 1.0 soon?

@allison-casey
Copy link
Contributor

allison-casey commented Apr 8, 2021

I dont think so, we can have as many alpha releases as we want. python3.9 had 6 alphas and 5 betas before release and we have much less to do than they did. I don't even think we even need to merge bugfixes on 0.20 just leave it as is for people to play around with something that is usable and stable.

@Kodiologist Kodiologist changed the title Release Hy 0.21.0 Release Hy 1.0a1 Apr 8, 2021
@Kodiologist
Copy link
Member Author

Okay, here's a full NEWS cleanup, and a new title for the PR. @allison-casey Do you anticipate any problems getting this new version to work with hy-interpreter?

@allison-casey
Copy link
Contributor

shouldn't be an issue. just need to change the requirements file.

@allison-casey allison-casey self-requested a review April 8, 2021 20:19
@allison-casey
Copy link
Contributor

@scauligi @peaceamongworlds is there any reason not to approve this at this point? we need two approvals for releases.

@Kodiologist
Copy link
Member Author

Thanks. I'll merge this and release it tomorrow or Monday.

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

Successfully merging this pull request may close these issues.

4 participants