Hi, Everyone, please update the CHANGELOG with your * …. notes of what you accomplished. We have JIRA itemizations, but also put them into the CHANGELOG too.
In general, every time you commit to a release branch, be sure to add your CHANGELOG notes. Thanks, Marko. http://markorodriguez.com On Oct 15, 2015, at 8:00 AM, Stephen Mallette <[email protected]> wrote: > Another quick status check for the 3.0.2 countdown. There are just two > issues left open in JIRA on this version. As both are under development > right now, I would think we can get them through our new RTC process by end > of day tomorrow so that I can just wake up with a fresh mind on Monday and > just head right to the release process. Please yell if you're working on > those issues and don't think that is possible for some reason. > > If you have not done so already, please take a look at our upgrade docs and > make changes as needed (again, nice to have this all squared away by the > weekend): > > https://github.com/apache/incubator-tinkerpop/blob/master/docs/src/upgrade-release-3.0.x-incubating.asciidoc > > Thanks, > > Stephen > > > > On Mon, Oct 12, 2015 at 11:03 AM, Stephen Mallette <[email protected]> > wrote: > >> Hi all, just a quick reminder that we're about a week a way from getting >> the 3.0.2 release process going. As you may have noted from another thread >> I just posted, I'm in the process of reviewing LICENSE/NOTICE in >> preparation for that release. Looks like we are down to just three open >> issues with 3.0.2. :) >> >> On Thu, Oct 8, 2015 at 8:24 AM, Stephen Mallette <[email protected]> >> wrote: >> >>> Ok - moved 838 off of 3.0.1 barring any SEO experts stepping up. I just >>> completed that bug fix to 870 which was pretty simple after all the work I >>> had to do to just initially identify the problem. >>> >>> On Wed, Oct 7, 2015 at 12:59 PM, Daniel Kuppitz <[email protected]> wrote: >>> >>>> I'm currently working on 852, I think I will be done today/tomorrow. Once >>>> that's done, I can work on 319 - this only means: verify that the >>>> TinkerGraph persistence works well with BLVP and write unit/integration >>>> tests for it. The other pending things in 319 are subject to 3.1.0. >>>> >>>> Let's push 838 to 3.1.0, since I have absolutely no idea how to solve it >>>> (unless someone else comes up with some ideas). >>>> >>>> Cheers, >>>> Daniel >>>> >>>> >>>> On Wed, Oct 7, 2015 at 5:24 PM, Stephen Mallette <[email protected]> >>>> wrote: >>>> >>>>> There are currently 5 unresolved issues assigned to 3.0.2: >>>>> http://bit.ly/1Q7Ez8O >>>>> >>>>> In summary we have: >>>>> >>>>> https://issues.apache.org/jira/browse/TINKERPOP3-852 (Kuppitz) >>>>> https://issues.apache.org/jira/browse/TINKERPOP3-838 (Unassigned - >>>>> probably >>>>> me/Kuppitz) >>>>> https://issues.apache.org/jira/browse/TINKERPOP3-319 (Kuppitz) >>>>> https://issues.apache.org/jira/browse/TINKERPOP3-865 (Jason) >>>>> https://issues.apache.org/jira/browse/TINKERPOP3-858 (Jason) >>>>> >>>>> My point in bringing these up is to open up dialog on any issues with >>>> these >>>>> final tickets as we'd previously discussed closing the doors on 3.0.2 >>>> on >>>>> 10/19. I'd also like to ask if anyone is aware of any other critical >>>>> issues not on the general 3.0.2 list - if so, please raise them for >>>>> discussion. >>>>> >>>>> For me, I'm concerned about 838 which I'm somewhat tied to, but I'm not >>>>> really clear what we need to do. Mr. Kuppitz, can you help us come to >>>> some >>>>> concrete steps to take for that issue please? If time is an issue and >>>> you >>>>> have SEO research to do, let's consider pushing this issue forward to >>>> 3.1.0 >>>>> and get stuff right at that point. Any SEO folks on the list who can >>>> help >>>>> on that one? >>>>> >>>>> I'd also like to make sure the road is clear to finish up 319. As I >>>>> recall, that issue was blocked by: >>>>> >>>>> https://issues.apache.org/jira/browse/TINKERPOP3-828 >>>>> >>>>> but that is complete now, so 319 should be clear. All good there, >>>> Daniel? >>>>> >>>>> Thanks, everyone - Please feel free to chime in with any issues >>>> related to >>>>> 3.0.2. >>>>> >>>> >>> >>> >>
