Happy Friday! This one’s brief.
Merged RFCs RFC #37: prototypes has landed! …but it probably could have use more detail regarding the run step, which is the only immediately actionable part of it. 🤔 I’ll draft another RFC for that; #37 mainly covered the protocol. RFC #38: resource prototypes is in! Its associated issue for implementation is #5870. RFCs to merge n/a - taking a breather for this round-up to focus on the below RFCs and “reset” the 2 week merge window so I can start publishing these posts earlier in the week.
With the four(!) RFCs from the last round-up now merged, it’s time to move on to the next RFC milestone: Prototypes!
Merged RFCs 🎉 RFC #31: set_pipeline step RFC #40: valid identifiers RFC #39: var sources RFC #27: var steps RFCs ready to merge 🤞 RFC #37: Prototypes is finally ready to go! For (much) further reading, check out the Re-inventing resource types blog post. The importance of this RFC really cannot be overstated; it will be the most significant change to Concourse since its creation.
First off: sorry, I immediately failed to keep my target pace for these. 😓 I got wrapped up in a deadline, and since I alternate weeks between engineering and community duties like this post, when I miss a week for RFC updates the 2-week interval can quickly turn into 4 or 5.
Owing to the missed round-up, and in hopes of burning through the backlog more quickly so that interested contributors may volunteer for merged RFCs, I’m going to expand the scope of this post to include more RFCs than the last one - primarily by proposing that we merge ones that are nearly certain for the v10 roadmap.
Howdy, and welcome to our first RFC round-up! ðŸ¤
For those unaware, Concourse RFCs are a process for proposing and collaborating on improvements to core Concourse functionality, including pipeline behavior, new step types, new operator capabilities, etc.
In short, RFCs are where all the cool new stuff is planned. 😎
My goal is to provide an update at least every few weeks on the status of RFCs and shepherd them through the process via blog posts like this one.