, the doc for 2.10.0 was a copy saved from the next (master)
> > doc at that milestone.
> > > ________
> > > 发件人: Asaf Mesika
> > > 发送时间: 2022年7月24日 21:00
> > > 收件人: dev@pulsar.apache.org
> > > 主题: Re: [Discuss] PIP-
ttps://github.com/apache/pulsar/tree/master/site2/website/versioned_docs.
> >
> > For example, the doc for 2.10.0 was a copy saved from the next (master)
> doc at that milestone.
> >
> > 发件人: Asaf Mesika
> > 发送时间: 2022年7月24日 21
at milestone.
> >> ________________
> >> 发件人: Asaf Mesika
> >> 发送时间: 2022年7月24日 21:00
> >> 收件人: dev@pulsar.apache.org
> >> 主题: Re: [Discuss] PIP-190: Simplify Pulsar documentation release and
> maintenance strategy
> >>
>
cs.
>>
>> For example, the doc for 2.10.0 was a copy saved from the next (master) doc
>> at that milestone.
>>
>> 发件人: Asaf Mesika
>> 发送时间: 2022年7月24日 21:00
>> 收件人: dev@pulsar.apache.org
>> 主题: Re: [Discuss] PIP-190
21:00
> 收件人: dev@pulsar.apache.org
> 主题: Re: [Discuss] PIP-190: Simplify Pulsar documentation release and
> maintenance strategy
>
> If I understand correctly, using tags, you can automatically create the
> docs for the next minor version?
> So for older minor versions, wher
Mesika
发送时间: 2022年7月24日 21:00
收件人: dev@pulsar.apache.org
主题: Re: [Discuss] PIP-190: Simplify Pulsar documentation release and
maintenance strategy
If I understand correctly, using tags, you can automatically create the
docs for the next minor version?
So for older minor versions, where those
If I understand correctly, using tags, you can automatically create the
docs for the next minor version?
So for older minor versions, where those files will be at? using tags from
git?
On Sat, Jul 23, 2022 at 7:04 AM Ma Jun wrote:
> Hi, Pulsar community,
>
> Happy weekend!
>
> I'd like to open a
Hi, Pulsar community,
Happy weekend!
I'd like to open a discussion about PIP-190: Simplify Pulsar documentation
release and maintenance strategy.
Proposal link: https://github.com/apache/pulsar/issues/16637.
-
##
