> On Oct 24, 2019, at 1:16 PM, Enrico Olivelli <eolive...@gmail.com> wrote:
>
> Guangnin,
> The documents looks good.
> Just one clarification:
>
> When you say
>
> Source and binary files:
>
>
> You don't provide a link to the staging area but only to the github tag
>
> Is this expected?
> IMHO we should have a link to the svn repository
That’s not just an opinion, it really is a requirement. That way we can be sure
that what is voted to be released is what is actually released.
Also, Github tags are not immutable.
Here is the release distribution policy:
https://www.apache.org/dev/release-distribution.html
Regards,
Dave
>
>
> Hope that helps
> Enrico
>
> Il gio 24 ott 2019, 08:10 Sijie Guo <guosi...@gmail.com> ha scritto:
>
>> Guangning,
>>
>> Thank you very much for putting all these together!
>>
>> Overall looks good to me. A few comments:
>>
>> 1) Initially we started with version 0.0.1. I would suggest us bump the
>> version to 0.1.0 to follow semantic versioning (https://semver.org/) for
>> managing our release versions. So we can manage both major releases and
>> minor/bugfix releases.
>>
>> 2) I didn't see a process of updating pulsar website. I would suggest
>> adding a section in pulsar download (http://pulsar.apache.org/en/download/
>> )
>> page for hosting the releases for pulsar manager, and add a section of
>> updating download page as part of release process.
>>
>> 3) It would be good to add a documentation page about pulsar manager to
>> pulsar website under "Admin" section. So people know there is a pulsar
>> manager can be used for administering the Pulsar clusters.
>>
>> - Sijie
>>
>> On Wed, Oct 23, 2019 at 11:10 AM Guangning E <eguangn...@gmail.com> wrote:
>>
>>> Hi, all
>>>
>>> I have written some release and verification steps and recorded them as
>>> follows:
>>>
>>> release:
>>> https://gist.github.com/tuteng/86a75e3421794a6b2048d5d2aca2c790
>>>
>>> validation:
>>> https://gist.github.com/tuteng/41c5c6489e27864f9cd4c2ac13dc2925
>>>
>>> What do you think about this?
>>> If you have any comments on this, please reply to this email.
>>>
>>> Next, I will apply for pulsar-manager to enable a wiki page and record
>> the
>>> content on the wiki.
>>>
>>> Thanks,
>>> Guangning
>>>
>>> Guangning E <eguangn...@gmail.com> 于2019年9月25日周三 下午8:51写道：
>>>
>>>> Ok, I will draft a release document next.
>>>>
>>>>
>>>> Thanks,
>>>> Guangning
>>>>
>>>> Sijie Guo <guosi...@gmail.com> 于2019年9月25日周三 下午3:13写道：
>>>>
>>>>> Thank you guys!
>>>>>
>>>>> Guangning, do you want to draft a doc for the release process and
>> share
>>> it
>>>>> in the mailing list? So we can move the discussion forward.
>>>>>
>>>>> Thanks,
>>>>> Sijie
>>>>>
>>>>> On Tue, Sep 24, 2019 at 6:18 AM Nozomi Kurihara <
>> nkuri...@yahoo-corp.jp
>>>>
>>>>> wrote:
>>>>>
>>>>>> +1
>>>>>>
>>>>>> Sounds nice to create the first release as soon as possible.
>>>>>> As Guangning says, deciding the release process is necessary.
>>>>>>
>>>>>> Regards,
>>>>>> Nozomi
>>>>>> ________________________________
>>>>>> 差出人: Guangning E <eguangn...@gmail.com>
>>>>>> 送信日時: 2019年9月22日 11:18
>>>>>> 宛先: dev@pulsar.apache.org <dev@pulsar.apache.org>
>>>>>> 件名: Re: [DISCUSS] Create the first pulsar-manager apache release
>>>>>>
>>>>>> That sounds very good. Before that, we may need to write a release
>> and
>>>>>> verification process.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>> Guangning
>>>>>>
>>>>>> Sijie Guo <guosi...@gmail.com> 于2019年9月22日周日 上午9:35写道：
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> Since the pulsar-manager repo has been transferred to the ASF
>> under
>>>>>> Pulsar
>>>>>>> PMC, I would suggest us creating the first pulsar-manager apache
>>>>> release
>>>>>> as
>>>>>>> soon as possible. So that we can identify what to release and what
>>> are
>>>>>> the
>>>>>>> potential issues to fix to follow the Apache way.
>>>>>>>
>>>>>>> This is the email thread for discussing the first pulsar-manager
>>>>> release.
>>>>>>> Please chime in with your thoughts.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Sijie
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
