Closed kytrinyx closed 7 years ago
@Theodus I don't know enough to understand why the build can't install dependencies. Do you have a moment to look at this?
@kytrinyx I believe this is caused a breakage we had on ponyc master regarding older c compilers, it should be resolved now. I've restarted the builds.
I've rebased onto master, but it didn't pick up any new changes. The build is still failing.
Build with recent changes is now passing. The other isn't for some reason, but It is obviously behind the master branch.
Very strange, let me try this again.
And there she goes. OK, I think we'll be good this time.
We will be moving to a tree-shaped track rather than a linear one, as described in the progression & learning in Exercism design document.
In order to support this, we need to expand the metadata that exercises are configured with.
Note that 'core' exercises are never unlocked by any other exercises. Core exercises appear in the track in the order that they are listed in the array.
Non-core exercises depend on only one exercise (unlocked_by: ). At the moment we are assuming that this is a core exercise, but there is no reason that it needs to be.
Until now we have operated with a separate deprecated array. These are now being moved into the exercises array with a deprecated field.
With these defaults the track in nextercism will have no core exercises, and all the exercises will be available as 'extras' from the start.
If you haven't already, now would be a good time to do the following:
If possible, leave 3 or 4 simple exercises as (core: false, unlocked_by: null), as this will provide new participants with some exercises that they can tackle even if they have not finished the first core exercise.
See https://github.com/exercism/meta/issues/16