[mosh-devel] Working towards a mosh 1.4 release
Dave Taht
dave.taht at gmail.com
Mon May 30 23:10:07 EDT 2022
happy to see this. My biggest feature request is to get rid of perl.
On Mon, May 30, 2022 at 5:31 PM Alex Chernyakhovsky <achernya at mit.edu> wrote:
>
> Hi folks,
>
> I wanted to give everyone an update on the progress that has been made
> on a mosh release so far. Our industrious group of volunteers has
> worked through the spreadsheet and identified 1 PR that needs fuzzing
> and 6 PRs that need additional testing. We've merged PRs for
> generating coverage reports
> (https://github.com/mobile-shell/mosh/pull/1173) and fuzzing
> infrastructure (https://github.com/mobile-shell/mosh/pull/1193).
>
> Next steps are now to work through these remaining actions items
> identified in the review, as well as hook up the fuzzing targets to
> OSS-Fuzz for continuous execution, and then it will be time to release
> a release candidate.
>
> Sincerely,
> -Alex
>
> On Sun, Feb 6, 2022 at 8:53 PM Alex Chernyakhovsky <achernya at mit.edu> wrote:
> >
> > Hi folks,
> >
> > I've done some preliminary work to see what it would take to produce a
> > (tentatively) mosh 1.4.0 release. Wolfgang has kindly kicked off the
> > process and set up Github Actions for CI, replacing the Travis CI we
> > had before. I've followed that up with a PR [1] to add support for
> > generating coverage reports, and run it at head so far [2].
> >
> > There have been approximately 100 commits merged since mosh 1.3.2 was
> > released in 2017. Our goal is to review each of these commits and
> > either
> >
> > a) conclude it's good as-is
> > b) it needs improved test coverage
> > c) it needs a fuzz test
> > d) something else entirely
> >
> > To help with this, I've produced a spreadsheet [3] using `
> > git log mosh-1.3.2..master~3 --oneline
> > --pretty='=HYPERLINK("https://github.com/mobile-shell/mosh/commit/%H",
> > "%h 🔗")|%s'` and have added columns for folks to indicate they've
> > reviewed a commit and what the outcome is. The sheet is
> > world-readable, but please ping me for editor access if you're going
> > to volunteer to review some of these commits.
> >
> > Once we've reviewed these commits and added any tests / fuzz tests as
> > needed, we should be ready to make a preview release. My goal is to
> > upload this to Debian experimental and encourage folks to test once
> > it's there.
> >
> > At this time, I don't think we should be merging any of the
> > outstanding ~40 PRs unless they're fixing outstanding bugs. Any
> > features still under review should be deferred until after the 1.4
> > release.
> >
> > Please let me know if you have any thoughts or suggestions.
> >
> > Sincerely,
> > -Alex
> >
> > [1] https://github.com/mobile-shell/mosh/pull/1173
> > [2] https://web.mit.edu/achernya/Public/mosh-1.3.2-105-gdbe419d-coverage/
> > [3] https://docs.google.com/spreadsheets/d/1GYlnYD8OaoINDo8ZZTwrZGRR3rEgtMGB3_38i6AcMQ8/edit#gid=0
>
> _______________________________________________
> mosh-devel mailing list
> mosh-devel at mit.edu
> https://mailman.mit.edu/mailman/listinfo/mosh-devel
--
FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
Dave Täht CEO, TekLibre, LLC
More information about the mosh-devel
mailing list