Release 0.8.0?

[danielshahaf]

I wonder if we should release master as 0.8.0 so we can immediately after that merge redrawhook, which is overdue. Thoughts? How long should the pre-release freeze be (waiting for bug reports from users of HEAD)?

Does current master perform acceptably?

---

EDIT: Here's a list of some tasks; interdependent tasks are separated by rules:

---

• Check performance — Checked and filed Global aliases cause performance regression #728. Further discussion should happen there.

---

• feature/redrawhook breaks zsh-autosuggestions #579 Fix z-asug interoperability: zsh-syntax-highlighting interoperability: Please register zle-line-pre-redraw hooks zsh-autosuggestions#529
• Merge feature/redrawhook: redrawhook issues #245 Use zle-line-pre-redraw (the feature/redrawhook branch) #749
  • Triage widget-wrapping issues
  • Triage feature:redrawhook issues
• (nice to have) Merge Question: have the driver sourced in zsh emulation? #688 (comment)

---

• Send Support an 'owner' key in region_highlight. zsh#57 to zsh upstream — done.
• Merge our patch Avoid emptying the whole of region_highlight #418 (comment) that relies on it (fixes Doesn't work alongside zsh-syntax-highlight? okapia/zsh-viexchange#1 (comment)) — postponed to 0.9.0 since it can't be released before the zsh patch is merged and released — will be in 0.8.0 after all, see Avoid emptying the whole of region_highlight #418 (comment).
• Review the changelog entry for Avoid emptying the whole of region_highlight #418 (it's right at the top of changelog)

---

• Merge Add comments for the platform dependency of the regex module #747

---

• (nice to have) Merge 'main': Highlight backslash escape sequences outside quotes. #706

[phy1729]

I had assumed redrawhook was getting merged this cycle. If memory serves it's ready for merge just wasn't because it was late in the 0.7.0 cycle. I can take another look tonight if you like,

[danielshahaf]

Could do it that way too. It's just there's a bunch of changes already in for days so I wondered whether to split the release cycle so as to get them out before destabilizing master again. Cheers

[danielshahaf]

For clarity, I'm not proposing any change to the schedule for merging and releasing redrawhook: the dates on which it will be merged and released don't depend on whether the merge will be preceded by a 0.8.0 tag.

[danielshahaf]

@phy1729 Is the next step to review performance of master, or to merge redrawhook, or to release and then merge redrawhook? Not trying to rehash; just not clear to me what we decided…

[phy1729]

I think redrawhook should be merged considering how many issues it solves. Not NACK'ing releasing 0.8.0 first (version numbers are cheap), but redrawhook has been waiting for a long time.

[danielshahaf]

I was going to just merge it (there's only a trivial conflict), but there's #579. Let's discuss there.

[danielshahaf]

Does current master perform acceptably?

There's a regression: #728.

[danielshahaf]

I'm going through the redrawhook issues now. Merging redrawhook fixes at least seven seventeen different bugs, so I'll probably tag a prerelease before merging it, so as to have a point of reference. Probably going to call it 0.8.0-beta1.

[danielshahaf]

After IRC discussion, called it 0.8.0-alpha1-pre-redrawhook. That's the tag to use for testing the memo= feature, too.

[danielshahaf]

redrawhook is merged.

[danielshahaf]

And the merge went well. I think we have two options:

• Review the milestone again, merge whatever is ready now (e.g., PR Add comments for the platform dependency of the regex module #747), release master as 0.8.0, and then move forward on everything else
• Delay the release until [some issues and/or PRs] are addressed.

@phy1729 WDYT?