On 16/05/12 22:02, Davide Andreoli wrote: > Changelog? Backport? no? Changelog: fix a stupid bug in a widget no one uses (but my colleague it seems).
Though seriously, changelog: no way I'm adding a changelog entry for that, we are really getting nuts with the changelog, we have 10000 changes like this per release which just clutters the changelog. That's what bug trackers and associating bugs with releases are for, not the changelog. If we plan on adding changelog entries for every small change, we might as well just paste the VCS log there on release (like some projects do). As for the backport. It's annoying to do with svn (and our directory structure), very annoying, also, it's driving me nuts. Again, comparing to other projects: that's why there are "version maintainers", just for backporting. When it comes to scratching my own itches: I couldn't care less about backports, I usually do it, but it's really just too annoying. We just need to find something to do with backporting (which will be a lot easier but still annoying with git) and define guidelines for when to backport (and more importantly who), and when to add changelog entries. It's just too crazy to go on like that. People are motivated about improving EFL, not supporting the debian-afraid-of-updates gang. Just my thoughts. :) -- Tom. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
