You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pekko.apache.org by fa...@apache.org on 2023/03/06 20:14:04 UTC
[incubator-pekko-connectors] branch main updated: remove-akka-release-train (#36)
This is an automated email from the ASF dual-hosted git repository.
fanningpj pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-pekko-connectors.git
The following commit(s) were added to refs/heads/main by this push:
new 6dee4ac2 remove-akka-release-train (#36)
6dee4ac2 is described below
commit 6dee4ac2c04a843265d5403e44430861efa42d70
Author: PJ Fanning <pj...@users.noreply.github.com>
AuthorDate: Mon Mar 6 21:13:58 2023 +0100
remove-akka-release-train (#36)
---
.github/release-drafter.yml | 111 -------------------------
.github/workflows/release-drafter.yml | 17 ----
RELEASING.md | 28 -------
docs/release-train-issue-template.md | 79 ------------------
docs/src/main/paradox/kudu.md | 2 +-
docs/src/main/paradox/other-docs/versioning.md | 2 +-
docs/src/main/paradox/release-notes/index.md | 2 +-
scripts/create-release-issue.sh | 12 ---
8 files changed, 3 insertions(+), 250 deletions(-)
diff --git a/.github/release-drafter.yml b/.github/release-drafter.yml
deleted file mode 100644
index 0a9a4bb4..00000000
--- a/.github/release-drafter.yml
+++ /dev/null
@@ -1,111 +0,0 @@
-# Config for https://github.com/toolmantim/release-drafter
-name-template: 'Apache Pekko Connectors $NEXT_PATCH_VERSION'
-tag-template: 'v$NEXT_PATCH_VERSION'
-categories:
- - title: ':toolbox: Infrastructure'
- label: 'alpakka-itself'
- - title: 'AMQP'
- label: 'p:amqp'
- - title: 'Apache Solr'
- label: 'p:solr'
- - title: 'Apache HDFS'
- label: 'p:hdfs'
- - title: 'Apache Kudu'
- label: 'p:kudu'
- - title: 'AvroParquet'
- label: 'p:avroparquet'
- - title: 'AWS EventBridge'
- label: 'p:aws-event-bridge'
- - title: 'AWS Lambda'
- label: 'p:aws-lambda'
- - title: 'AWS Kinesis'
- label: 'p:kinesis'
- - title: 'AWS S3'
- label: 'p:aws-s3'
- - title: 'AWS SNS'
- label: 'p:aws-sns'
- - title: 'AWS SQS'
- label: 'p:aws-sqs'
- - title: 'Azure Storage Queue'
- label: 'p:azure-storage-queue'
- - title: 'Cassandra'
- label: 'p:cassandra'
- - title: 'Comma-separated Values (CSV)'
- label: 'p:csv'
- - title: 'Couchbase'
- label: 'p:couchbase'
- - title: 'Dynamo DB'
- label: 'p:dynamodb'
- - title: 'Elasticsearch'
- label: 'p:elasticsearch'
- - title: 'File'
- label: 'p:file'
- - title: 'FTP'
- label: 'p:ftp'
- - title: 'Geode'
- label: 'p:geode'
- - title: 'Google Cloud BigQuery'
- label: 'p:google-cloud-bigquery'
- - title: 'Google Cloud BigQuery Storage'
- label: 'p:google-cloud-bigquery-storage'
- - title: 'Google Cloud Pub/Sub'
- label: 'p:google-cloud-pub-sub'
- - title: 'Google Cloud Pub/Sub gRPC'
- label: 'p:google-cloud-pub-sub-grpc'
- - title: 'Google Cloud Storage'
- label: 'p:google-cloud-storage'
- - title: 'Google FCM (Firebase)'
- label: 'p:google-fcm'
- - title: 'HBase'
- label: 'p:hbase'
- - title: 'Huawei Push Kit'
- label: 'p:huawei-push-kit'
- - title: 'InfluxDB'
- label: 'p:influxdb'
- - title: 'IronMQ'
- label: 'p:ironmq'
- - title: 'JDBC'
- label: 'p:jdbc'
- - title: 'JMS'
- label: 'p:jms'
- - title: 'Json streaming'
- label: 'p:json-streaming'
- - title: 'MongoDB'
- label: 'p:mongodb'
- - title: 'MQTT'
- label: 'p:mqtt'
- - title: 'MQTT Streaming'
- label: 'p:mqtt-streaming'
- - title: 'OrientDB'
- label: 'p:orientdb'
- - title: 'Pravega'
- label: 'p:pravega'
- - title: 'Reference'
- label: 'p:reference'
- - title: 'Server-sent events (SSE)'
- label: 'p:sse'
- - title: 'Simple Codecs'
- label: 'p:recordio'
- - title: 'Slick'
- label: 'p:slick'
- - title: 'Spring Web'
- label: 'p:spring-web'
- - title: 'Text'
- label: 'p:text'
- - title: 'UDP'
- label: 'p:udp'
- - title: 'Unix Domain Socket'
- label: 'p:unix-domain-socket'
- - title: 'XML'
- label: 'p:xml'
-
-change-template: '- $TITLE [#$NUMBER](https://github.com/apache/incubator-pekko-connectors/issues/$NUMBER) by [@$AUTHOR](https://github.com/$AUTHOR)'
-template: |
- # :mega: Apache Pekko Connectors $NEXT_PATCH_VERSION released!
-
- ## Changes
-
- $CHANGES
-
- ## :bow: Credits
- Special thanks to the following contributors who helped with this release: $CONTRIBUTORS
diff --git a/.github/workflows/release-drafter.yml b/.github/workflows/release-drafter.yml
deleted file mode 100644
index 9b2de164..00000000
--- a/.github/workflows/release-drafter.yml
+++ /dev/null
@@ -1,17 +0,0 @@
-name: Release Drafter
-
-on:
- push:
- branches:
- - master
- - main
- - release-*
-
-jobs:
- update_release_draft:
- runs-on: ubuntu-18.04
- steps:
- # Drafts your next Release notes as Pull Requests are merged
- - uses: release-drafter/release-drafter@v5
- env:
- GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
diff --git a/RELEASING.md b/RELEASING.md
deleted file mode 100644
index 5bf916e8..00000000
--- a/RELEASING.md
+++ /dev/null
@@ -1,28 +0,0 @@
-## Releasing
-
-Use this command to create a release issue of [Pekko Connectors Release Train Issue Template](docs/release-train-issue-template.md) and follow the steps.
-
-```bash
-~/pekko-connectors> scripts/create-release-issue.sh `version-to-be-released`
-```
-
-### Releasing only updated docs
-
-It is possible to release a revised documentation to the already existing release.
-
-1. Create a new branch from a release tag. If a revised documentation is for the `v0.3` release, then the name of the new branch should be `docs/v0.3`.
-1. Add and commit `version.sbt` file that pins the version to the one, that is being revised. Also set `isSnapshot` to `false` for the stable documentation links. For example:
- ```scala
- ThisBuild / version := "1.0.4"
- ThisBuild / isSnapshot := false
- ```
-1. Make all of the required changes to the documentation.
-1. Build documentation locally with `CI` settings:
- ```sh
- env CI=true sbt docs/previewSite
- ```
-1. If the generated documentation looks good, send it to Gustav:
- ```sh
- env CI=true sbt docs/publishRsync
- ```
-1. Do not forget to push the new branch back to GitHub.
diff --git a/docs/release-train-issue-template.md b/docs/release-train-issue-template.md
deleted file mode 100644
index 3552fca1..00000000
--- a/docs/release-train-issue-template.md
+++ /dev/null
@@ -1,79 +0,0 @@
-# Release Alpakka $VERSION$
-
-<!--
-# Release Train Issue Template for Alpakka
-
-(Liberally copied and adopted from Scala itself https://github.com/scala/scala-dev/blob/b11cd2e4a4431de7867db6b39362bea8fa6650e7/notes/releases/template.md)
-
-For every Alpakka release, make a copy of this file named after the release, and expand the variables.
-Ideally replacing variables could become a script you can run on your local machine.
-
-Variables to be expanded in this template:
-- $VERSION$=???
-- $BINARY_VERSION$=???
-
-Key links:
- - apache/incubator-pekko-connectors milestone: https://github.com/apache/incubator-pekko-connectors/milestone/?
--->
-### ~ 1 week before the release
-
-- [ ] Check that any new `deprecated` annotations use the correct version name
-- [ ] Check that open PRs and issues assigned to the milestone are reasonable
-- [ ] Decide on planned release date
-- [ ] Create a new milestone for the [next version](https://github.com/apache/incubator-pekko-connectors/milestones)
-- [ ] Check [closed issues without a milestone](https://github.com/apache/incubator-pekko-connectors/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aclosed%20no%3Amilestone) and either assign them the 'upcoming' release milestone or `invalid/not release-bound`
-
-### 1 day before the release
-
-- [ ] Make sure all important / big PRs have been merged by now
-
-### Preparing release notes in the documentation / announcement
-
-- [ ] Check readiness levels in `/project/project-info.conf`, and put in the release date for any new modules
-- [ ] For non-patch releases: Create a news item draft PR on [akka.github.com](https://github.com/akka/akka.io), using the milestone
-- [ ] Move all [unclosed issues](https://github.com/apache/incubator-pekko-connectors/issues?q=is%3Aopen+is%3Aissue+milestone%3A$VERSION$) for this milestone to the next milestone
-- [ ] Close the [$VERSION$ milestone](https://github.com/apache/incubator-pekko-connectors/milestones?direction=asc&sort=due_date)
-
-### Cutting the release
-
-- [ ] Wait until the [build finished](https://github.com/apache/incubator-pekko-connectors/actions) after merging the release notes
-- [ ] [Fix up the draft release](https://github.com/apache/incubator-pekko-connectors/releases) with the next tag version `v$VERSION$`, title and release description linking to announcement and milestone
-- [ ] Check that the CI release build has executed successfully (GitHub actions will start a [CI publish build](https://github.com/apache/incubator-pekko-connectors/actions/workflows/publish.yml) for the new tag and publish artifacts to Sonatype and documentation to Gustav)
-
-### Check availability
-
-- [ ] Check [API](https://doc.akka.io/api/alpakka/$VERSION$/) documentation
-- [ ] Check [reference](https://doc.akka.io/docs/alpakka/$VERSION$/) documentation
-- [ ] Check the release on [Maven central](https://repo1.maven.org/maven2/org/pekko/akka-stream-alpakka-xml_2.13/$VERSION$/)
-
-### When everything is on maven central
- - [ ] Log into `gustav.akka.io` as `akkarepo`
- - [ ] update the `current` links on `repo.akka.io` to point to the latest version with
- ```
- ln -nsf $VERSION$ www/docs/alpakka/current
- ln -nsf $VERSION$ www/api/alpakka/current
- ln -nsf $VERSION$ www/docs/alpakka/$BINARY_VERSION$
- ln -nsf $VERSION$ www/api/alpakka/$BINARY_VERSION$
- ```
- - [ ] check changes and commit the new version to the local git repository
- ```
- cd ~/www
- git add docs/alpakka/$BINARY_VERSION$ docs/alpakka/current docs/alpakka/$VERSION$
- git add api/alpakka/$BINARY_VERSION$ api/alpakka/current api/alpakka/$VERSION$
- git commit -m "Alpakka $VERSION$"
- ```
-
-### Announcements
-
-- [ ] For non-patch releases: Merge draft news item for [akka.io](https://github.com/akka/akka.io)
-- [ ] Send a release notification to [Lightbend discuss](https://discuss.akka.io)
-- [ ] Tweet using the akkateam account (or ask someone to) about the new release
-- [ ] Announce internally
-
-### Afterwards
-
-- [ ] If Couchbase has relevant changes, create/update PR in [Apache Pekko Persistence Couchbase](https://github.com/akka/akka-persistence-couchbase/) to upgrade to $VERSION$
-- [ ] If Cassandra has relevant changes, create/update PR in [Apache Pekko Persistence Cassandra](https://github.com/akka/akka-persistence-cassandra/) to upgrade to $VERSION$
-- [ ] Update version for [Lightbend Supported Modules](https://developer.lightbend.com/docs/lightbend-platform/introduction/getting-help/build-dependencies.html#_alpakka) in [private project](https://github.com/lightbend/lightbend-platform-docs/blob/master/docs/modules/getting-help/examples/build.sbt)
-- [ ] Create an issue or PR to upgrade projects in [Alpakka Samples](https://github.com/apache/incubator-pekko-connectors-samples)
-- Close this issue
diff --git a/docs/src/main/paradox/kudu.md b/docs/src/main/paradox/kudu.md
index 48cc238e..2e066d24 100644
--- a/docs/src/main/paradox/kudu.md
+++ b/docs/src/main/paradox/kudu.md
@@ -31,7 +31,7 @@ To connect to Kudu you need:
1. Describe the Kudu @javadoc[Schema](org.apache.kudu.Schema)
1. Define a converter function to map your data type to a @javadoc[PartialRow](org.apache.kudu.client.PartialRow)
1. Specify Kudu @javadoc[CreateTableOptions](org.apache.kudu.client.CreateTableOptions)
-1. Set up Apache Pekko Connectors's @scaladoc[KuduTableSettings](akka.stream.alpakka.kudu.KuduTableSettings)
+1. Set up Apache Pekko Connectors' @scaladoc[KuduTableSettings](akka.stream.alpakka.kudu.KuduTableSettings)
Scala
: @@snip [snip](/kudu/src/test/scala/docs/scaladsl/KuduTableSpec.scala) { #configure }
diff --git a/docs/src/main/paradox/other-docs/versioning.md b/docs/src/main/paradox/other-docs/versioning.md
index fdbb9c12..70cc470c 100644
--- a/docs/src/main/paradox/other-docs/versioning.md
+++ b/docs/src/main/paradox/other-docs/versioning.md
@@ -37,7 +37,7 @@ See Apache Pekko's @extref:[Downstream upgrade strategy](pekko:project/downstrea
Users are recommended to upgrade to the latest Apache Pekko version later than the one required by Apache Pekko Connectors at their convenience.
-Apache Pekko Connectors's nightly tests verify compatibility with the upcoming Apache Pekko's 1.0 release.
+Apache Pekko Connectors' nightly tests verify compatibility with the upcoming Apache Pekko's 1.0 release.
@@@
diff --git a/docs/src/main/paradox/release-notes/index.md b/docs/src/main/paradox/release-notes/index.md
index 3f53d2e0..fc28616c 100644
--- a/docs/src/main/paradox/release-notes/index.md
+++ b/docs/src/main/paradox/release-notes/index.md
@@ -1,6 +1,6 @@
# Release Notes
-To understand the forces on version numbers, read about @ref:[Apache Pekko Connectors's versioning scheme](../other-docs/versioning.md).
+To understand the forces on version numbers, read about @ref:[Apache Pekko Connectors' versioning scheme](../other-docs/versioning.md).
@@toc { depth=2 }
diff --git a/scripts/create-release-issue.sh b/scripts/create-release-issue.sh
deleted file mode 100755
index aba20ca6..00000000
--- a/scripts/create-release-issue.sh
+++ /dev/null
@@ -1,12 +0,0 @@
-#!/bin/bash
-
-VERSION=$1
-BINARY_VERSION=$2
-if [ -z $BINARY_VERSION ]
-then
- echo specify the version name to be released and its minor version, eg. 2.0.0 2.0
-else
- sed -e 's/\$VERSION\$/'$VERSION'/g' docs/release-train-issue-template.md > /tmp/release-$VERSION.tmp
- sed -e 's/\$BINARY_VERSION\$/'$BINARY_VERSION'/g' /tmp/release-$VERSION.tmp > /tmp/release-$VERSION.md
- echo Created $(gh issue create --title "Release Alpakka $VERSION" --body-file /tmp/release-$VERSION.md --milestone $VERSION --web)
-fi
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pekko.apache.org
For additional commands, e-mail: commits-help@pekko.apache.org