Thanks Enrico. I was thinking about the following, which I'm not sure is
valid but an idea: can't we just link to the release notes on the JIRA
(etc...) rather than having a copy as part of the release?
e.g.
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310801&version=12345243
Patrick,
Il ven 20 dic 2019, 21:56 Patrick Hunt ha scritto:
> Why not move to something managed/hosted by JIRA or perhaps Github?
>
Can you elaborate more please?
We are coping release notes from JIRA.
We can copy them to github releases page.
But I think that a page on the website is useful
Why not move to something managed/hosted by JIRA or perhaps Github?
Patrick
On Fri, Dec 20, 2019 at 2:20 AM Norbert Kalmar
wrote:
> +1 on option A.
> But!
> I think we should have a page containing all the changes in all supported
> line. So like option C.
>
> Why? - I agree a specific release
+1 on option A.
But!
I think we should have a page containing all the changes in all supported
line. So like option C.
Why? - I agree a specific release should only contain changes to that
version. If someone wants to see the changes that went into various
releases, he/she should check the website
Hi,
I am preparing release notes for 3.6.0,
as branch-3.6 has been cut from master branch I found that
releasenotes.mdtalk about ZooKeeper 3.0.0 !!
https://github.com/apache/zookeeper/blob/master/zookeeper-docs/src/main/resources/markdown/releasenotes.md
I found also that when I wrote the release
