hi list, i wanted to ask, if it would be possible to have a little CHANGELOG file in side the batman-sources? i think it is very informative for the users, which are not active developer to know whet is changed from one version to the other.
cheers, doc
Hi
did you know that you can always visit: https://dev.open-mesh.net/batman/log/branches/batman-0.2.x/ to get probably exactly what you want?
ciao, axel
On Friday 25 May 2007 13:56, Dragan Noveski wrote:
hi list, i wanted to ask, if it would be possible to have a little CHANGELOG file in side the batman-sources? i think it is very informative for the users, which are not active developer to know whet is changed from one version to the other.
cheers, doc _______________________________________________ B.A.T.M.A.N mailing list B.A.T.M.A.N@open-mesh.net https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n
Axel Neumann wrote:
Hi
did you know that you can always visit: https://dev.open-mesh.net/batman/log/branches/batman-0.2.x/ to get probably exactly what you want?
ciao, axel
most probably i did not !? other ways i would not ask for it. thanks for the advice!
cheers, doc
Hi,
i wanted to ask, if it would be possible to have a little CHANGELOG file in side the batman-sources? i think it is very informative for the users, which are not active developer to know whet is changed from one version to the other.
you are right but developers are lazy people regarding documentation. I already started a CHANGELOG file but somehow I found more interesting things to deal with. ;-) I think we will make an effort for the 0.2 release. May be there is someone who is willing to bother about the continuous maintenance of the file ?
Regards, Marek
PS: What about the Bug / Fixes we issued on your behalf ?
Marek Lindner wrote:
Hi,
i wanted to ask, if it would be possible to have a little CHANGELOG file in side the batman-sources? i think it is very informative for the users, which are not active developer to know whet is changed from one version to the other.
you are right but developers are lazy people regarding documentation. I already started a CHANGELOG file but somehow I found more interesting things to deal with. ;-) I think we will make an effort for the 0.2 release. May be there is someone who is willing to bother about the continuous maintenance of the file ?
hi marek, i see that the rev is updated often, so perhaps it would be very useful to write a changelog file with only a content like: 'if you wanna see changelog, pleas visit: https://dev.open-mesh.net/batman/log/branches/batman-0.2.x/'
as i see the most important changes are listed there, so everyone would know where - nobody would ask for anymore. perhaps!
Regards, Marek
PS: What about the Bug / Fixes we issued on your behalf ?
oh, sorry i was thinking that you are informed already! well since rv360, batman is running (well, flying!) here with 'batmand -d 1 -p 105.131.41.5 -r 1 eth2', plus 'batmand -c -d 2' in another terminal for about 15 hours a day. it stopped working 2 times but it was not a segfault and i was able to restart next moment! as i installed today rv371, it is running as well as 360, i ll see if it will stop sometimes!
cheers, doc
Hi,
hi marek, i see that the rev is updated often, so perhaps it would be very useful to write a changelog file with only a content like: 'if you wanna see changelog, pleas visit: https://dev.open-mesh.net/batman/log/branches/batman-0.2.x/'
as i see the most important changes are listed there, so everyone would know where - nobody would ask for anymore. perhaps!
may be even better: What if the script which generates the packages after each commit would print the commit history into the CHANGELOG file ?
oh, sorry i was thinking that you are informed already!
Unfortunately not. ;-)
well since rv360, batman is running (well, flying!) here with 'batmand -d 1 -p 105.131.41.5 -r 1 eth2', plus 'batmand -c -d 2' in another terminal for about 15 hours a day. it stopped working 2 times but it was not a segfault and i was able to restart next moment! as i installed today rv371, it is running as well as 360, i ll see if it will stop sometimes!
Sounds good. Keep us informed.
Regards, Marek
Marek Lindner wrote:
Hi,
hi marek, i see that the rev is updated often, so perhaps it would be very useful to write a changelog file with only a content like: 'if you wanna see changelog, pleas visit: https://dev.open-mesh.net/batman/log/branches/batman-0.2.x/'
as i see the most important changes are listed there, so everyone would know where - nobody would ask for anymore. perhaps!
may be even better: What if the script which generates the packages after each commit would print the commit history into the CHANGELOG file ?
uff, i am a poor sound engineer, so i really don't have an idea how that should work, but it sounds good to me if it works that way!
oh, sorry i was thinking that you are informed already!
Unfortunately not. ;-)
well since rv360, batman is running (well, flying!) here with 'batmand -d 1 -p 105.131.41.5 -r 1 eth2', plus 'batmand -c -d 2' in another terminal for about 15 hours a day. it stopped working 2 times but it was not a segfault and i was able to restart next moment! as i installed today rv371, it is running as well as 360, i ll see if it will stop sometimes!
Sounds good. Keep us informed.
Regards, Marek _______________________________________________
have rv372 here now and it runs pretty good in the moment!
cheers, doc
Hey,
On Saturday 26 May 2007 15:08, Dragan Noveski wrote:
uff, i am a poor sound engineer, so i really don't have an idea how that should work, but it sounds good to me if it works that way!
Never mind, download a recent batmand-0.2.0-rc2-current_sources.tgz and you'll node the autogenerated CHANGELOG file inside.
regards, axel
b.a.t.m.a.n@lists.open-mesh.org
-
Axel Neumann -
Dragan Noveski -
Marek Lindner