* Otherwise, you might have to stop the TLS Termination Proxy momentarily, start the renewal program to acquire the certificates, then configure them with the TLS Termination Proxy, and then restart the TLS Termination Proxy. This is not ideal, as your app(s) will not be available during the time that the TLS Termination Proxy is off.

	now := time.Now()

	// Check for existing item
	if ent, ok := c.items[key]; ok {
		c.evictList.MoveToFront(ent)
		c.removeFromBucket(ent) // remove the entry from its current bucket as expiresAt is renewed
		ent.Value = value
		ent.ExpiresAt = now.Add(c.ttl)
		c.addToBucket(ent)
		return false
	}

	// Add new item
	ent := c.evictList.PushFrontExpirable(key, value, now.Add(c.ttl))
	c.items[key] = ent

        return ROLE_ASSISTANT.equals(role);
    }

    /**
     * Gets the HTML-rendered content.
     *
     * @return the HTML content, or null if not rendered
     */
    public String getHtmlContent() {
        return htmlContent;
    }

    /**
     * Sets the HTML-rendered content.
     *
     * @param htmlContent the HTML content
     */

import java.io.File;
import java.util.Collections;
import java.util.HashMap;
import java.util.Map;

/**
 * Takes a rendered release notes HTML file and decorates it with extra elements/content/links.
 */
@CacheableTask
public abstract class DecorateReleaseNotes extends DefaultTask {
    /**
     * The rendered HTML release notes that need decoration.
     */
    @InputFile
    @PathSensitive(PathSensitivity.NONE)

Public properties are **stable properties**: they CANNOT be renamed or removed without notice.
While we normally deprecate the feature or behavior itself, changes to the property cannot happen in a minor release.
Public properties must be documented.

**Internal properties** are not part of the Public API.
Internal properties are **unstable properties**: they CAN be renamed or removed without notice.
They are not intended for general use.

    /**
     * The location of the release notes assets
     */
    public abstract DirectoryProperty getReleaseNotesAssets();

    // TODO: Need staging root property too

    /**
     * The collection of rendered documentation.
     */
    public abstract RegularFileProperty getRenderedDocumentation();

    # Messages to create or check
    new_translation_message = f"Good news everyone! 😉 There's a new translation PR to be reviewed: #{pr.number} by @{pr.user.login}. 🎉 This requires 2 approvals from native speakers to be merged. 🤓"
    done_translation_message = f"~There's a new translation PR to be reviewed: #{pr.number} by @{pr.user.login}~ Good job! This is done. 🍰☕"

    # Normally only one language, but still
    for lang in langs:

* To avoid asking the same thing multiple times during code review.
* To explain *rejected solutions*, for now, and future development, in case they are proposed again.

ADRs can be written by any team.
Like code, they should be reviewed by any other relevant teams.
The goal is not to *own* a decision, but to *share* it with other teams, and improve the build tool together.

### Format

The format for ADR should follow this template:

```markdown

    /**
     * Additional resources to include in the final docs
     */
    public abstract ConfigurableFileCollection getResources();

    /**
     * A collection of the final rendered user manual
     */
    public abstract ConfigurableFileCollection getRenderedDocumentation();

* **Third-party APIs and libraries**: When integrating with external APIs that use different spelling conventions
* **Historical compatibility**: Existing public API methods that are part of Gradle's stable API cannot be renamed due to backward compatibility requirements (though new APIs should use American English)
* **Proper nouns and quotes**: Names of organizations, products, or quoted text that use different conventions

## Consequences