Story 17.8 — R1 blog series + LinkedIn cadence (elasticsql)#150
Closed
fupelaqu wants to merge 1 commit into
Closed
Story 17.8 — R1 blog series + LinkedIn cadence (elasticsql)#150fupelaqu wants to merge 1 commit into
fupelaqu wants to merge 1 commit into
Conversation
…ar (Story 17.8) Channel B (Medium / personal LinkedIn; site collection deferred). Commits the R1 marketing content so launch copy is written ahead of time. - blogs/: 4 R1 posts (announcing-r1, join-matrix, sre-triage, customer-usage), each with >=1 LIVE cross-link; pending targets carry tracked markers. - linkedin/: 4 staged drafts (launch / demo / BI showcase / federation reveal) + r1-editorial-calendar.md (J+0/7/14/21, Epic-18 non-overlap + R2a 90-day hold). Guards: price EUR 119 never 129; no hard perf numbers (Arrow benchmark reserved for R1.1/Epic 18); ELv2 not source-available; Power BI never ADBC-default-driver; tested-vs-compatible tool wording; Post 4 ships fully anonymized. Last story of Epic 17. Closed Issue #149 Refs #148 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
Author
|
Closing: this PR contained only blog posts (blogs/) and LinkedIn drafts (linkedin/), which are local-only working material and must not be committed to the public elasticsql repo. They are being rewritten as local, untracked drafts in elasticsql/blogs/. The Story 17.8 landing-page work lives in the softclient4es-web PR. Deleting the feature/17.8 branch. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Epic 17 (R1 Documentation & Marketing) — last story. elasticsql side, Channel B.
Commits the R1 marketing content so launch copy is written ahead of time.
What landed
blogcollection deferred per OQ#2):announcing-r1-cross-cluster-join.md(J+0) ·join-matrix-walkthrough.md(J+7) ·sre-cross-cluster-incident-triage.md(J+14) ·how-customers-use-r1.md(J+21, fully-anonymized)r1-launch-announcement·r1-demo-teaser·r1-bi-showcase·r1-federation-reveal+r1-editorial-calendar.mdblogs/+linkedin/were untracked before this PR — these are the first committed copies. No binary PNG/PDF committed (hero images staged at publish time).Guards honored
/sql/joins/17.1,/integrations/federation-helm/17.2) carry tracked<!-- pending -->markers for the epic-close launch-gate.Sibling Epic-17 PRs (cross-link launch-gate)
elasticsql: #137 (17.1) · #141 (17.6) · #124 (17.2) · #145 (17.3) · #143 (17.4) · #147 (17.5) · #140 (17.2 tracking) — plus web #12/#17/#8/#21/#19/#23/#6.
Closes #149
Refs #148