Re: [rt-pmc] Juno Retrospective

[Ralf Sternberg <rsternberg@xxxxxxxxxxxxxxxxx>]

I don't know how many RAP users consume the RAP runtime from the
simrel repository - I doubt that this is particularly useful. The RAP
tools come with a target installer that fetches the runtime from our
project's repository.

But I know that many of our users appreciate that we release on a
schedule. So even without contributing our runtime to the simrel
aggregator, I'm sure we'd continue to synchronize our releases with
the release train.

We notice that more and more users are interested in using RAP outside
of Eclipse, running on Felix and Apache Karaf. Those guys live in a
Maven world, they want a mvn: URL to get the bits from. That's why we
started to publish some core parts of RAP on Maven. We had some
struggle with the gap between both worlds, such as version numbers
that are handled differently on Maven etc. A common infrastructure for
publishing to Maven would be a benefit for us, automated or not.

Also finding out how to run eclipse.core bundles on Felix caused us
some headache and unnecessary work. Even though that was just because
of our lack of knowledge, I guess that others will also have a hard
time finding out that in order to run eclipse.core.databinding on
Felix, they will need certain bundles from equinox [1]. I think that
cleaning up dependencies and supporting non-Equinox users better is
more important for RT to become more popular than the release train.

Regards, Ralf

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=388319


On Wed, Sep 5, 2012 at 2:18 PM, Markus Knauer <mknauer@xxxxxxxxxxxxxxxxx> wrote:
> In RAP we started with Indigo last year to publish some of our (unmodified)
> bundles from Maven Central. Our build is based on Tycho, but it is still a
> very time consuming process to contribute our artifacts to a Maven
> repository. From our perspective it is the opposite: We are very interested
> in ways to make it easier (automate) the process of contributing our RAP
> bundles to Maven Central.
>
> Regards, Markus
>
>
> On Wed, Sep 5, 2012 at 1:59 PM, Jesse McConnell <jesse.mcconnell@xxxxxxxxx>
> wrote:
>>
>> > Also, what could be done (blue-sky thinking) to get you (or keep you) on
>> > the
>> > train? I ask this in a completely hypothetically, and I'm not going to
>> > force
>> > you to join based on your response :-).  But what could the train do for
>> > you? For example, if the train resulted in a automatic delivery of your
>> > contribution to maven central, would this help?  If the train provided
>> > 'release engineering resources', would this help?
>>
>> I am interested with what people come up with, as it stands we
>> reconsume our own artifacts from central to build out our signed p2
>> repository so automatic contribution to central would be counter
>> productive for us.
>>
>> Personally I would like to see information from the release repository
>> on actual usage of the bundles inside, from our perspective it is this
>> weirdly versioned and organized ball of string in a black box.  It is
>> impossible for us to know if anyone out there is actually consuming
>> jetty from the release repo aside from a post on our users list from
>> time to time.  With maven central we can get download statistics on a
>> per artifact (and version) basis which helps us gauge the usage of
>> particular point releases of jetty over time.  Release repositories
>> (and p2 in general) have no concept of incremental point releases nor
>> does it give us any view into actual usage that we are aware of.
>>
>> cheers,
>> jesse
>> _______________________________________________
>> rt-pmc mailing list
>> rt-pmc@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/rt-pmc
>
>
>
>
>
> _______________________________________________
> rt-pmc mailing list
> rt-pmc@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/rt-pmc
>