You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think we should create changelogs and follow some versioning system. It'll allow us to change supported versions of Racket and Node.js for every single major version of RacketScript.
I'm not sure we can completely rely on racket versions because we have node.js as a second major tool. Thus, maybe it's better to have our versioning system just to have an ability to change versions when we need to do that. Because future users of RacketScript will rely on the RacketScript's versions mostly.
Activity
stchang commentedon May 18, 2021
Open to suggestions, but otherwise we'll just follow Racket's major-minor-patch versioning system.
daynin commentedon May 18, 2021
I'm not sure we can completely rely on racket versions because we have node.js as a second major tool. Thus, maybe it's better to have our versioning system just to have an ability to change versions when we need to do that. Because future users of RacketScript will rely on the RacketScript's versions mostly.
stchang commentedon May 18, 2021
Oh I didn't mean to match Racket's exact version. Just to use Racket's version numbering conventions.
daynin commentedon May 18, 2021
Oh, I see. Yeah I think it's a great idea!