Releases: Financial-Times/engineering-progression
v2.1.0
3bfd5fd
rowanmanning
Rowan Manning
Full Changelog: v2.0.0...v2.1.0
v2.0.0
40c00ca
rowanmanning
Rowan Manning
Full Changelog: v1.2.5...v2.0.0
v1.2.5
What's Changed
- Correct the Operations competencies by @rowanmanning in #373
Full Changelog: v1.2.4...v1.2.5
Contributors
Assets 2
v1.2.4
Contributors
Assets 2
v1.2.3
34db692
rowanmanning
Rowan Manning
What's Changed
- Overhaul the build process and competency data structure by @rowanmanning in #371
Full Changelog: v1.2.2...v1.2.3
Contributors
Assets 2
v1.2.2
v1.2.1
What's Changed
- Update the release documentation by @rowanmanning in #362
- Remove the holding page for Principal Engineer competencies by @niksilver in #364
Full Changelog: v1.2.0...v1.2.1
Contributors
Assets 2
v1.2.0
What's Changed
- Add guidance for delivering feedback by @NatashaMcCann in #323
- Correct and clarify documentation. by @niksilver in #358
- Mid-level engineer should be aware of business benefits by @niksilver in #360
- Add Junior Engineer competencies by @niksilver in #359
- updated home group info by @hamza-samih in #357
New Contributors
- @NatashaMcCann made their first contribution in #323
- @niksilver made their first contribution in #358
- @hamza-samih made their first contribution in #357
Full Changelog: v1.1.0...v1.2.0
Contributors
Assets 2
v1.1.0
previously, competencies were listed for the boundary between two seniority levels, e.g. “Mid to Senior 1” for the new competencies a Senior 1 Engineer would be expected to exhibit over a Mid-level Engineer.
to reduce confusion about the purpose of the levels, and make it clearer that the intent of the framework is defining responsibilities at each level, not promotion between levels, we’ve changed this so competencies are listed under only the level you’re expected to exhibit them at, e.g. just “Senior 1".
none of the competencies themselves, or the levels they’re expected at, have changed, so this doesn’t constitute a breaking change to the framework itself, but this is a breaking change to the API, so we’ve bumped that to v2. if you maintain an API integration please talk to us about migrating.