You should mention in the comment there that this effects 3.2, 4.0 and master, and you think this should be backported. After it got merged into master, then usually the core team will ask you to create associated PRs. No need to do it up front. ;)
-Prem On Wednesday, August 21, 2013 at 1:03 PM, Simon Coffey wrote: > Hi, > > I've got a bugfix PR[1] on master, which I'd really like (if possible) to > make it into the final 3.2 bugfix release as a backport. > > Is it out of order to open a backport PR for something that hasn't yet been > merged into master? I'm conscious of the heavy existing workload on > maintainers, and don't want to add to it unnecessarily - just also aware that > there's a cutoff for 3.2 bugfixes hoving into view... :-) > > All the best, > Simon > > [1] https://github.com/rails/rails/pull/11636 > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > (mailto:[email protected]). > To post to this group, send email to [email protected] > (mailto:[email protected]). > Visit this group at http://groups.google.com/group/rubyonrails-core. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/groups/opt_out.
