Re: [DISCUSS] JIRA Version page only available to authenticated users

[Nick Dimiduk <nd...@apache.org>]

For implementing this change, I have filed
https://issues.apache.org/jira/browse/HBASE-26771

On Tue, Oct 26, 2021 at 8:36 PM Sean Busbey <bu...@apache.org> wrote:

> for example, this is roughly what HBase 2.4.7 would look like:
>
>
> https://gist.github.com/busbey/b5a849626bc4fcc2cbdd18f56c8d2807#file-apache-hbase-2-4-7-releasenotes-md
>
> (but the url would be to the rel/2.4.7 tag on github)
>
> On Tue, Oct 26, 2021 at 1:33 PM Sean Busbey <bu...@apache.org> wrote:
>
> > let's just start pointing at the release notes? for any given release
> that
> > should be where we as a community have spent the most effort crafting a
> > message for our downstream folks.
> >
> > preferably rendered. Could we start putting the generated release note
> > that just the part relevant to the specific patch release into the GitHub
> > release tag's release note? IIRC that will render markdown and is
> readable
> > without logging in. We could integrate populating it via the GitHub API
> > into the release tooling.
> >
> > On Tue, Oct 26, 2021 at 11:39 AM Nick Dimiduk <nd...@apache.org>
> wrote:
> >
> >> I find it surprising that our announcements point people at something
> that
> >> requires a login. It seems not very “open” or “inviting”.
> >>
> >> On Tue, Oct 26, 2021 at 07:26 Sean Busbey <bu...@apache.org> wrote:
> >>
> >> > We have historically linked to the Jira Version page because it
> >> provides a
> >> > starting point on issue navigation that we don't get elsewhere. Plenty
> >> of
> >> > interactions with our issue tracker require a login. Why is that
> >> threshold
> >> > not acceptable here? I think we should just note that a login with
> >> > low-friction signup is required. Though I guess we will need to
> validate
> >> > that it's still straightforward to create a jira account.
> >> >
> >> > The changelog and release notes for the release are both available on
> >> > downloads.a.o if we want to link to something available without a
> login
> >> > rather than just mentioning them. If we're going to change what we'd
> >> link
> >> > to I'd rather one of those than jira at all.
> >> >
> >> > On Tue, Oct 26, 2021 at 5:55 AM 张铎(Duo Zhang) <pa...@gmail.com>
> >> > wrote:
> >> >
> >> > > At least for me I haven't typed it up in the past...
> >> > >
> >> > > I'm not sure whether you need to set up a template manually first...
> >> > >
> >> > > Wei-Chiu Chuang <we...@cloudera.com.invalid> 于2021年10月26日周二
> >> 下午5:48写道：
> >> > >
> >> > > > Duo,
> >> > > > Just out of curiosity, is this release note in the JIRA populated
> >> > > > automatically? Or someone typed it up?
> >> > > >
> >> > > > On Tue, Oct 26, 2021 at 4:25 PM 张铎(Duo Zhang) <
> >> palomino219@gmail.com>
> >> > > > wrote:
> >> > > >
> >> > > > > I think this is what we should link in the announcement?
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310753&version=12350545
> >> > > > >
> >> > > > > We should link the release note, not the page where we can
> >> generate
> >> > the
> >> > > > > release note...
> >> > > > >
> >> > > > > Just my thoughts. Thanks.
> >> > > > >
> >> > > > > Nick Dimiduk <nd...@apache.org> 于2021年10月26日周二 上午1:19写道：
> >> > > > >
> >> > > > > > Heya,
> >> > > > > >
> >> > > > > > The link we include in our announcement emails is only
> >> accessible
> >> > for
> >> > > > > > people who are logged into JIRA. Seems like bad form.
> >> > > > > >
> >> > > > > > I.e.,
> >> > > https://issues.apache.org/jira/projects/HBASE/versions/12350545
> >> > > > > >
> >> > > > > > I doubt this is by design on our part. I wonder if JIRA has
> >> always
> >> > > been
> >> > > > > > configured this way, or if it's an (un)intentional change on
> the
> >> > part
> >> > > > of
> >> > > > > > Infra.
> >> > > > > >
> >> > > > > > Should we instead link to something else?
> >> > > > > >
> >> > > > > > Thanks,
> >> > > > > > Nick
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> >
>