VOTE threads are out. If you are running bin/validate-distribution.sh to test out the artifacts, please make sure that you pull in the latest changes as I had to modify its operations in both branches:
* 3.5-dev had some gremlin-go issues * master had issues with the new web site content You should find running that script a bit faster now btw as the download sizes have reduced tremendously given our decision to remove the documentation from the packaging of Gremlin Server/Console. We went from 100mb files down to about 25mb. On Tue, Apr 5, 2022 at 11:32 AM Stephen Mallette <[email protected]> wrote: > hit some more snags along the way this morning. note that the 3.5.3 tag > will have a failing build associated to it in CI. it's not due to > anything wrong with the code itself. the problem is with the CI > configuration for gremlin-go. everything else should be passing just fine. > i'm doing another build now just to be sure. i don't think this should be a > reason to re-package the build (which i've already had to do once today > unfortunately when a bad file found its way into the source distribution). > > Assuming my test runs of the build pass, I'll get the 3.5.3 VOTE thread > out there. > > > > On Mon, Apr 4, 2022 at 6:40 AM Stephen Mallette <[email protected]> > wrote: > >> I pushed a number of little changes last week, but they were mostly to >> non-code related bits of the release branches. afaik, we're still having >> some issues with the merge of gremlin-go to master as there were more >> changes than expected to deal with in the merge. worst case, i suggest that >> we move ahead with release and only put out a 3.5.3-rc1 for gremlin-go and >> then push ahead with 3.5.3/3.6.0 release. Then, when master stabilizes for >> gremlin-go we can do a 3.6.1-rc1 immediately. I'm also a bit behind on few >> other code freeze items, so release artifacts may not be available today. >> >> On Mon, Mar 28, 2022 at 7:20 AM Stephen Mallette <[email protected]> >> wrote: >> >>> Moving forward with code freeze - let's look to get all open PRs >>> expected to land in releases merged early this week so that proper testing >>> of all changes can start. As usual, we will use this thread, throughout >>> code freeze as issues arise. Thanks! >>> >>> On Thu, Mar 24, 2022 at 1:49 PM Stephen Mallette <[email protected]> >>> wrote: >>> >>>> I should have sent this a bit earlier but I think we largely have all >>>> of the PRs in review at this point that will cover what was planned for >>>> 3.5.3 and 3.6.0. As such I think we can enter into code freeze for close of >>>> business tomorrow and get organized for release. Please yell if there are >>>> any outstanding concerns to address. >>>> >>>> >>>>
