meta-issue: learn-ocaml 0.13.1+ release plan and milestones suggestions for upcoming releases #437
Closed
15 tasks done
Labels
kind: meta
Meta discussion beyond a mere feature or defect
Milestone
Hi all,
This issue aims to document the release plan as well as possible milestones for issues/PRs before setting them.
We'll close this issue as soon as learn-ocaml 0.14.1 is released.
(feel free to comment below for questions/remarks if need be)
0.13.1
Bug: Unable to access inside "Actions" menubar button #444
fix(UI): Display teacher_menubar (Actions) properly in responsive mode #450
Bug: grader report may display negative numbers without mandatory parenthesis around them #440
fix(grader): Display negative numbers with mandatory parens #448
fix(UI): Fix CSS bug regarding the loading animation #445
v
-prefix-free)ci: Ensure release-please triggers docker/build-push-action jobs #443
Progress bar for students is not displayed on a fresh repository #314
Fail to view student contributions #337
A few fixes, in particular for student follow-up on new repos #439
0.14.0
*.opam.locked
→ https://github.com/ocaml-sf/learn-ocaml/wiki/Checklist-for-testing-and-merging-a-PR
CONTRIBUTING.md
, including Conventional Commits, BREAKING-CHANGE syntax, structure of a PRdocs: Add
CONTRIBUTING.md
file #452Improve PR/issues templates #453
docs: Improve
{ISSUE,PULL_REQUEST}_TEMPLATE
s, slightly #464learn-ocaml build -j 2
learn-ocaml build -j 2
is broken #414Fix
learn-ocaml build -j 2
issue #416 • Draft[build] Generate
given_exo.{cmi,cmo,cmt}
files #458 (first commit)fix(docker): Add missing libs for compiler-libs related features #459
fix(grader): Workaround issue #457 about the
Introspection
module #461fix(UI): Restore the UX of welcome message "Choose an activity." #455
Offer better protections against solution overwriting #372 opened on Dec 22, 2020 by yurug
Enhance the web UX for students clicking too much onSync
, avoiding empty commits. → subsumed by#372
0.14.1
Bug: Mechanism-2 of PR #372 does not work #505
→ chore(master): release 0.14.1 #486
The text was updated successfully, but these errors were encountered: