We will be establishing an alternative, better way to communicate which versions are compatible and our recommendation for the stack you should be running – while increasing our ability to get changes to you quickly. Beam Enrich (which already existed as an independant asset for a couple of months). ![]() We’re creating the following new repositories for our subprojects: ![]() ![]() We also would like to use this as a next step in our batch pipeline deprecation process and archive the following components: We expect this change will make development even more OSS-friendly and easier to contribute to. In order to solve that problem we’ve made a decision to split the Snowplow monorepository into individual repositories, each containing code for a single application. However, as Snowplow’s OSS estate was growing, we started to realise that it’s getting harder to maintain this guarantee and that the monorepository approach makes our development process very inflexible as we sometimes had to do an umbrella release and a blog post just for an urgent hot fix. One of the goals of these big bang releases was a compatibility guarantee, which meant that all assets within a single release are compatible with each other. Almost every month we then would do a big bang release with all assets and an associated blog post. This repository holds the whole history of changes back to inception in 2012. Historically, most of Snowplow’s Open Source estate was hosted by a single GitHub monorepository. Hence the Event Recovery job 0.2.0 will be announced soon, which leverages all benefits of the new format. In order to make R119 production-ready we also wanted to make sure that new functionality related to bad rows is on feature-parity (or above) with the legacy format.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |