I'm glad the new approach is working for you! There are a number of placeholders for new evaluators which were added before we moved the pages out of Confluence, I think inserted for 6.6 (or maybe 6.5?) - pow, mod, ceil, floor, sin, asin, sinh, etc. - that it looks like you missed removing last night. I'll remove them now so I can move forward getting the artifacts up, but just wanted you to know.
On Wed, Jun 7, 2017 at 11:12 AM, Joel Bernstein <[email protected]> wrote: > True. But hopefully this is just a temporary problem. Going forward I think > it's best to commit the docs along with the ticket. > > By the way I'm really enjoying the new documentation format. Thanks for all > your work on this! > > Joel Bernstein > http://joelsolr.blogspot.com/ > > On Wed, Jun 7, 2017 at 10:48 AM, Cassandra Targett <[email protected]> > wrote: >> >> OK, I get your point, but note you'll have to use the 6.6 CHANGES list >> to double-check what might have been missed in 6.6 docs when you get >> the chance to document what was added in 6.7. >> >> I'll leave it up to you, but one of the benefits of this approach is >> we can leave comments in the docs so we don't forget things we want to >> add in the future. I intend to use this extensively in the future for >> all kinds of things - you can find lots of comments in various places >> already - so it's not like the streaming expression pages will be >> unique in this regard. >> >> On Wed, Jun 7, 2017 at 9:39 AM, Joel Bernstein <[email protected]> wrote: >> > I think we can move away from having the TODO's in the pages. I've been >> > using the CHANGES.txt as guide of what's left to document. >> > >> > Joel Bernstein >> > http://joelsolr.blogspot.com/ >> > >> > On Wed, Jun 7, 2017 at 10:27 AM, Cassandra Targett >> > <[email protected]> >> > wrote: >> >> >> >> Hey Joel - >> >> >> >> I noticed that you removed those remaining streaming expression TODOs >> >> from master and branch_6x. I think we should revert those commits in >> >> those branches, because we'll want to see if we can fill them in for >> >> 7.0 or maybe even 6.7 if there's time. We only need branch_6_6 to be >> >> "right" for the 6.6 Ref Guide, since that's the branch it will be >> >> built from. The TODOs in other branches can wait until a later time if >> >> necessary. >> >> >> >> WDYT? I'm happy to do the revert, just want to check I understand what >> >> you were trying to do. >> >> >> >> Cassandra >> >> >> >> On Tue, Jun 6, 2017 at 2:09 PM, Cassandra Targett >> >> <[email protected]> >> >> wrote: >> >> > Ah, that's perfect Joel, thanks so much. Let me know if I can help at >> >> > all. >> >> > >> >> > On Tue, Jun 6, 2017 at 2:03 PM, Joel Bernstein <[email protected]> >> >> > wrote: >> >> >> I'll do the cherry-picks to 6_6 this evening. >> >> >> >> >> >> It looks like I won't be able to finish all the functions today. So >> >> >> I'll >> >> >> also pull the place holders for functions I don't get to. >> >> >> >> >> >> Joel Bernstein >> >> >> http://joelsolr.blogspot.com/ >> >> >> >> >> >> On Tue, Jun 6, 2017 at 2:47 PM, Cassandra Targett >> >> >> <[email protected]> >> >> >> wrote: >> >> >>> >> >> >>> Hey Joel, >> >> >>> >> >> >>> Have you done any changes in those commits yesterday or earlier for >> >> >>> 6.7 streaming expression changes? All of those changes need to go >> >> >>> into >> >> >>> branch_6_6 in order to make it into the 6.6 Guide. >> >> >>> >> >> >>> I can simply checkout the files from branch_6x to branch_6_6 if I >> >> >>> don't have to worry about 6.7-specific changes being already mixed >> >> >>> in. >> >> >>> Otherwise, I'll need to cherry-pick each commit. >> >> >>> >> >> >>> Thanks, >> >> >>> Cassandra >> >> >>> >> >> >>> On Tue, Jun 6, 2017 at 11:25 AM, Joel Bernstein >> >> >>> <[email protected]> >> >> >>> wrote: >> >> >>> > Hi Cassandra, >> >> >>> > >> >> >>> > I will attempt to finish the streaming expression changes for 6.6 >> >> >>> > today. >> >> >>> > I >> >> >>> > backported the first set of changes to branch_6x yesterday. >> >> >>> > >> >> >>> > Joel Bernstein >> >> >>> > http://joelsolr.blogspot.com/ >> >> >>> > >> >> >>> > On Mon, Jun 5, 2017 at 10:28 AM, Cassandra Targett >> >> >>> > <[email protected]> >> >> >>> > wrote: >> >> >>> >> >> >> >>> >> I'd like to start the VOTE process for the Solr 6.6 Ref Guide in >> >> >>> >> the >> >> >>> >> next couple of days. This will be our first release with the new >> >> >>> >> publication process. >> >> >>> >> >> >> >>> >> There isn't a TODO list for what needs to be doc'd anymore, but >> >> >>> >> I >> >> >>> >> did >> >> >>> >> review what was in CHANGES.txt and was able to do many items on >> >> >>> >> my >> >> >>> >> own, and contacted a few folks privately for help, so most of it >> >> >>> >> is >> >> >>> >> done. There are a couple things still remaining: >> >> >>> >> >> >> >>> >> * SOLR-10521 (Mikhail) -- does this need to be documented >> >> >>> >> anywhere? >> >> >>> >> Where? What should it say? >> >> >>> >> * Lots of streaming expressions added in 6.6 still have TODOs - >> >> >>> >> I >> >> >>> >> know >> >> >>> >> Joel is working on these. >> >> >>> >> >> >> >>> >> From a vote perspective it will work exactly the same, but for >> >> >>> >> the >> >> >>> >> first time we'll also have a 6.6-specific HTML version online >> >> >>> >> for >> >> >>> >> review at the same time. >> >> >>> >> >> >> >>> >> We have daily builds set up so you can look at the artifacts at >> >> >>> >> any >> >> >>> >> time: https://builds.apache.org/job/Solr-reference-guide-6.6/. >> >> >>> >> >> >> >>> >> Also, if you're struggling with working with the new docs, >> >> >>> >> please >> >> >>> >> feel >> >> >>> >> free to reach out to me by email or on IRC and I'll try to help >> >> >>> >> however I can. >> >> >>> >> >> >> >>> >> Cassandra >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> --------------------------------------------------------------------- >> >> >>> >> To unsubscribe, e-mail: [email protected] >> >> >>> >> For additional commands, e-mail: [email protected] >> >> >>> >> >> >> >>> > >> >> >>> >> >> >>> >> >> >>> --------------------------------------------------------------------- >> >> >>> To unsubscribe, e-mail: [email protected] >> >> >>> For additional commands, e-mail: [email protected] >> >> >>> >> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [email protected] >> >> For additional commands, e-mail: [email protected] >> >> >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
