I don't think it's a blocker, though I wonder what the point of that date
and attribution are on the WebUI.

Maybe file a follow-on JIRA to remove it for the future?

On Thu, Oct 6, 2016 at 3:09 PM, Sangjin Lee <sj...@apache.org> wrote:

> I looked into building it on jenkins earlier, but it appears that this
> jenkins job is busted (at least for 2.6.x):
> https://builds.apache.org/job/HADOOP2_Release_Artifacts_Builder/
>
> I don't have access to the job configuration, so I'm unable to fix it atm.
>
> That said, I do think Allen has a point. It strikes me that the release
> manager building it under his/her own control shouldn't be a problem, if
> not better. Also, the how-to-release wiki currently seems to suggest
> building it locally is fine (http://wiki.apache.org/hadoop/HowToRelease).
>
> IMO I don't think this is a blocker. Thoughts?
>
> Thanks,
> Sangjin
>
> On Thu, Oct 6, 2016 at 1:39 PM, Akira Ajisaka <ajisa...@oss.nttdata.co.jp>
> wrote:
>
> > > It wasn't 'renamed' to jenkins, prior releases were actually built by
> > and on the Jenkins infrastructure. Which was a very very bad idea:  it's
> > insecure and pretty much against ASF policy.
> >
> > Sorry for the confusion. I should not have used the word 'rename'.
> > What I meant is that "would you change the name to 'jenkins' by using the
> > Jenkins infra?"
> >
> > Regards,
> > Akira
> >
> >
> > On 10/7/16 03:04, Allen Wittenauer wrote:
> >
> >>
> >> On Oct 5, 2016, at 10:35 PM, Akira Ajisaka <ajisa...@oss.nttdata.co.jp>
> >>> wrote:
> >>> Can we rename it?
> >>>
> >>> AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed
> to
> >>> jenkins.
> >>>
> >>
> >>         That's not how that works.
> >>
> >>         It's literally storing the id of the person who built the
> >> classes.  It wasn't 'renamed' to jenkins, prior releases were actually
> >> built by and on the Jenkins infrastructure. Which was a very very bad
> >> idea:  it's insecure and pretty much against ASF policy.
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
> >> For additional commands, e-mail: common-dev-h...@hadoop.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
> > For additional commands, e-mail: common-dev-h...@hadoop.apache.org
> >
> >
>

Reply via email to