Ok - code freeze is lifted. Recall from previous discussion that the master branch is basically our line of development right now and that it will correspond to 3.1.1-SNAPSHOT development. Therefore current dev work to be merged to this branch should not incur big breaking changes. If something really bad happens and we have to hot fix something, we can branch from the 3.1.0-incubating tag, fix and release from there i guess.
Note that I've bumped to 3.1.1-SNAPSHOT and pushed. Finally, i think that by the release after next (if lucky, next release), i'll have the "Release Process" docs solid to the point where anyone will be able to execute them and have a successful day with it. Things went pretty smoothly today - just a minor flub with gpg that I can't seem to explain but other than that, the process is getting quite refined.. On Mon, Nov 16, 2015 at 6:31 AM, Stephen Mallette <[email protected]> wrote: > This was a successful code freeze - this was a nice addition to the > release process. Thanks to those who helped polish things up over the last > week. I'm starting the release process and will announce the VOTE on > 3.1.0-incubating in the next few hours. > > On Fri, Nov 6, 2015 at 12:39 PM, Dylan Millikin <[email protected]> > wrote: > >> Mine will be in soon. I'm just trying to make sure I test threaded >> transactions against titan before pushing. >> >> On Fri, Nov 6, 2015 at 6:34 PM, Stephen Mallette <[email protected]> >> wrote: >> >> > What about the other issue? >> > >> > https://issues.apache.org/jira/browse/TINKERPOP3-917 >> > >> > >> > >> > On Fri, Nov 6, 2015 at 12:31 PM, Daniel Kuppitz <[email protected]> >> wrote: >> > >> > > > >> > > > What is the status on the remaining issues? Will we see PRs today? >> > > >> > > >> > > Not today, perhaps tomorrow.I just found a promising approach to solve >> > the >> > > edge-copy problem, it's actually pretty simple code. Will have to >> write >> > > some more tests though to verify that it works for all GraphComputers. >> > > No problem if it doesn't make it into 3.1.0 due to missing votes, we >> > > haven't had anybody (or only few people) asking for it so far. >> > > >> > > Cheers, >> > > Daniel >> > > >> > > >> > > On Fri, Nov 6, 2015 at 5:36 PM, Stephen Mallette < >> [email protected]> >> > > wrote: >> > > >> > > > I've put the hammer down and somehow knocked out a draft of the >> > developer >> > > > docs. You can see the published form here: >> > > > >> > > > * >> > > > >> > > >> > >> http://tinkerpop.incubator.apache.org/docs/3.1.0-SNAPSHOT/tutorials-getting-started.html >> > > > < >> > > > >> > > >> > >> http://tinkerpop.incubator.apache.org/docs/3.1.0-SNAPSHOT/tutorials-getting-started.html >> > > > >* >> > > > >> > > > It's not exactly what I thought it would be when I started, but I >> like >> > > how >> > > > it ended. I expect to clean up spelling mistakes and other odds and >> > ends, >> > > > but for purposes of code review and general feedback I think it's >> good >> > to >> > > > go. I sense we'll tweak its contents in future releases, but this >> gives >> > > us >> > > > our pattern to follow for other tutorials. I love that we now have >> > > > something we can point new users at to help them get into TinkerPop. >> > > > >> > > > As it stands, my work is done for code freeze though I still need >> VOTEs >> > > > from committers on my two PRs: >> > > > >> > > > https://github.com/apache/incubator-tinkerpop/pull/137 >> > > > https://github.com/apache/incubator-tinkerpop/pull/138 >> > > > >> > > > What is the status on the remaining issues? Will we see PRs today? >> > > Dylan? >> > > > Kuppitz? >> > > > >> > > > >> > > > >> > > > >> > > > On Thu, Nov 5, 2015 at 6:13 AM, Stephen Mallette < >> [email protected] >> > > >> > > > wrote: >> > > > >> > > > > Just a reminder that code freeze on 3.1.0 is coming up for monday >> > 11/9. >> > > > > We have a handful of remaining issues open: >> > > > > >> > > > > >> > > > > >> > > > >> > > >> > >> https://issues.apache.org/jira/issues/?jql=project%20%3D%20TINKERPOP3%20AND%20fixVersion%20%3D%203.1.0-incubating%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20assignee%20ASC%2C%20priority%20DESC >> > > > > >> > > > > so i would expect those to start showing up in code review today. >> > Note >> > > > > that we are shorthanded for code review votes as Marko is gone for >> > the >> > > > next >> > > > > few days, so please pay attention to the pull request queue and >> let's >> > > > move >> > > > > things through quickly. If you are expecting trouble meeting code >> > > freeze >> > > > > deadline, please yell. >> > > > > >> > > > > For my part, I expect that I will not have this ticket done in >> time >> > for >> > > > > code freeze: >> > > > > >> > > > > https://issues.apache.org/jira/browse/TINKERPOP3-923 >> > > > > >> > > > > It is however a "documentation task" and we've agreed that we can >> > allow >> > > > > such things to trickle into the early part of code freeze. We'll >> see >> > > if >> > > > > allowing that causes problems and if we need to be stricter with >> that >> > > > > policy. >> > > > > >> > > > >> > > >> > >> > >
