I cleaned up all the branches a few days ago and had little clue what a large number of them were for, but it doesn't matter. If there was anything of value in it presumably the person who wrote the code would have raised awareness of it and we'd have used it. The way we use branches a lot of them are just to play with an idea in and never come to significant results, which makes it pointless to worry about keeping track of them.
Since I'm the one who's created the last couple branches for ilo and I'm far too lazy to post to -dev on the off chance I take 30 seconds to help someone on IRC by creating a branch for them, I propose we just make the branch commit at least somewhat meaningful and admit that the system is never going to be perfect. On Sep 27, 2010, at 8:12 PM, michael.twofish wrote: > Branches are a great way to test out functionality that might not make > it into trunk, and they also allow non-cabal people to work directly > without submitting patches. Unfortunately, as things are now, branches > get created and usually the only people who know what they're for are > the person who created them and sometimes those who happened to be on > IRC at the time. > > I'd like to propose that when a branch is created, someone should > email -dev with a short announcement. This would provide a link to the > branch, a short description of the goal of the branch, and links to > relevant trac issues. I think this will make it more likely that > multiple people could work on branches together and, more importantly, > more likely that the resulting functionality will get noticed enough > to get merged back into trunk. > > -- > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/habari-dev
smime.p7s
Description: S/MIME cryptographic signature
