APInf release 0.58.0 is baking in the oven

Ok, we just got the 0.57.0 out. And now we are coming out with 0.58.0 already. What is going on?

0.58.0 is a bit special. This release is going to the latest (7.5) FIWARE release. In the last blog I wrote about the deepening co-operation with FIWARE. Now we are so deep we need scuba gear.

The other major feature is the HSL ID login:

Our intention is to have single master and develop branches. We have limited resources, and at this time we see that maintaining multiple branches would be too resource intensive. The downside of this simplicity is that everything is baked into one.

I understand that people do not want to have all sorts of weird logins and irrelevant features in the API management tool. We are tackling this with configuration. For example we are planning on having a config for the login options on version 0.60.0 so those options that you don’t need can be disabled.

Other strategies are also being considered, like build time variation. We are still on a level that allows us to deal with these features on UI config level. But soon this might not be the case. No worries, we have plans for this.

Few words about our release plans. We are planning to do a stabilization / upgrade / bug fixing. Some of the component versions we are using are quite old and need an update.

After that the 0.60.0 is the “Next”:

Next brings totally new UI and UX. This is the base that we will continue to build on. I’ll be writing more on that later.

Ok, so we got our SaaS and everything, but we are still in versions 0.xx.y. Reason for this is that I don’t want to go for 1.0 unless we have these things in place: Monetization with tokens instead of x-api-keys. We have already tokens in the umbrella and we are looking to leverage FIWARE monetization, but we need to build the support to the platform. Interesting times ahead! Have a nice week end all!