I've created a draft pages on apache.readme.io and will continue my work there during next 2 weeks. Should I create any tickets for that? Or could miss that step?
Will notify in this thread than the work will be done! чт, 20 февр. 2020 г. в 12:16, Alexey Zinoviev <zaleslaw....@gmail.com>: > Yes, there are a lot of changes in ML from 2.7, I'm going to prepare new > documentation and create documentation related tickets for the ML > component. > After some consultation and review from Artem side I'll add new > documentation on readme.io. > > > > чт, 20 февр. 2020 г. в 02:34, Denis Magda <dma...@apache.org>: > >> Artem, >> >> Thanks for stepping in and preparing the list of top priority >> documentation tasks! How about labeling those tickets somehow and creating >> a filter similar to this one [1] but for "Required & Unresolved >> Documentation Tasks"? I would simply add this as a new section to the >> Ignite 2.8 release wiki page for ease of tracking and start working with >> the guys contributed improvements directly. Will see the names of the >> authors who need to be involved ;) >> >> *Alexey Zinoviev*, there are many ML related changes coming in the >> release. Could you check existing ML docs and suggest any changes? >> >> [1] >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Unresolveddocumentationtasks >> >> - >> Denis >> >> >> On Wed, Feb 19, 2020 at 11:14 AM Artem Budnikov < >> a.budnikov.ign...@gmail.com> wrote: >> >>> Maxim, >>> >>> One note from my side, I think we can move disk page compression [1] >>> > to the 2-nd priority, but definitely must document WAL page >>> > compression first [2] >>> >>> >>> OK, good to know. >>> >>> On Wed, Feb 19, 2020 at 6:48 PM Maxim Muzafarov <mmu...@apache.org> >>> wrote: >>> >>> > Artem, >>> > >>> > >>> > Thank you for starting this thread. >>> > One note from my side, I think we can move disk page compression [1] >>> > to the 2-nd priority, but definitely must document WAL page >>> > compression first [2] >>> > >>> > >>> > The list of important tasks [3]. >>> > The list of documentation tasks [4]. >>> > >>> > [1] https://issues.apache.org/jira/browse/IGNITE-10330 >>> > [2] https://issues.apache.org/jira/browse/IGNITE-11336 >>> > [3] >>> > >>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Themostimportantreleasetasks >>> > [4] >>> > >>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Unresolveddocumentationtasks >>> > >>> > On Wed, 19 Feb 2020 at 18:15, Artem Budnikov >>> > <a.budnikov.ign...@gmail.com> wrote: >>> > > >>> > > Hi everyone, >>> > > >>> > > As the release of Ignite 2.8 is getting closer, let's discuss which >>> > features should be documented. I created a list of features based on >>> the >>> > release notes and the documentation tickets in jira (see below). Much >>> more >>> > has been added, but these seemed to have first priority. It's not to >>> say >>> > that other features are not important, but given the limited resources >>> a >>> > list of high-priority task would help to schedule the time of those who >>> > will help with the docs. >>> > > >>> > > Here is the list of features: >>> > > >>> > > Disk page compression >>> > > Metrics and System Views documentation >>> > > Default Ignite work dir location >>> > > Baseline auto-adjust feature >>> > > Cluster (de)activation events documentation >>> > > Remove SqlQuery documentation >>> > > Partition awareness for thin clients >>> > > Transactions support in thin clients >>> > > KILL QUERY command >>> > > Move rebalance configuration properties to the IgniteConfiguration >>> level >>> > > Renamed IGNITE schema to SYS >>> > > JDBC: Support for query cancellation >>> > > JDBC: Support for query timeout >>> > > suspend/resume for pessimistic transactions >>> > > >>> > > Now, two really big questions here: >>> > > >>> > > If you want to add anything else to the documentation, please let us >>> > know in this thread. >>> > > If you are the author of any of the features listed above, please >>> share >>> > the details on the feature. You can do it by creating a documentation >>> > ticket. If you want to contribute a page or section to the existing >>> docs, >>> > you can write directly on apacheignite.readme.io (send me a note if >>> you >>> > don't have an account there). Any help is greatly appreciated. >>> > > >>> > > -Artem >>> > > >>> > > >>> > >>> >>
