Hi Andreas, The patches in JIRA are just proposals and are applied to trunk only after they are reviewed by committers. The review process sometimes takes a long time since it is done at spare time of committers.
DIGY -----Original Message----- From: Andreas Mummenhoff [mailto:an...@online.de] Sent: Thursday, December 18, 2008 9:06 PM To: lucene-net-dev@incubator.apache.org Subject: AW: [jira] Commented: (LUCENENET-164) upgrade from version 2.3.1. to 2.3.2 Hello Digy, why nobody applies this patches to the current SVN trunk? People just downloading the trunk and not knowing about jira don't get the "best" version available? Why? greetings, Andreas > -----Ursprüngliche Nachricht----- > Von: Digy (JIRA) [mailto:j...@apache.org] > Gesendet: Donnerstag, 18. Dezember 2008 18:44 > An: lucene-net-dev@incubator.apache.org > Betreff: [jira] Commented: (LUCENENET-164) upgrade from > version 2.3.1. to 2.3.2 > > > [ > https://issues.apache.org/jira/browse/LUCENENET-164?page=com.a tlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId =12657827#action_12657827 ] > > Digy commented on LUCENENET-164: > -------------------------------- > > I forgot to say. All Nunit tests pass. > > DIGY. > > > upgrade from version 2.3.1. to 2.3.2 > > ------------------------------------ > > > > Key: LUCENENET-164 > > URL: > https://issues.apache.org/jira/browse/LUCENENET-164 > > Project: Lucene.Net > > Issue Type: Improvement > > Reporter: Doug Sale > > Attachments: 2.3.2-Candidate.patch, LUCENENET-106 Patch for > > v2.3.2.patch, TestIndexModifier.patch > > > > Original Estimate: 0h > > Remaining Estimate: 0h > > > > This issue is a placeholder for attaching a comprehensive > patch upgrading the SVN HEAD of Lucene.Net from 2.3.1 > candidate to 2.3.2 candidate. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. >
