You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by clement escoffier <cl...@gmail.com> on 2013/01/10 14:22:57 UTC

Re: [VOTE] Release of iPOJO Runtime 1.8.6

+1,

Regards,

Clement

2012/12/20 Carsten Ziegeler <cz...@apache.org>

> +1
>
> Carsten
>
> 2012/12/20 Felix Meschberger <fm...@adobe.com>:
> > +1
> >
> > Regards
> > Felix
> >
> > Am 18.12.2012 um 11:37 schrieb Clement Escoffier:
> >
> >> Hi,
> >>
> >> It's time to cut a release of the runtime project (1.8.6).
> >>
> >> This releases contains:
> >> * iPOJO Core 1.8.6
> >> * iPOJO Composite 1.8.6
> >> * iPOJO Annotations 1.8.6
> >> * iPOJO Runtime Project 1.8.6
> >>
> >> Those releases contain several bugs fixes. The changelog is below.
> >>
> >> Staging repository:
> >> https://repository.apache.org/content/repositories/orgapachefelix-043/
> >>
> >> You can use this UNIX script to download the release and verify the
> >> signatures:
> >> http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
> >>
> >> Usage:
> >> sh check_staged_release.sh 043 /tmp/felix-staging
> >>
> >> Please vote to approve this release:
> >>
> >> [ ] +1 Approve the release
> >> [ ] -1 Veto the release (please provide specific comments)
> >>
> >> This vote will be open for 72 hours (at least).
> >>
> >> Regards,
> >>
> >> Clement
> >>
> >> Changelog of the runtime project (1.8.6):
> >>
> >> ** Bug
> >>    * [FELIX-3742] - Implementing class fails to load unless super
> interface's (interface extended by implemented interface) package is
> imported.
> >>    * [FELIX-3789] - Deadlock due to synchronization on INSTANCE_NAME
> >>    * [FELIX-3819] - The export directive of iPOJO is wrong
> >
>
>
>
> --
> Carsten Ziegeler
> cziegeler@apache.org
>

How to distribute a release(was: [VOTE] Release of iPOJO Runtime 1.8.6)

Posted by Felix Meschberger <fm...@adobe.com>.
Hi

this reminds of some important piece of information: If have switched how we provide distributions to http://www.apache.org/dist/felix.

We now use SVN PubSub as described in [1]. Our repo is [2].

The disadvantage (so to speak) is to get the artifacts there and remove the old ones: You might have to checkout the folder [2]. Then you can just do "svn add" and "svn rm" and "svn commit".

The big advantage is, that this becomes active immediately. So except for mirrors, the ASF distro location is immmediately up-to-date.

Also the downloads page is now http://felix.apache.org/downloads.cgi and is easily managed in a simple list file and the Apache CMS:

 * Edit the download list [4]
 * Edit the news page [5]
 * Commit changes
 * Publish site [6]

This immediately (within seconds) updates our site.

This all is about to be described on our Release Management with Nexus page [3].

Sorry for the inconvenience and short notice.

Regards
Felix

[1] http://www.apache.org/dev/release.html#upload-ci
[2] https://dist.apache.org/repos/dist/release/felix
[3] http://felix.apache.org/documentation/development/release-management-nexus.html
[4] https://cms.apache.org/redirect?uri=http%3A//felix.apache.org/downloads.list
[5] https://cms.apache.org/redirect?uri=http%3A//felix.apache.org/news.html
[6] https://cms.apache.org/felix/publish