On Wed, 16 May 2012 23:59:38 +0300 Tom Hacohen <t...@stosb.com> said:
> 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). the point of releases and stability is that regardless if *YOU* care, you have "users" (customers) who care and stability is about supporting them. making bugfix releases with no nasty surprises they can DEPEND on. if you personally care about the bug/widget or not is not really relevant. your USERS will care - some of them will, AND if you care about the project at all you care about users and at least TRY to help them out and make them happy. there are of course limits and there is the other side of being unreasonable, but doing a backport of a fix is far from unreasonable. > 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 the changelog is a small fraction of the size of the svn log. the changelog is for packagers and users to see what did change when they GET THE TARBALL. the changelog is what i use to update NEWS files at release time. scm log is everything. changelog is filtered down entries to the new additions, removals and bug fixes done - any bug fix at all that may have affected someone and their apps/code etc. (fixing a spelling mistakke in a comment, doc, readme etc. isn't going to affect people normally). > what bug trackers and associating bugs with releases are for, not the > changelog. If we plan on adding changelog entries for every small and then the bug tracker is "cluttered with 10000 changes". unlike the changelog you have to wait 5 seconds for each bug report page to come up, as opposed to a quick scan of a text file to see if your annoying bug has been fixed this release or not. > change, we might as well just paste the VCS log there on release (like > some projects do). no - because scm logs contain all the junk in between. > 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. <just before u svn commit the change> svn diff | (cd ~/dev/svn/e/branches/elementary-1.0; patch -p0) that's annoying? you could script it trivially: cat backport.sh #!/bin/sh svn diff | (cd ~/dev/svn/e/branches/$1; patch -p0) so now it's a simple: backport.sh elementary-1.0 reality is that often the changelogs (and patches) don't apply so there is a manual fix anyway and no scm is going to magically fix that for you. this is the cost of stability and doing releases. this is WHY on most large projects there are DEDICATED people who just do the backporting (ie maintaining) of stable releases. so please do this. it's the right and professional thing to do. our tools are just fine > 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 no easier with git. see above. > 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. and then all your serious users run away because you can't be bothered maintaining any stability that they RELY on in their servers/products/devices/apps and they go and find somone else who bothers. if you just want to hack in a bubble then fine, but we are now in a position of needing to maintain stability. if you are uninterested in helping out and instead now making others do your backport for you when it's easier to do yourself at the time (much easier - see above), then perhaps this isn't the project for you? > 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 > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ 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
