Provide a solution document for #206 #219
Conversation
"Current Rakudo (possibly MoarVM as well) development process hinders releasing" Fixes Raku#206
|
@patrickbkr just a thought, can we easily have CI for 32-bit platforms too? Is it already there or not? IIRC there was one point release associated with a 32-bit-specific bug, and after that I used https://github.com/perl6/rakudo-pkg-canary before every release to make sure we don't break something again. |
There was a problem hiding this comment.
Exciting stuff! Totally makes sense to me, and I hope that OBS will actually provide potential for more kinds of testing (e.g. running tests of popular modules, etc.). I guess the only debatable topic here is the PR-only policy, but it's hard to object to it because devs can't know themselves if their changes are causing breakage on other platforms, so having to check CI status before merging into master is essential at this point.
Thank you for your work!
|
OBS supports building on a variety of architectures, including i586 (i.e. 32 bit): https://build.opensuse.org/project/show/home:niner9:rakudo-git As rakudo/rakudo#3848 shows we may not want to become complete slaves to a process. E.g. what happens if the CI is currently broken? Will we not be able to merge important fixes then? But anyway, I do support a strong encouragement of using PRs and requiring green CI status. And I say that as someone who is usually too impatient to follow the proper process. Let's do this right. |
Fixes #206
I might make some more minor changes on this, so it's still a draft PR. But I do value feedback.
@Altai-man @lizmat @niner