All,
as subject, I think 1.1 is ready to ship. I am planning to cut a release over the weekend unless anybody has any pending work that needs to merge right away.
Cheers Fabio
"Fabio M. Di Nitto" fdinitto@redhat.com writes:
as subject, I think 1.1 is ready to ship. I am planning to cut a release over the weekend unless anybody has any pending work that needs to merge right away.
Hi Fabio,
Why do we neglect #100 for so long?
On 2/20/2018 9:34 AM, Ferenc Wágner wrote:
"Fabio M. Di Nitto" fdinitto@redhat.com writes:
as subject, I think 1.1 is ready to ship. I am planning to cut a release over the weekend unless anybody has any pending work that needs to merge right away.
Hi Fabio,
Why do we neglect #100 for so long?
I didn´t neglet it per se. I explained Bin Liu on IRC that I would merge it once we switch to libnozzle and fix kronosnetd build for good and he was ok with it.
Afterall we don´t support kronosnetd so I am not too worried about it atm.
Fabio
"Fabio M. Di Nitto" fdinitto@redhat.com writes:
On 2/20/2018 9:34 AM, Ferenc Wágner wrote:
"Fabio M. Di Nitto" fdinitto@redhat.com writes:
as subject, I think 1.1 is ready to ship. I am planning to cut a release over the weekend unless anybody has any pending work that needs to merge right away.
Why do we neglect #100 for so long?
I didn´t neglet it per se. I explained Bin Liu on IRC that I would merge it once we switch to libnozzle and fix kronosnetd build for good and he was ok with it.
That's fine, I'm happy it isn't forgotten.
"Fabio M. Di Nitto" fdinitto@redhat.com writes:
as subject, I think 1.1 is ready to ship. I am planning to cut a release over the weekend unless anybody has any pending work that needs to merge right away.
I tested creating preliminary packages and things worked out nicely. The only thing missing is some sort of a changelog for users. Don't you think we should provide one? It could be reused in the release announcement as well.
On 2/23/2018 3:59 PM, Ferenc Wágner wrote:
"Fabio M. Di Nitto" fdinitto@redhat.com writes:
as subject, I think 1.1 is ready to ship. I am planning to cut a release over the weekend unless anybody has any pending work that needs to merge right away.
I tested creating preliminary packages and things worked out nicely. The only thing missing is some sort of a changelog for users. Don't you think we should provide one? It could be reused in the release announcement as well.
The Changelog should be automatically generated in the tarball but it appears is not. We can fix that and release 1.1
Fabio
On 2/23/2018 4:03 PM, Fabio M. Di Nitto wrote:
On 2/23/2018 3:59 PM, Ferenc Wágner wrote:
"Fabio M. Di Nitto" fdinitto@redhat.com writes:
as subject, I think 1.1 is ready to ship. I am planning to cut a release over the weekend unless anybody has any pending work that needs to merge right away.
I tested creating preliminary packages and things worked out nicely. The only thing missing is some sort of a changelog for users. Don't you think we should provide one? It could be reused in the release announcement as well.
The Changelog should be automatically generated in the tarball but it appears is not. We can fix that and release 1.1
Fixed in https://github.com/kronosnet/kronosnet/pull/137
I´ll release 1.1 over the weekend if there are no further urgent concerns.
Cheers Fabio
Fabio
Devel mailing list Devel@lists.kronosnet.org https://lists.kronosnet.org/mailman/listinfo/devel
"Fabio M. Di Nitto" fdinitto@redhat.com writes:
On 2/23/2018 3:59 PM, Ferenc Wágner wrote:
"Fabio M. Di Nitto" fdinitto@redhat.com writes:
as subject, I think 1.1 is ready to ship. I am planning to cut a release over the weekend unless anybody has any pending work that needs to merge right away.
I tested creating preliminary packages and things worked out nicely. The only thing missing is some sort of a changelog for users. Don't you think we should provide one? It could be reused in the release announcement as well.
The Changelog should be automatically generated in the tarball but it appears is not. We can fix that and release 1.1
I didn't mean an automatically generated changelog, but something for human consumption, which users can make sense of. A prettier git log still does not strike the best balance of detail/overview in my opinion.
On 2/23/2018 4:44 PM, Ferenc Wágner wrote:
"Fabio M. Di Nitto" fdinitto@redhat.com writes:
On 2/23/2018 3:59 PM, Ferenc Wágner wrote:
"Fabio M. Di Nitto" fdinitto@redhat.com writes:
as subject, I think 1.1 is ready to ship. I am planning to cut a release over the weekend unless anybody has any pending work that needs to merge right away.
I tested creating preliminary packages and things worked out nicely. The only thing missing is some sort of a changelog for users. Don't you think we should provide one? It could be reused in the release announcement as well.
The Changelog should be automatically generated in the tarball but it appears is not. We can fix that and release 1.1
I didn't mean an automatically generated changelog, but something for human consumption, which users can make sense of. A prettier git log still does not strike the best balance of detail/overview in my opinion.
https://docs.google.com/document/d/1ZNXpyBpzpj0F1RQkpTj2cIeiF6aVaNW-IKeuFH5F...
we can add it here with the major highlights between 1.0 and 1.1. I am using that doc as template for release announcements.
Cheers
Fabio
-
Fabio M. Di Nitto -
Fabio M. Di Nitto -
wferi＠niif.hu