[ 
https://issues.apache.org/jira/browse/GEODE-10461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18020906#comment-18020906
 ] 

ASF subversion and git services commented on GEODE-10461:
---------------------------------------------------------

Commit 17c64496f559c9df74b2fc4fcbb52c7d028437c3 in geode-examples's branch 
refs/heads/support/1.15 from Jinwoo Hwang
[ https://gitbox.apache.org/repos/asf?p=geode-examples.git;h=17c6449 ]

GEODE-10461: Bump version to 1.15.2

As part of the Geode Release Process, the geode-examples build number
must be rolled forward as work begins on the next release


> Release 1.15.2
> --------------
>
>                 Key: GEODE-10461
>                 URL: https://issues.apache.org/jira/browse/GEODE-10461
>             Project: Geode
>          Issue Type: Task
>            Reporter: Jinwoo Hwang
>            Priority: Major
>
> h3. Summary
> Prepare and publish Apache Geode 1.15.2 (maintenance release on 1.15.x line) 
> addressing critical bugs, stability, security, and dependency updates.
> h3. Objectives
>  * Produce signed source release + binaries
>  * Stage & vote on one or more Release Candidates (RCs)
>  * Publish approved artifacts to dist + Maven Central
>  * Update docs, website, and announce
> h3. Key Dates (proposed)
>  * Branch cut / freeze: T0
>  * RC1 build + staging: T0 + 1d
>  * Community vote window (72h minimum)
>  * Target release publishing: T0 + ~7–10d
> h3. Scope (high‑level)
>  * Bug fixes since 1.15.1 (list JIRA issues once finalized)
>  * Dependency updates (enumerate once locked)
>  * No new incompatible API changes
>  * CVE fixes (if any; enumerate or “none”)
> h3. Preconditions
>  * PGP key present in KEYS and on keyservers
>  * All JIRA issues for 1.15.2 in “Resolved” / “Fixed” state
>  * CHANGELOG / RELEASE_NOTES updated
>  * All tests (unit, integration, distributed, benchmarks) green in CI
>  * License / NOTICE review complete
>  * Third‑party dependency audit (no forbidden or unexpected upgrades)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to