I only released Apache Commons components. Would Jena be too different/complex?
I have GitHub 2FA, ASF gpg keys (4096), Maven settings.xml set up for ASF maven repo. So if the process is not too hard for a beginner, I can volunteer to either sidekick and review/learn the process, or to RM 3.10.0. I haven't done much Jena development, so maybe I can help running releases and website migration & issues for now :) (also want to discuss Fuseki JS web layer later, as backbone.js isn't being used much lately, and we could try something simpler perhaps). Cheers Bruno ________________________________ From: Andy Seaborne <[email protected]> To: [email protected] Sent: Thursday, 13 December 2018 7:29 AM Subject: Re: [DISCUSS] Move Jena repo to gitbox or github On 12/12/2018 15:53, Chris Tomlinson wrote: > Hi Andy, > >> On Dec 12, 2018, at 7:35 AM, Andy Seaborne <[email protected]> wrote: >> >> >> >> On 11/12/2018 17:19, Chris Tomlinson wrote: >>> Hi Andy, >>> My GH and ASF accounts are linked. As I understand the note from D.Gruno >>> once jena is moved to GB then we can use either GB or GH or both in our >>> individual workflows. For me just working with GH would be my choice. >>> I’m not sure how far away 3.10.0 is (I’ve completed all of the pending >>> jena-text updates for 3.10.0) but maybe it makes sense if that release can >>> be completed prior to moving from git-wip-us without running into the >>> forced move beginning on 7 Feb 2019. >> >> I'd like to avoid a forced move, if nothing else, out of politeness to INFRA >> because they asked nicely. > > I certainly agree that we’d be better served by orchestrating a voluntary > move. How far away is 3.10.0? Ssh! but I _hope_ end of Dec. Ish. Maybe slip into Jan. I'm not so worried about the git repo changes affecting things very much. It happens automatically and at a point in time. Might/should work to just edit .git/config Andy > > Regards, > Chris >
