It was a github issue that came in this morning that made me think to suggest that we should disable github issues. On that issue I typed my standard thing that basically said - "we are in maintenance mode - no more releases" to which the poster basically replied: "well if you aren't releasing anymore then you aren't in maintenance mode - the project is closed". Is that where we are now, "closed"? Is there anything that would trigger a non-apache release of any of the TinkerPop 2.x stuff? if not, then the poster is probably right and we should probably change our wording on that.
On Tue, Nov 24, 2015 at 7:50 AM, Daniel Kuppitz <[email protected]> wrote: > +1 > > I will also get rid of TP2 support next time I release a new version of the > Neo4j plugin. > > On Tue, Nov 24, 2015 at 1:41 PM, Stephen Mallette <[email protected]> > wrote: > > > We are still getting issues being added to the various TP 2.x projects in > > GitHub. Should we disable issues in GitHub for the old projects? > > > > Maybe that will further force folks to recognize that TP2 is no > > more.....thoughts? > > >
