Hi all,
The PR has merged, and the https://github.com/apache/pulsar/wiki link has
been updated.
If you have any good ideas to improve the release process and release
validation documents.
You can push a PR directly.
Best,
Penghui
On Fri, Aug 19, 2022 at 2:18 PM PengHui Li wrote:
> The PR to
The PR to move the release-related documentation to the codebase.
https://github.com/apache/pulsar/pull/17176
After the PR gets merged, I will update the
https://github.com/apache/pulsar/wiki
to link to the doc in the codebase.
Thanks,
Penghui
On Tue, Aug 16, 2022 at 11:42 AM Haiting Jiang
Hi Dave,
> Just remove that command. Having two servers should be enough.
Agree, I have removed it.
> Release candidates should not be made by a bot. Releases must be verified
by building them from source. See
https://www.apache.org/legal/release-policy.html#owned-controlled-hardware
Thanks
> On Aug 15, 2022, at 3:30 AM, Haiting Jiang wrote:
>
>> Maybe we'd better move the release process doc and validation doc
>> to the codebase, not the wiki pages.
>
> IMO, we can move all contributor documentation and committers documentation
> to codebase.
> One example is that
> On Aug 15, 2022, at 4:09 AM, Yunze Xu wrote:
>
>> One example is that `pool.sks-keyservers.net` in [1] seems not available
> anymore, but I am not that confident enough to edit it directly.
>
> Yeah. It’s not available in my env as well. I made some changes recently,
> but I’m also not
> One example is that `pool.sks-keyservers.net` in [1] seems not available
anymore, but I am not that confident enough to edit it directly.
Yeah. It’s not available in my env as well. I made some changes recently,
but I’m also not sure about this point.
> I think we can consider using a BOT
> Maybe we'd better move the release process doc and validation doc
> to the codebase, not the wiki pages.
IMO, we can move all contributor documentation and committers documentation
to codebase.
One example is that `pool.sks-keyservers.net` in [1] seems not available
anymore, but I am not that
Sent from my iPhone
> On Aug 13, 2022, at 9:35 PM, Michael Marshall wrote:
>
> Thanks for raising this Yunze. The docker image was added to the VOTE
> threads as a convenience for voters/testers. I don't believe we
> established a formal requirement for it, which might explain why it is
>
Thanks for raising this Yunze. The docker image was added to the VOTE
threads as a convenience for voters/testers. I don't believe we
established a formal requirement for it, which might explain why it is
not in the wiki. It should, however, be listed as an optional step if
we want it to be one.
> The RM should ask a PMC member to help them add their KEY.
> Do not make the release docs part of versioned docs.
I agree.
Thanks,
Yunze
> 2022年8月12日 23:10，Dave Fisher 写道：
>
> Hi -
>
> One change that needs to be made is regarding the KEYS file.
>
> We should drop the use of
Hi -
One change that needs to be made is regarding the KEYS file.
We should drop the use of https://dist.apache.org/repos/dist/dev/pulsar/KEYS
instead we should carefully update
https://dist.apache.org/repos/dist/release/pulsar/KEYS
The two KEYS files are currently out of sync. The release
Hi Penghui & Yunze,
I ever wrote developer guides for TiDB[1] and Apache Kvrocks (Incubating),
including the release guide for the latter[2].
Just for your information, I'm preparing the proposal to bring a developer
guide page (series docs). Perhaps start in the next month.
Although, it cannot
Yeah, I agree. It’s better to move the release process to the codebase.
Regarding the automatic validation program, we can have that for some
common verifications like the GPG verification, which only requires a simple
command if you have downloaded the binary.
Thanks,
Yunze
> 2022年8月12日
Thanks for raising this question.
Maybe we'd better move the release process doc and validation doc
to the codebase, not the wiki pages.
- Only committers can update the wiki pages
- The changes without review
After moving to the pulsar codebase
- Everyone can contribute to the validation doc
> the 7th step is "Write release notes", should we execute this
> step later?
>From what I see, the release note can be postponed after the voting process.
And it's not part of the voting content and does not affect whether we
should cut a new release candidate.
> In addition, I found the
I'm going to push the Docker images for the 1st candidate soon.
Unfortunately, when I followed the 10th step "Publish Docker Images",
I found the tag doesn't have the "-rc" suffix.
```bash
cd docker
./build.sh
DOCKER_USER=bewaremypower DOCKER_PASSWORD=""
DOCKER_ORG=bewaremypower ./publish.sh
```
Hi all,
Recently I'm working on the release of 2.8.4 and it's near the vote of
the 1st candidate but I have some questions.
From the tutorial [1] we can see, the 8th step is "Run the vote".
However, the 7th step is "Write release notes", should we execute this
step later? I see the 16th step is
17 matches
Mail list logo
