Skip to content

Commit 0fc6e50

Browse files
authored
1 parent 9a5a329 commit 0fc6e50

1 file changed

Lines changed: 0 additions & 61 deletions

File tree

README.md

Lines changed: 0 additions & 61 deletions
Original file line numberDiff line numberDiff line change
@@ -415,64 +415,3 @@ The first command will prompt you for a password. The second step requires you t
415415
license, and then accept it by typing "agree".
416416

417417
(Thanks to [this thread](https://github.com/bazelbuild/bazel/issues/4314) for these steps)
418-
419-
## Releasing
420-
421-
Begin by tagging the revision you're about to release, and push that tag to GitHub.
422-
423-
Before running a release build, you must ensure that the `--stamp` flag is used by
424-
the build. The easiest way to do this is:
425-
426-
```shell
427-
echo build --stamp >>.bazelrc.local
428-
```
429-
430-
### GitHub Release Page
431-
432-
* Draft a new (perhaps pre-release)
433-
* Make sure this release is for the tag you created earlier
434-
* Set the title to be whatever the release is.
435-
* Use `git log $PREV_RELEASE..$NEW_TAG --format=format:'* [`%h`](https://github.com/seleniumhq/selenium/commit/%H) - %s :: %an' | pbcopy`
436-
to generate the list of changes. Make sure you've set
437-
`$PREV_RELEASE` and `$NEW_TAG`!
438-
* The release notes are:
439-
```
440-
### Changelog
441-
442-
For each component's detailed changelog, please check:
443-
* [Ruby](https://github.com/SeleniumHQ/selenium/blob/trunk/rb/CHANGES)
444-
* [Python](https://github.com/SeleniumHQ/selenium/blob/trunk/py/CHANGES)
445-
* [JavaScript](https://github.com/SeleniumHQ/selenium/blob/trunk/javascript/node/selenium-webdriver/CHANGES.md)
446-
* [Java](https://github.com/SeleniumHQ/selenium/blob/trunk/java/CHANGELOG)
447-
* [DotNet](https://github.com/SeleniumHQ/selenium/blob/trunk/dotnet/CHANGELOG)
448-
* [IEDriverServer](https://github.com/SeleniumHQ/selenium/blob/trunk/cpp/iedriverserver/CHANGELOG)
449-
450-
### Commits in this release
451-
<details>
452-
<summary>Click to see all the commits included in this release</summary>
453-
454-
INSERT LIST OF CHANGES HERE!
455-
456-
</details>
457-
```
458-
* Now publish the release.
459-
460-
### Java
461-
462-
To release the Java components, make sure you have permission to push to the OSS Sonatype
463-
repo. You will need these credentials when pushing the maven release.
464-
465-
Make sure that the java `CHANGELOG` is up to date, then just run:
466-
467-
```shell
468-
./go release-java
469-
```
470-
471-
This will do two things:
472-
473-
1. Build the publishable artifacts and push them to a staging repo on the
474-
OSS Sonatype server.
475-
2. Create zip files to upload in `build/dist`
476-
477-
You will need to manually release the maven artifacts, and also upload
478-
the artifacts from `build/dist` to the GitHub release.

0 commit comments

Comments
 (0)