On 18.02.2011, at 05:43, Jeremy Mikola wrote: > Perhaps I'm biased in that the first thought that came to mind was the weekly > Symfony blog posts, which summarize commits. Additionally, fabpot/master is > moving at a very quick pace recently, and already I've had trouble locating > the appropriate commits that document how to upgrade in light of BC-breakage. > > Also, when drafting my original email, > https://github.com/fabpot/symfony/pull/510 was fresh on my mind. Not > criticizing the the work within, but I think a significant number of those > two dozen commits will become obsolete in light of the final, upcoming > commits. And that's not to say these old commits represent broken code - > it's just an early step of the development process. The full chain of > commits no doubt presents a history of the development process (and things > that were investigated), but a vital part of that history is in the > conversation around those commits (IRC, pull request comments, etc) which > will be disconnected from the commits should they land in fabpot/master. I'm > not convinced they would provide the same value in the core repository.
What I think would be the better solution if github would make it possible to see the originating pull requests in the history. That way we would get the finely grained real history, but could also easily see logical units. At work we use the convention of always prefixing commits to feature branches with the ticket number but I guess we do not really have that, but maybe we could just write a script that would prefix the pull id before pushing it to the main branch. Or we could lobby github to do some magic to solve this for us. regards, Lukas Kahwe Smith [email protected] -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. 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/symfony-devs?hl=en
