<story><title>FF4J – Feature Flags for Java</title><url>https://ff4j.github.io/</url></story><parent_chain></parent_chain><comment><author>tantalor</author><text>&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;ff4j&amp;#x2F;ff4j&amp;#x2F;blob&amp;#x2F;v1&amp;#x2F;ff4j-core&amp;#x2F;src&amp;#x2F;main&amp;#x2F;java&amp;#x2F;org&amp;#x2F;ff4j&amp;#x2F;strategy&amp;#x2F;time&amp;#x2F;ReleaseDateFlipStrategy.java#L100&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;ff4j&amp;#x2F;ff4j&amp;#x2F;blob&amp;#x2F;v1&amp;#x2F;ff4j-core&amp;#x2F;src&amp;#x2F;main&amp;#x2F;java...&lt;/a&gt;&lt;p&gt;&amp;gt; The feature will be flipped after release date is reached.&lt;p&gt;Don&amp;#x27;t ever use this. This is a &amp;quot;time bomb&amp;quot;. This is a very bad idea. It&amp;#x27;s basically like scheduling a time for your app to go down when you aren&amp;#x27;t paying attention.&lt;p&gt;You have to have a human in the loop. The right way to &amp;quot;schedule a release&amp;quot; is to have a human flip the flag at the appropriate time (preferably, ramp it up to 100% of users gradually) and then stay online for a little while to do an emergency ramp down if&amp;#x2F;when things go bad (that weren&amp;#x27;t caught by some automated system in the ramp up).</text></comment>
<story><title>FF4J – Feature Flags for Java</title><url>https://ff4j.github.io/</url></story><parent_chain></parent_chain><comment><author>nprateem</author><text>Having recently kind of abandoned golang for Java, I&amp;#x27;ve got to say I love the richness of the Spring ecosystem.</text></comment>