You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Marshall Schor <ms...@schor.com> on 2013/12/03 21:33:47 UTC
Re: Let's have releases in the future be in a folder structure
hmmm,
Apache projects are not allowed to "publish" things without doing the release
process.
I think the main principle would be:
For addons, do a "release" of each one whenever it seems appropriate, and then,
From time to time - do a bundled milestone release (like Eclipse).
Of course, that's more work :-( ...
-Marshall
On 11/28/2013 9:19 AM, Richard Eckart de Castilho wrote:
> That's what I mean, yes.
>
> -- Richard
>
> On 28.11.2013, at 12:10, Jens Grivolla <j+...@grivolla.net> wrote:
>
>> On 11/28/2013 01:48 PM, Richard Eckart de Castilho wrote:
>>> For the addons, we might consider not having a separate folder for each
>>> addon, and neither do source/binary releases for each release of an individual
>>> addon. Instead, we might consider doing bundled milestone releases (like Eclipse)
>>> every once in a while.
>> Do you mean to publish maven artifacts of individual addons whenever they get updated, but only do releases for download from the UIMA page once in a while? That sounds like a very good option to me...
>>
>> -- Jens
>>
>
Re: Let's have releases in the future be in a folder structure
Posted by Richard Eckart de Castilho <re...@apache.org>.
On 03.12.2013, at 18:52, Marshall Schor <ms...@schor.com> wrote:
> On 12/3/2013 3:37 PM, Richard Eckart de Castilho wrote:
>> Is it documented somewhere what constitutes a release per Apache conventions?
>> I would imagine that a PMC could decide that certain releases are only made
>> on Maven Central and only specific releases are made as binary and source
>> bundles that go through the Apache mirroring/archive system.
>
> There was a discussion somewhere (I'd have to search) that says because Apache's
> mission is to produce source code (not those exact words...) projects need to do
> source releases, and can optionally do binary convenience packages. The source
> code must be published on the Apache distribution system as part of the release.
>
> Because of this, the Maven project, which produces lots of maven plugins that
> are only used via Maven Central, started to publish as part of their release
> process, the sources on the Apache distribution system. See
> http://www.apache.org/dist/maven/plugins/
I see.
>> On 03.12.2013, at 18:33, Marshall Schor <ms...@schor.com> wrote:
>>
>>> hmmm,
>>>
>>> Apache projects are not allowed to "publish" things without doing the release
>>> process.
>>>
>>> I think the main principle would be:
>>>
>>> For addons, do a "release" of each one whenever it seems appropriate, and then,
>>> From time to time - do a bundled milestone release (like Eclipse).
I wonder if the extra work is worth it. The addons appear to be quite diverse. I wonder
if people really use a larger number of them and would benefit from a bundled release.
Anyway, we should do whatever is helping to keep those addons in which people have
active interest spinning.
Regarding the doing it like Eclipse: we might also consider to forego bundled releases
for the addons, and instead do a global UIMA release bundle every once in a while,
including UIMA-AS, DUCC, ruta, etc. all in versions that are compatible with each other.
I think having a reference for users about which versions go well together may be more
important than a ZIP which contains a couple of addons that do not really relate to
each other.
-- Richard
Re: Let's have releases in the future be in a folder structure
Posted by Marshall Schor <ms...@schor.com>.
On 12/3/2013 3:37 PM, Richard Eckart de Castilho wrote:
> Is it documented somewhere what constitutes a release per Apache conventions?
> I would imagine that a PMC could decide that certain releases are only made
> on Maven Central and only specific releases are made as binary and source
> bundles that go through the Apache mirroring/archive system.
There was a discussion somewhere (I'd have to search) that says because Apache's
mission is to produce source code (not those exact words...) projects need to do
source releases, and can optionally do binary convenience packages. The source
code must be published on the Apache distribution system as part of the release.
Because of this, the Maven project, which produces lots of maven plugins that
are only used via Maven Central, started to publish as part of their release
process, the sources on the Apache distribution system. See
http://www.apache.org/dist/maven/plugins/
-Marshall
>
> Doing a release only via a specific channel doesn't mean that we wouldn't have
> to do the usual process for voting etc.
>
> -- Richard
>
> On 03.12.2013, at 18:33, Marshall Schor <ms...@schor.com> wrote:
>
>> hmmm,
>>
>> Apache projects are not allowed to "publish" things without doing the release
>> process.
>>
>> I think the main principle would be:
>>
>> For addons, do a "release" of each one whenever it seems appropriate, and then,
>> From time to time - do a bundled milestone release (like Eclipse).
>>
>> Of course, that's more work :-( ...
>>
>> -Marshall
>>
>> On 11/28/2013 9:19 AM, Richard Eckart de Castilho wrote:
>>> That's what I mean, yes.
>>>
>>> -- Richard
>>>
>>> On 28.11.2013, at 12:10, Jens Grivolla <j+...@grivolla.net> wrote:
>>>
>>>> On 11/28/2013 01:48 PM, Richard Eckart de Castilho wrote:
>>>>> For the addons, we might consider not having a separate folder for each
>>>>> addon, and neither do source/binary releases for each release of an individual
>>>>> addon. Instead, we might consider doing bundled milestone releases (like Eclipse)
>>>>> every once in a while.
>>>> Do you mean to publish maven artifacts of individual addons whenever they get updated, but only do releases for download from the UIMA page once in a while? That sounds like a very good option to me...
>>>>
>>>> -- Jens
>
Re: Let's have releases in the future be in a folder structure
Posted by Richard Eckart de Castilho <re...@apache.org>.
Is it documented somewhere what constitutes a release per Apache conventions?
I would imagine that a PMC could decide that certain releases are only made
on Maven Central and only specific releases are made as binary and source
bundles that go through the Apache mirroring/archive system.
Doing a release only via a specific channel doesn't mean that we wouldn't have
to do the usual process for voting etc.
-- Richard
On 03.12.2013, at 18:33, Marshall Schor <ms...@schor.com> wrote:
> hmmm,
>
> Apache projects are not allowed to "publish" things without doing the release
> process.
>
> I think the main principle would be:
>
> For addons, do a "release" of each one whenever it seems appropriate, and then,
> From time to time - do a bundled milestone release (like Eclipse).
>
> Of course, that's more work :-( ...
>
> -Marshall
>
> On 11/28/2013 9:19 AM, Richard Eckart de Castilho wrote:
>> That's what I mean, yes.
>>
>> -- Richard
>>
>> On 28.11.2013, at 12:10, Jens Grivolla <j+...@grivolla.net> wrote:
>>
>>> On 11/28/2013 01:48 PM, Richard Eckart de Castilho wrote:
>>>> For the addons, we might consider not having a separate folder for each
>>>> addon, and neither do source/binary releases for each release of an individual
>>>> addon. Instead, we might consider doing bundled milestone releases (like Eclipse)
>>>> every once in a while.
>>> Do you mean to publish maven artifacts of individual addons whenever they get updated, but only do releases for download from the UIMA page once in a while? That sounds like a very good option to me...
>>>
>>> -- Jens