Fernando Garcia Bermudez <f...@eecs.berkeley.edu> writes: > Do you know if these changes will trickle to the py3 repo after > merging into master?
I don't know if we have a process in place for that. It depends on how you view the py3 repo: if it's just another feature branch, it shouldn't do any merges from master just for the sake of it, but if it's kind of like "next" or "pu" (proposed updates) in some workflows, it makes sense for it to be occasionally brought up to date (possibly even by rebasing). But it's fine for even feature branches to merge from master, e.g. if there is a feature in master that the branch is going to depend on. -- Jouni K. Seppänen http://www.iki.fi/jks ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
