Until Today the java provider, used the guava cache to store the flags and the segments. Using the guava cache is now discouraged by the guava team.

In order to follow the guidance of the guava team, we have decided to migrate the internal cache of the Java provider from guava to caffeine.

This may create a breaking change for you if you were using a custom cache configuration with the guava cache in your provider.
Because of this, the cache configuration on GoFeatureFlagProviderOptions that used Guava's CacheBuilder is now handled by Caffeine.

We're excited to announce significant improvements to the integration between GO Feature Flag and OpenFeature.

To better serve our users' diverse needs, we've decided to split the previous Go provider into two distinct providers:

• go-feature-flag: For use with the GO Feature Flag relay proxy.
• go-feature-flag-in-process: For direct integration of GO Feature Flag into your application.

Thomas recently delivered a presentation on Feature Flagging in the Software Development Lifecycle (SDLC) for OpenFeature. Given the presentation's public availability, we are pleased to share the slides with you.

Effective management of the feature flag lifecycle is crucial for maximizing the value of feature flags within an organization.

This presentation is covering the following key areas:

• Feature flag lifecycle: Understanding the complete journey of a feature flag.
• Roles and responsibilities: Identifying who owns each phase of the lifecycle.
• Feature flag naming conventions: Best practices for clear and consistent flag identification.
• Preventing flag debt: Strategies for avoiding the accumulation of unused or obsolete flags.
• Involving project managers: The importance of project management collaboration in feature flag initiatives.

By understanding these concepts, you can optimize your feature flagging strategy and drive business success.

We're thrilled to announce a major milestone for GO Feature Flag: full compatibility with mobile applications. That's right, you can now leverage the power of feature flags to optimize your iOS, Android, and React Native apps with unparalleled ease and flexibility.

We're excited to announce that GO Feature Flag is now one of the first flag management systems to support the Open Feature Remote Evaluation Protocol (OFREP) (currently in an experimental stage).

This is a significant step towards the adoption of Open Feature, a community-driven initiative aiming to standardize feature flag management across different platforms.

As software engineers, the process of releasing new features and updates can be both exhilarating and nerve-wracking.
You've put in countless hours of hard work, and the moment has arrived to introduce your latest creation to the world.

But what happens when things don't go as planned? What if a new feature causes unforeseen issues or negatively impacts your users?

This is where feature flags come to the rescue, offering a safety net that allows you to roll back features immediately without waiting for a deployment. In this blog post, we'll explore why feature flags are an essential tool for securing your software releases.

Welcome to this tutorial on using feature flags in Node js with GO Feature Flag and Open Feature SDKs.

In this video, we'll walk you through the process of implementing feature flags in your Node js applications, allowing you to roll out new features gradually and control their visibility in real-time.

In the ever-evolving world of software development, feature flag solutions have become instrumental in enabling continuous integration and deployment. These solutions allow developers to toggle features on and off without deploying new code, providing flexibility and control over feature releases.

But sometimes you need to give context about your flag, is it linked to an issue? Do you need a precise description? ... To respond to this, GO Feature Flag has recently introduced an exciting new feature: the ability to add metadata to each flag configuration.

With the version v1.11.0 of GO Feature Flag, developers can now add valuable metadata to their flag configurations. This metadata serves as additional information linked directly to each flag, allowing for a more comprehensive understanding of its purpose and context. This metadata can include essential details such as issue tracker links, descriptions, or any other information that developers deem relevant.

GO Feature Flag Relay Proxy is a powerful tool that enables you to evaluate your feature flags without deploying code changes. It allows you to test and roll out new features to your users gradually, and to monitor the performance of your code in real-time.

With the recent release of version v1.7.0, GO Feature Flag Relay Proxy introduces a new feature that enhances the security of your feature flag evaluations. This new feature allows you to control who can access your relay proxy by configuring API Keys.

Feature flags are a powerful tool for software development, allowing for more flexible and adaptable development processes.

However, to get the most out of feature flags, it's important to follow some best practices to ensure they are used effectively and efficiently.