I sure appreciate you are taking this on Matt, whenever it comes :-) Gary
On Tue, Jun 19, 2018 at 7:50 AM Matt Sicker <[email protected]> wrote: > No offense taken! I didn’t want you all to think I dropped the ball here. > ☺️ > > On Tue, Jun 19, 2018 at 08:32, Dominik Psenner <[email protected]> wrote: > > > On 2018-06-18 20:34, Matt Sicker wrote: > > > There's plenty of good reasons to migrate! I've just been rather busy > > > lately (currently closing on a new condo), so I haven't had a chance to > > > follow through with this. Since there are pom updates and site patches > to > > > accompany this, I'd rather not launch it off when I can't intervene to > > > clean up the results. > > > > I hope you haven't taken this message as an offense and if so I would > > like to apologize. I've not intended in no way to make this message an > > offense but upon receiving a feedback from infra I thought this is > > something worth to be shared with everyone. > > > > > > > > On 18 June 2018 at 13:22, Dominik Psenner <[email protected]> wrote: > > > > > >> Moving to gitbox would give github users ci outputs and thus provide > > >> automated feedbacks from ci when pull requests are built. > > >> > > >> https://issues.apache.org/jira/plugins/servlet/mobile# > > >> issue/INFRA-14492/comment/16516065 > > >> > > >> On Thu, 14 Jun 2018, 16:57 Matt Sicker, <[email protected]> wrote: > > >> > > >>> I haven't had a chance to follow up with Infra (since I know this > will > > >> take > > >>> a bit of collaboration to change). I'm thinking to start backwards > from > > >> any > > >>> repos that don't have any upcoming or recent releases, then > progressing > > >>> forward until all of them have been moved. > > >>> > > >>> On 13 June 2018 at 20:19, Ralph Goers <[email protected]> > > >> wrote: > > >>>> Whatever happened with this? > > >>>> > > >>>> Ralph > > >>>> > > >>>>> On May 7, 2018, at 8:38 AM, Matt Sicker <[email protected]> wrote: > > >>>>> > > >>>>> And here is my +1. > > >>>>> > > >>>>> This vote passes with 5 +1s binding and 1 +1 non-binding. I'll > follow > > >>> up > > >>>>> with the migration details over the next couple days. > > >>>>> > > >>>>> On 30 April 2018 at 07:04, Apache <[email protected]> > > >> wrote: > > >>>>>> +1 > > >>>>>> > > >>>>>> Ralph > > >>>>>> > > >>>>>> > > >>>>>>> On Apr 29, 2018, at 7:38 PM, Ílson Bolzan <[email protected]> > > >>> wrote: > > >>>>>>> +1 > > >>>>>>> > > >>>>>>>> On Sun, Apr 29, 2018 at 3:20 PM, Matt Sicker <[email protected]> > > >>>> wrote: > > >>>>>>>> Good point on the clarification. I said all git repos, and that > > >>>> actually > > >>>>>>>> entails: > > >>>>>>>> > > >>>>>>>> * chainsaw > > >>>>>>>> * log4cxx > > >>>>>>>> * log4j2 and all its repos > > >>>>>>>> * log4net > > >>>>>>>> * log4php > > >>>>>>>> * parent pom > > >>>>>>>> > > >>>>>>>> In fact, the only repos this doesn't cover are the old log4j 1 > svn > > >>>> repos > > >>>>>>>> that we have. > > >>>>>>>> > > >>>>>>>>> On 29 April 2018 at 05:08, Dominik Psenner <[email protected] > > > > >>>> wrote: > > >>>>>>>>> +1 > > >>>>>>>>> > > >>>>>>>>> Also for the log4net repository. > > >>>>>>>>> > > >>>>>>>>>> On Sat, 28 Apr 2018, 23:59 Remko Popma, < > [email protected]> > > >>>>>> wrote: > > >>>>>>>>>> +1 > > >>>>>>>>>> > > >>>>>>>>>> On Sat, Apr 28, 2018 at 11:48 PM, Gary Gregory < > > >>>>>> [email protected] > > >>>>>>>>>> wrote: > > >>>>>>>>>> > > >>>>>>>>>>> +1 > > >>>>>>>>>>> > > >>>>>>>>>>> Gary > > >>>>>>>>>>> > > >>>>>>>>>>>> On Sat, Apr 28, 2018, 17:12 Matt Sicker <[email protected]> > > >>> wrote: > > >>>>>>>>>>>> This is a vote to migrate from the existing git-wip-us > > >>>>>>>> infrastructure > > >>>>>>>>>> to > > >>>>>>>>>>>> the currently supported gitbox infrastructure that Infra > > >>> advocates > > >>>>>>>>> for > > >>>>>>>>>>>> using nowadays. Using gitbox will allow our projects to > > >>> integrate > > >>>>>>>>>> better > > >>>>>>>>>>>> with GitHub including the ability to merge PRs directly from > > >> the > > >>>>>>>> site > > >>>>>>>>>> and > > >>>>>>>>>>>> the ability to push commits to GitHub and have them be > > >>>>>>>> automatically > > >>>>>>>>>>>> mirrored back to Apache. Not only that, but new Apache > > >> projects > > >>>>>>>>> cannot > > >>>>>>>>>>> use > > >>>>>>>>>>>> the old git-wip-us infrastructure anymore, so it makes sense > > >> to > > >>>>>>>>> migrate > > >>>>>>>>>>> to > > >>>>>>>>>>>> the best supported option going forward. > > >>>>>>>>>>>> > > >>>>>>>>>>>> The migration process will entail the following: > > >>>>>>>>>>>> > > >>>>>>>>>>>> * Marking existing git repo as read-only > > >>>>>>>>>>>> * Moving repo to gitbox > > >>>>>>>>>>>> * Update website and pom.xml with new SCM URLs > > >>>>>>>>>>>> * Update local git clones with the new remote URL(s) > > >>>>>>>>>>>> > > >>>>>>>>>>>> Note that this vote only applies to the source code. I'm not > > >>>>>>>>>> considering > > >>>>>>>>>>>> using GitHub Issues instead of Jira, for example. Note also > > >> that > > >>>>>>>> this > > >>>>>>>>>>> vote > > >>>>>>>>>>>> does not apply to the use of subversion for publishing the > > >> site > > >>>>>>>>>>> (svnpubsub) > > >>>>>>>>>>>> nor the use of it for publishing releases (only available > via > > >>>> svn), > > >>>>>>>>>>> though > > >>>>>>>>>>>> moving the sites from svnpubsub to gitpubsub (i.e., storing > > >> the > > >>>>>>>>>> generated > > >>>>>>>>>>>> site in a branch called "asf-site", similar to the > "gh-pages" > > >>>>>>>> branch > > >>>>>>>>>>>> feature on GitHub) would be a related topic to cover > > >> separately. > > >>>>>>>>>>>> Please vote +1, +0, -0, or -1. > > >>>>>>>>>>>> > > >>>>>>>>>>>> -- > > >>>>>>>>>>>> Matt Sicker <[email protected]> > > >>>>>>>>>>>> > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> -- > > >>>>>>>> Matt Sicker <[email protected]> > > >>>>>>>> > > >>>>>> > > >>>>>> > > >>>>> > > >>>>> -- > > >>>>> Matt Sicker <[email protected]> > > >>>> > > >>>> > > >>> > > >>> -- > > >>> Matt Sicker <[email protected]> > > >>> > > > > > > > > > > -- > Matt Sicker <[email protected]> >
