Thank you, Mauricio,

I'm going to apply this patch on Monday. I will be traveling with limited
access to the Internet.

I'll also add more explanation on why we should update these tags to the
wiki.

вт, 11 июн. 2019 г. в 20:57, Mauricio Stekl <mauri...@gridgain.com>:

> Hi Dmitriy,
> Yes, that would be enough to set the URL for latest docs.
>
> Additionally I usually do some SEO updates to new/old .html files, like
> adding NOINDEX metatag to older version; add canonical URL to latest docs;
> and add GA code.
>
> I am attaching a svn patch which includes all these updates, including the
> .htaccess one.
>
>
> Thanks.
> Mauricio Stekl
>
>
>
>
>
> On Tue, Jun 11, 2019 at 1:38 PM Dmitriy Pavlov <dpav...@apache.org> wrote:
>
>> Ok, Denis, thank you.
>>
>> Garrett, could you please advice me on how to do a copy of 2.7.0 docs to
>> 2.7.5? I have an account on the readme.io, so I would like to do it and
>> describe in the Release process
>> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
>>
>> Mauricio, is my understanding correct?
>> in the htaccess I can replace
>>
>> RewriteRule ^releases/latest/(.*)$ /releases/2.7.0/$1 [L]
>>
>> to
>>
>> RewriteRule ^releases/latest/(.*)$ /releases/2.7.5/$1 [L]
>>
>> and that's it?
>>
>> Sincerely
>> Dmitriy Pavlov
>>
>> вт, 11 июн. 2019 г. в 19:26, Denis Magda <dma...@apache.org>:
>>
>> > Igniters,
>> >
>> > We have to create version 2.7.5 for readme.io even if the changes are
>> > minimal. That's a general practice. Copying Garrett and Artem who can
>> > facilitate on the documentation end.
>> >
>> > Also, feel free to reach out Mauricio (copied) who can help to run the
>> > scripts that will make JavaDocs 2.7.5 latest for Ignite website.
>> >
>> > -
>> > Denis
>> >
>> >
>> > On Tue, Jun 11, 2019 at 6:00 AM Dmitriy Pavlov <dpav...@apache.org>
>> wrote:
>> >
>> > > Sorry for the second email. I want to clarify: I've already uploaded
>> > > Javadoc,scaladoc,c++ docs (generated). Question is related only to
>> > > readme.io.
>> > > We have links named as 2.7 there, so both 2.7.5 & 2.7.0 seems to be
>> > > applicable.
>> > >
>> > > There were no changes in the public API/parameters.
>> > >
>> > > вт, 11 июн. 2019 г. в 15:44, Nikolay Izhikov <nizhi...@apache.org>:
>> > >
>> > > > Hello, Dmitriy.
>> > > >
>> > > > I think we should write down diff between 2.7.0 and 2.7.5 on some
>> page
>> > in
>> > > > 2.7 documentation.
>> > > > Also, we should make this page very noticable.
>> > > >
>> > > > В Вт, 11/06/2019 в 15:22 +0300, Dmitriy Pavlov пишет:
>> > > > > Hi Igniters, PMCs,
>> > > > >
>> > > > > could you please advice me about step
>> > > > >
>> > > > >    1. Release all the documentation (Java, .NET, C++, etc.) on
>> > > > >    apacheignite.readme.io.
>> > > > >
>> > > > > from the release process.
>> > > > >
>> > > > > Do we have some documentation to publish for 2.7.5? Since it is
>> minor
>> > > > > release I propose to keep documentation for 2.7.0.
>> > > > >
>> > > > > Sincerely,
>> > > > > Dmitriy Pavlov
>> > > > >
>> > > > > пн, 10 июн. 2019 г. в 14:30, Dmitriy Pavlov <dpav...@apache.org>:
>> > > > >
>> > > > > > The vote for a new release candidate is closed, now
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > Vote result: Vote passes with 9 votes +1 (4 binding +1 votes),
>> no 0
>> > > > and no
>> > > > > > -1.
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > +1 votes:
>> > > > > >
>> > > > > > - Ilya Kasnacheev
>> > > > > >
>> > > > > > - Nikolay Izhikov (binding)
>> > > > > >
>> > > > > > - Denis Magda (binding)
>> > > > > >
>> > > > > > - Andrey Gura (binding)
>> > > > > >
>> > > > > > - Alexey Goncharuk (binding)
>> > > > > >
>> > > > > > - Igor Sapego
>> > > > > >
>> > > > > > - Ivan Pavlukhin
>> > > > > >
>> > > > > > - Yuriy Babak
>> > > > > >
>> > > > > > - Vyacheslav Daradur
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > Vote thread
>> > > > > >
>> > > >
>> > >
>> >
>> https://lists.apache.org/thread.html/35cbc2d4c5b769155dc8aec15edd808a25c5cf48a5e12637528e931d@%3Cdev.ignite.apache.org%3E
>> > > > > >
>> > > > > >
>> > > >
>> > >
>> >
>>
>

Reply via email to