Jira is not really helpful for that.
Here's a list extract from the svn log

API
===
    Change parent version to 2.0.0-SNAPSHOT
    More updates to latest version plugin
    [ARIES-1006] Upgrade to the "new" parent pom in proxy modules
    [aries-1006] Point poms back to version 1.0.0 of java5-parent.
    ARIES-1006 : Get Aries building on JDK 7 - fixes for Aries proxy
    ARIES-1006 : Get Aries building on JDK 7 - fixes for Aries proxy
    Update to the release version of the plugin
    ARIES-979: Integrate semantic versioning maven plugin in aries modules

Core
====
[ARIES-1220] Fix required and provided services for ProxyManager
Change parent version to 2.0.0-SNAPSHOT
 Fix proxy-impl test compilation
Aries-1217: ProxySubclassGenerator doesn't compile
[ARIES-1216] Error when creating proxies with an invisible super class in
the hierarchy
 Extend the version range of the slf4j import and set it optional in proxy
Use asm-debug-all for easier debugging
 More updates to latest version plugin
Get Java6 builds working again
Fix proxy integration tests
 [ARIES-1006] Upgrade to the "new" parent pom in proxy modules
Remove debug qualifier
[ARIES-1186] Support Java 8 with ASM 5.0.2 in Aries Proxy
 Update version for checker




2014-07-01 9:25 GMT+02:00 David Bosschaert <david.bosscha...@gmail.com>:

> Hi Guillaume,
>
> I'm kinda missing in this vote (and in the others in the set) what has
> been changed since the last release.
>
> Also, I was wondering whether we should be using the odd-even release
> number scheme that is in use in the Felix project. That ensures that
> version ordering between snapshots and release ordering is always
> right regardless of the context...
>
> Thanks,
>
> David
>
> On 30 June 2014 19:11, Guillaume Nodet <gno...@apache.org> wrote:
> > Second release vote ...
> > This one contains the proxy api and impl.
> > Staging repo at
> >
> https://repository.apache.org/content/repositories/orgapachearies-1003
> >
> > [ ] +1 Release Aries Proxy 1.0.1 and Impl 1.0.3
> > [ ] -1 Do not
> >
> > Cheers,
> > Guillaume Nodet
>

Reply via email to