20 Feb
2018
20 Feb
'18
7:26 a.m.
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
20 Feb
20 Feb
8:34 a.m.
"Fabio M. Di Nitto" <fdinitto(a)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?
--
Regards
Feri
1:37 p.m.
On 2/20/2018 9:34 AM, Ferenc Wágner wrote:
"Fabio M. Di Nitto"
<fdinitto(a)redhat.com> writes:
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
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?
1:53 p.m.
"Fabio M. Di Nitto" <fdinitto(a)redhat.com> writes:
On 2/20/2018 9:34 AM, Ferenc Wágner wrote:
That's fine, I'm happy it isn't forgotten.
--
Thanks,
Feri
"Fabio M. Di Nitto"
<fdinitto(a)redhat.com> writes:
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. 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?
23 Feb
23 Feb
2:59 p.m.
"Fabio M. Di Nitto" <fdinitto(a)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.
--
Regards,
Feri
3:03 p.m.
On 2/23/2018 3:59 PM, Ferenc Wágner wrote:
"Fabio M. Di Nitto"
<fdinitto(a)redhat.com> writes:
The Changelog should be automatically generated in the tarball but it
appears is not. We can fix that and release 1.1
Fabio
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. 
3:43 p.m.
On 2/23/2018 4:03 PM, Fabio M. Di Nitto wrote:
On 2/23/2018 3:59 PM, Ferenc Wágner wrote:
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 M. Di Nitto"
<fdinitto(a)redhat.com> writes:
The Changelog should be automatically generated in the tarball but it
appears is not. We can fix that and release 1.1 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.
Fabio
_______________________________________________
Devel mailing list
Devel(a)lists.kronosnet.org
https://lists.kronosnet.org/mailman/listinfo/devel
3:44 p.m.
"Fabio M. Di Nitto" <fdinitto(a)redhat.com> writes:
On 2/23/2018 3:59 PM, Ferenc Wágner wrote:
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.
--
Regards,
Feri
"Fabio M. Di Nitto"
<fdinitto(a)redhat.com> writes:
The Changelog should be automatically generated in the tarball but it
appears is not. We can fix that and release 1.1 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.
4:03 p.m.
On 2/23/2018 4:44 PM, Ferenc Wágner wrote:
"Fabio M. Di Nitto"
<fdinitto(a)redhat.com> writes:
https://docs.google.com/document/d/1ZNXpyBpzpj0F1RQkpTj2cIeiF6aVaNW-IKeuFH5…
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
On 2/23/2018 3:59 PM, Ferenc Wágner wrote:
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. "Fabio M. Di Nitto"
<fdinitto(a)redhat.com> writes:
The Changelog should be automatically generated in the
tarball but it
appears is not. We can fix that and release 1.1 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.
2493
days inactive
2496
days old
8 comments
3 participants
participants (3)
-
Fabio M. Di Nitto -
Fabio M. Di Nitto -
wferi＠niif.hu