Could the back-porting process be the issue itself? >From what I've seen, the example of mongoid >changelog<https://github.com/mongoid/mongoid/blob/master/CHANGELOG.md>is the >best way to go. The point is simple: you fix the bug on a specific branch ("3.0.x" for instance) and being on that branch put the changes under the "3.0.x" section. That's it. You can even release it if you want to.
Just look at it to catch the idea (in breif: several stable branches (where the actual fixes are made) for independent releases; changelogs are populated independently; from time to time branches are merged to master). Still, mongoid's changelog is specific to a development and release processes. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-core/-/RHnP52ucRAUJ. 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/rubyonrails-core?hl=en.
