That sounds pretty promising. What would the next step be in that case? On Mon, Nov 16, 2015 at 7:48 PM, Jeremy Hanna <[email protected]> wrote:
> And to be clear, all external linking with the old project key will work > and redirect to the new project key. So if you linked to a TP3 ticket on > stack overflow, it will redirect properly to TP. > > > On Nov 16, 2015, at 12:38 PM, Jeremy Hanna <[email protected]> > wrote: > > > > I checked into it, and as I mentioned on the infra ticket: > > > > It looks like the old links will still work if you edit the > project key (as well as the project name but the project key is the > stickier bit). > > > https://confluence.atlassian.com/jira/editing-a-project-key-389284652.html > > The only thing that appears to be lost is the linking within > tickets using the old key in free-text, > > such as referencing another ticket in a comment like > TINKERPOP3-123 - that will no longer be auto-linked. > > However that's a relatively small impact I think. > > > > I’ll leave it to this group though as to whether you would like an > updated key/project that’s more future proof. > > > >> On Nov 12, 2015, at 6:31 AM, Stephen Mallette <[email protected]> > wrote: > >> > >> It's a bit unfortunate that no one seemed to notice that the naming of > the > >> JIRA project bound us to "3" when we were reviewing the migration from > >> github. I've often thought of that over the past year and whether or > not > >> it would be possible to change it to just TINKERPOP. The problem at > this > >> point of course is the number of links that point at TINKERPOP3-*. The > >> main question I have at the moment is whether or not Apache Infra could > do > >> anything to help mitigate that and what their recommendations would be > in > >> that area. > >> > >> > >> On Wed, Nov 11, 2015 at 11:34 PM, Jeremy Hanna < > [email protected]> > >> wrote: > >> > >>> If it's no big deal then no worries. I just thought I would look into > it > >>> in case it would become more difficult to manage later. > >>> > >>>> On Nov 11, 2015, at 3:51 PM, Jeremy Hanna <[email protected] > > > >>> wrote: > >>>> > >>>> I was curious why the Jira project was named TinkerPop3 instead of > just > >>> TinkerPop and asked Stephen Mallette about it and it sounded like it > was > >>> just something that happened on import. So I just thought I would > check to > >>> see whether it could be changed. I created an INFRA ticket to ask and > got > >>> the following response on > >>> https://issues.apache.org/jira/browse/INFRA-10752 from Gavin: > >>>> > >>>> I'm guessing the reason is because the supplied JSON export file from > >>> Github (https://github.com/tinkerpop/tinkerpop3) had TINKERPOP3 as the > >>> project name. > >>>> We can rename it but would [need] a link to the mailing list > >>> discussion and PMC agreement where the name change was discussed. > >>>> Thanks > >>>> > >>>> So I wanted to reach out on this list to find out whether people > really > >>> care enough to make the change. We can also ask whether a redirect > could > >>> be put in place for incoming links for the project and for specific > tickets. > >>>> > >>>> I would just think that if the change is done it would be better to do > >>> it sooner than later. Stephen also mentioned after going to TP4 it > could > >>> be changed to just TinkerPop and the TP3 project could be retired. > >>>> > >>>> In any case, just wanted to bring it up. It’s not a huge deal by any > >>> means, but I just thought I would check. > >>>> > >>>> Cheers, > >>>> > >>>> Jeremy > >>> > > > >
