Hi Fabian. Let me go through those links in detail. I was in charge once of releasing Apache ManifoldCF so I will try to remember how I did it as well. In Stanbol I suppose that the process should be similar
Thanks, Rafa El El vie, 24 jun 2016 a las 11:14, Fabian Christ < christ.fab...@googlemail.com> escribió: > Hi, > > from my perspective there is not much to hand over. The trick is to > generate release bundles, upload them to the Apache Nexus instance and > call a vote. > > Rafa, are you willing to become a release manager for Stanbol? That > would be great! You would need access to https://repository.apache.org > - as this is the staging repository. > > The challenge in Stanbol was the overwhelming number of components > that have to be released. This can be tricky and handling the Maven > Release plugin can be become a pain in itself. If have not used the > toolchain since the last release but in theory it should work as > described here [1,2]. > > For each release you could decide to release each component for itself > or release a big TAR ball that has to be generated somehow and > contains everything to be released. Then we have only one large > artifact to vote on. > > [1] http://stanbol.apache.org/development/release-management.html > [2] http://www.apache.org/dev/release-publishing.html > > Best > Fabian > > 2016-06-16 17:57 GMT+02:00 Rafa Haro <rh...@apache.org>: > > Hi Reto > > > > On Thu, Jun 16, 2016 at 4:47 PM Reto Gmür <r...@apache.org> wrote: > > > >> Hi Rafa > >> > >> There was a delay between the discussion on the list and me committing > >> the changes. The reason is also that some little issues had to be fixed > >> in clerezza so that all of Stanbol works. > >> > >> But the problem is not the change between earlier SNAPSHOT version and > >> the release but the lack of release. Developing against a SNAPSHOT > >> version should be the exception, the whole apache release and licensing > >> process depends on artifacts actually being released if people just rely > >> on the subversion code rather than releases this misses a very important > >> aspect of the Apache way and licensing. > >> > > > > I totally agree with you and, at the end, I was saying exactly the same > in > > my first email. I'm using SNAPSHOT because the only released version I > > could use was 0.12 and I needed to work with 1.X. So yeah, the problem is > > we are not releasing because current trunk was probably ready for a first > > 1.0.0 release. > > > > Apart from that, being aware of that situation, I would have probably > > notified such a change in this mailing list, at least to give us the > chance > > to locally or in a fork tag a version and not force us to adapt our > private > > code. But, of course, the real problem is the lack of releasing since too > > much time ago. > > > > Let's try to fix this situation then, is anyone apart from Fabian aware > > about how the releasing process? > > > > I'm more than happy to learn and help > > > > Cheers, > > Rafa > > > > > >> > >> So the problem is that we're not releasing. When an issue is fixed it > >> should never take so long till the fix is available to the public, that > >> is, till there is a release. > >> > >> Cheers, > >> Reto > >> > >> On Wed, 15 Jun 2016, at 12:32, Rafa Haro wrote: > >> > Hi all, > >> > > >> > We should get back to the releasing discussion as soon as possible. > >> > Yesterday, I had to adapt the code of several custom engines that we > used > >> > for an internal project in my company because I was relying on version > >> > 1.0.0-SNAPSHOT and like a month ago Clerezza version was updated. > This is > >> > not nice, because probably there are more people out there developing > >> > with > >> > 1.0.0-SNAPSHOT artifacts (because those are the only ones that we can > get > >> > using maven if you want to use "version 1.x") which code is not going > now > >> > to compile at all like it happened to me yesterday. > >> > > >> > I'm not saying that the update to the new Clerezza API shouldn't have > >> > been > >> > done and released as SNAPSHOT version, but I would have expected at > least > >> > to announce it here first and to wait until releasing and publish a > first > >> > 1.0.0 version for people that have been working with 1.0.0-SNAPSHOT > prior > >> > to this major change doesn't seen his code affected. > >> > > >> > Anyway, Fabian, could we speed up the handover for the releasing > process? > >> > > >> > By the way, I have updated Clerezza bundlelists dependencies for all > the > >> > launchers, because only the full launchers was updated in the last > commit > >> > > >> > Cheers, > >> > Rafa > >> > > > > -- > Fabian > http://twitter.com/fctwitt >
