: So I guess there is no way of me doing a patch for 3.6.0 since the issue in : JIRA <https://issues.apache.org/jira/browse/SOLR-3574> I reported is not a : bug (but a new feature). Ok. Than, I'll do a patch for the 4.0
As a general rule, features should always be developed against trunk, and then once all the kinks are worked out and test are written, they can be backported -- usually backporting is as easy as an "svn merge" command, so 90% of the time there is no reason to worry about attaching specific patches for each backported branch to jira (unless you really want to, or if you are aware of some specific deviation in the branches that will make the backporting hard) The reason to always start with trunk and work backwards is because that way you never risk getting into a situation where a feature is implimented in version X, but then version X+1 comes out and the feature is now missing. Bug fixes should usualy be developed in the same way, the only differnece is sometimes the bug only affects specific versions, so you start with the newest version the bug is known to affect (ie: maybe because of some refactoring or other improvements a bug only exists in 3.6 and 4.0, but not on trunk) -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
