Looks like a bug. Is there a test case for that? I thought I had a test for most edges of the report gen, but the reports could probably do with some more love. It will probably be a couple of weeks before I give v-m-p some more attention, so do not feel ignored if your patch(es) sit there for a few weeks... ;-)
On Wednesday, 18 April 2012, Nicky Ramone wrote: > Hello. > > I'm trying to completely understand how the plugin works before submitting > a patch, but one case baffles me. I want to be sure it's not a bug. > Suppose I'm currently using version 1.0.0 of some dependency. > In the repository, the following versions exist: 1.0.1-alpha1, 1.0.1, > 1.0.2, 1.1.0-beta-2, 1.1.0, 1.1.1 > > The report shows this: > *1.0.1-alpha1* *Next Version* > *1.0.1* *Next Incremental* > 1.0.2 > *1.1.0-beta-2* *Latest Incremental* > *1.1.0* *Next Minor* > *1.1.1* *Latest Minor* > * > * > * > * > Why is 1.1.0-beta-2 considered as the latest incremental? Shouldn't 1.0.2 > be the latest incremental ? > Thanks in advance. > > Regards. >
