Yup, looks like a custom velocity schema is the way to go here. @JB would I require any additional permissions for this ? I don't mind playing around with this.
On Thu, Dec 15, 2016 at 10:13 PM Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > +1 Dan, it's exactly what I had in mind. I would be great to e > experiment a bit around that. > > Regards > JB > > On 12/15/2016 05:35 PM, Dan Halperin wrote: > > Amit, I think you bring up a wonderful point. Release notes are hard to > > grok right now. > > > > I wonder if we can expose the component name (which issues are already > > tagged with) in a custom release notes template? https://developer. > > atlassian.com/jiradev/jira-platform/jira-architecture/ > > > jira-templates-and-jsps/creating-a-custom-release-notes-template-containing- > > release-comments > > > > On Thu, Dec 15, 2016 at 6:15 AM, Jean-Baptiste Onofré <j...@nanthrax.net> > > wrote: > > > >> Yes, agree. We had kind of similar discussion while ago: > >> "java-sdk-extension" vs "io" afair ;) > >> > >> Regards > >> JB > >> > >> > >> On 12/15/2016 03:12 PM, Amit Sela wrote: > >> > >>> If we can do this via JIRA component, even better, but then we would > need > >>> to work on components. > >>> > >>> On Thu, Dec 15, 2016 at 3:45 PM Jean-Baptiste Onofré <j...@nanthrax.net> > >>> wrote: > >>> > >>> Hi Amit, > >>>> > >>>> interesting idea, even if it's redundant with the Jira component. > >>>> However, the Jira component is also generic (for instance, > >>>> java-sdk-extension is for both extensions and IOs). > >>>> > >>>> If possible, I would more work on the component (and customize the > >>>> Release Notes output to include it). > >>>> > >>>> Regards > >>>> JB > >>>> > >>>> On 12/15/2016 02:30 PM, Amit Sela wrote: > >>>> > >>>>> I took a look at the release notes for 0.4.0-incubating now and I > felt > >>>>> > >>>> like > >>>> > >>>>> it could have been "tagged" in a way that helps people focus on > what's > >>>>> interesting to them > >>>>> Currently, all resolved issues simply appear as they are in JIRA, > but we > >>>>> don't have any way to tag them. > >>>>> > >>>>> What if we were to prefix the issue title with the component, > examples: > >>>>> [runners-spark] fixed-some Spark runner issue > >>>>> [SDK] added state and timers API > >>>>> [IO] added HBaseIO support > >>>>> ... > >>>>> > >>>>> This would be more readable, and allow users to focus by looking for > >>>>> > >>>> what's > >>>> > >>>>> interesting to them in a release (CTRL/CMD + F in the browser..) > >>>>> > >>>>> Thoughts ? > >>>>> > >>>>> > >>>> -- > >>>> Jean-Baptiste Onofré > >>>> jbono...@apache.org > >>>> http://blog.nanthrax.net > >>>> Talend - http://www.talend.com > >>>> > >>>> > >>> > >> -- > >> Jean-Baptiste Onofré > >> jbono...@apache.org > >> http://blog.nanthrax.net > >> Talend - http://www.talend.com > >> > > > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com >
