This article was first published on Lisk Blog - Medium
Everything you need to know about Lisk’s new monorepo — Lisk SDK
We will introduce Lisk Framework and discuss our recent move to merge it along with Elements and Commander to create the Lisk SDK monorepo. We will also discuss the renaming of Core 1.7.0 to 2.0.0 and identify this release as the first role model app created using Lisk’s SDK. Lastly, we will outline the next steps necessary for the release of Alpha SDK.
In preparation for the release of Lisk’s Alpha SDK, we have merged our repositories into a monorepo structure. Today, we will take a closer look at the process of changing to this development strategy. We will also disclose plans for the future of Lisk Core including the renaming of Lisk Core 1.7.0 to 2.0.0. We will also outline how this move improves development speed, code consistency and allows greater accessibility to our products. Lastly, we will discuss what it means for the first initial release of our SDK and what else needs to take place before Alpha goes to Mainnet. Please be aware that the move to a monorepo structure does not affect current node operators and no actions are required to stay compliant with the network.
First of all, what is a monorepo structure?
In the most basic terms, it can be defined as a software development strategy in which code that may refer to multiple projects is stored in the same repository, in our case, on our public GitHub. This particular strategy is used by many tech industry players including Google and Facebook, as well as top open source projects including React and Babel. In the case of Lisk, the move to a monorepo means a couple of changes across our GitHub and product suite.
Monorepo structure enables ...
To keep reading, please go to the original article at:
Lisk Blog - Medium