As part of the release process we are supposed to create an announcement
for the users list:
https://felix.apache.org/documentation/development/release-management-nexus.html#_create_an_announcement

I don't recall ever doing this and I don't think others have been doing it
either.  Is this still encouraged / required?

Thanks
Tom

On Thu, Sep 4, 2025 at 3:02 PM Thomas Watson <[email protected]> wrote:

> Hi,
>
>
> The vote has passed with the following result :
>
>  +1 (binding): Thomas Watson, Paul Rütter, Carsten Ziegeler, David 
> Bosschaert, Karl Pauls,
>  +1 (non-binding): Arnoud, Christoph Läubrich
>
> I will copy this release to the Felix dist directory and
> promote the artifacts to the central Maven repository now.
>
>
> Thanks
>
> Tom Watson
>
>
>
> On Wed, Aug 20, 2025 at 12:13 PM Thomas Watson <[email protected]> wrote:
>
>> Hi,
>>
>> We solved the following for SCR 2.2.14
>>
>> ** PRs
>>
>>     * #383 Do not print an error when a wildcard is used in component header
>>     * #359 felix.scr - Fix printing of array of primitive types.
>>     * #438 Enable conditional command registration.
>>     * #437 Use globalContext for commands if configured
>>
>> ** Bug
>>     * [FELIX-6726] One reference can be unset more then once and will cause 
>> IllegalArgumentExceptionin Framework
>>     * [FELIX-6778] Reduce number of re-creation(s) of SCR Component Registry 
>> thread
>>
>> Staging 
>> repository:https://repository.apache.org/content/repositories/orgapachefelix-1530/
>>
>> You can use this UNIX script to download the release and verify the
>> signatures:https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
>>
>> Usage:
>> sh check_staged_release.sh 1530 /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.
>>
>> Thanks
>> Tom
>>
>>

Reply via email to