Here's the revised validate-distribution.sh file: https://gist.github.com/spmallette/8a1296a50320fe0e1b350fc6caef372e
Please use that to test out the release (if you use that approach - it really is a super easy way to checkout the distribution if you'd like to participate in the vote and don't have a ton of time to look at everything manually). I'll commit these changes to the repo after release is all settled. On Mon, Jul 18, 2016 at 4:00 PM, Stephen Mallette <[email protected]> wrote: > Having some trouble with release. Some of the trouble is a bit out of my > control - like a bank of thunderstorms flickering my internet connection. > Some of the trouble was self-created, like trying to rename the > distributions - which I've abandoned doing for this release (we'll do it > for the next one now that I see all the problems with doing that). And now > i'm stuck with validate-distribution.sh which doesn't seem to want to > behave. I think I have it figured out now with a patch or two. I'll post > that as a gist later for everyone to use as a replacement for the one in > git or perhaps make the commit to master before i start working on 3.2.1 - > I don't plan to go back through the release process for 3.1.3 to make > another commit on tp31 at this point. Anyway, as soon as this > validate-distribution.sh run finishes successfully, you can expect a VOTE > thread for 3.1.3. > > If I can get 3.2.1 out as well tonight I will but it might be better for > me to wait until morning because I don't want to make any dumb mistakes at > this point and it's always good to have a sharp mind when doing this stuff. > So, worst case, the 3.2.1 VOTE should start tomorrow morning. Sorry for the > delay.... > > Thanks, > > Stephen > > > > On Sat, Jul 16, 2016 at 8:57 AM, Marko Rodriguez <[email protected]> > wrote: > >> Thanks again for handling the release process. >> >> I appreciate nearly nothing in this world except for the effort you put >> into the release process. >> >> Thank you, >> Marko. >> >> http://markorodriguez.com >> >> >> >> > On Jul 15, 2016, at 4:39 PM, Stephen Mallette <[email protected]> >> wrote: >> > >> > Everything looks good to do a vote for 3.1.3 and 3.1.2 on Monday. I'm >> going >> > to publish the final SNAPSHOT docs over the weekend - nothing has >> changed >> > of significance for the artifacts SNAPSHOTS to warrant republishing. >> > >> > On Wed, Jul 13, 2016 at 7:08 AM, Stephen Mallette <[email protected] >> > >> > wrote: >> > >> >> I've run full integration tests on tp31 and master and both passed. As >> a >> >> result, I've published 3.2.1-SNAPSHOT and 3.1.3-SNAPSHOT to the Apache >> >> Snapshots repo. I hope developers of graph databases, drivers, etc. >> can get >> >> a moment to try it out and report any problems. >> >> >> >> >> >> On Tue, Jul 12, 2016 at 9:52 AM, Marko Rodriguez <[email protected] >> > >> >> wrote: >> >> >> >>> Hello, >> >>> >> >>>> Code freeze essentially begins today. We cleared up all the remaining >> >>>> issues that were lingering. Please focus on testing and documentation >> >>> for >> >>>> the next few days with a vote for release on Monday July 18th 2016. >> >>> >> >>> >> >>> Thank you Stephen. >> >>> >> >>> As I was saying in HipChat, while we have merged the >> >>> PathRetractionStrategy work ( >> >>> https://issues.apache.org/jira/browse/TINKERPOP-1254 < >> >>> https://issues.apache.org/jira/browse/TINKERPOP-1254>), I’m >> continually >> >>> benchmarking and testing scenarios and am finding numerous little >> nick nack >> >>> bugs and obvious optimizations. I’m going to continue to CTR to >> master/ >> >>> these updates and note that each evening I’m doing local integration >> >>> testing to ensure that no one finds a hiccup (if any) that were >> caused by >> >>> this “nick nack” work I’m doing. >> >>> >> >>> Again, thank you Stephen for managing the release process (as always). >> >>> >> >>> Marko. >> >>> >> >>> http://markorodriguez.com >> >>> >> >>> >> >> >> >> >
