The branches are reopened. I still need to push the SNAPSHOT docs for 3.5.2 another time as I ran into a problem with generating the javadocs again there, but that should happen today, and it shouldn't stop any work on 3.5-dev.
-----Ursprüngliche Nachricht----- Von: Florian Hockmann <[email protected]> Gesendet: Freitag, 16. Juli 2021 16:11 An: [email protected] Betreff: AW: [DISCUSS] code freeze 3.4.12/3.5.1 I just published the updated docs: reference, developer and upgrade for 3.5.1-SNAPSHOT. -----Ursprüngliche Nachricht----- Von: Florian Hockmann <[email protected]> Gesendet: Donnerstag, 15. Juli 2021 17:20 An: [email protected] Betreff: AW: [DISCUSS] code freeze 3.4.12/3.5.1 Thanks for the heads up and good to know that the deployment worked for gremlint without any new issues coming up. I will probably republish the changed docs tomorrow and then continue with the release process at the start of next week. -----Ursprüngliche Nachricht----- Von: Stephen Mallette <[email protected]> Gesendet: Donnerstag, 15. Juli 2021 16:50 An: [email protected] Betreff: Re: [DISCUSS] code freeze 3.4.12/3.5.1 Florian, you probably noticed the other thread where the gremlint release candidate worked just fine. I updated the release docs on 3.5-dev to include the step to also release gremlint for 3.5.1. It is basically the same command as the one for gremlin-javascript so easy stuff. While you're free to follow the dev docs in /current for the release, note that there is this little addition to that process that won't be present in .current as you're going through the steps. On Thu, Jul 15, 2021 at 9:57 AM Stephen Mallette <[email protected]> wrote: > I just pushed a change for upgrade docs on 3.5.1. If you feel like > republishing toward the end of code freeze you can, but it's not > necessary in this case i don't think. Note that you can selectively > update documentation, but the task is a bit of a manual one: > > 1. bin/process-docs.sh --dryRun > 2. in target/postprocess-asciidoc manually delete the folder(s) you > want to regenerate content for 3. bin/process-docs.sh (this will only > generate docs for the stuff you > deleted) > 4. you can then do an: svn checkout > https://svn.apache.org/repos/asf/tinkerpop/site/docs/<version>/<dir > containing the file you want to update> 5. copy the newly generated > file in target/docs over the old one in the svn directory 6. svn > commit your change > > In this case, it's even easier because you probably just care about > upgrade docs really. since upgrade docs are static you can skip steps > 2 and > 3 as the doc should already be in good order as there are no code > examples to pass through the script engine. > > > > > On Wed, Jul 14, 2021 at 6:51 AM Florian Hockmann > <[email protected]> > wrote: > >> I’ve published SNAPSHOT artifacts and docs for review: >> >> https://tinkerpop.apache.org/docs/3.4.12-SNAPSHOT/ >> https://tinkerpop.apache.org/docs/3.5.1-SNAPSHOT/ >> >> -----Ursprüngliche Nachricht----- >> Von: Stephen Mallette <[email protected]> >> Gesendet: Freitag, 9. Juli 2021 16:23 >> An: [email protected] >> Betreff: Re: [DISCUSS] code freeze 3.4.12/3.5.1 >> >> > Stephen already mentioned in the discussion thread on 3.5.1 that >> > he >> intends to merge a PR in for 3.5.1 around gremlin-language that he >> considers to be low risk. >> >> i think i will pull back on that. it's turning into more work than >> i'd expected. no need to expect further code changes from me. >> >> On Fri, Jul 9, 2021 at 4:01 AM Florian Hockmann >> <[email protected]> >> wrote: >> >> > Code freeze on 3.4-dev and 3.5-dev starts now. I don't see any open >> > issues in JIRA that are tagged for this release or open PRs that >> > need to be merged. >> > If you have anything that should be included in these releases, >> > then please respond to this thread. Stephen already mentioned in >> > the discussion thread on 3.5.1 that he intends to merge a PR in for >> > 3.5.1 around gremlin-language that he considers to be low risk. >> > >> > >> > >> > I will be publishing SNAPSHOT artifacts and documentation for >> > testing/review and will post back here when that is available. >> > >> > >> > >> > Please use this thread for any issues that come up during the code >> > freeze time frame. Thanks. >> > >> > >> >>
