On Mon, Aug 14, 2017 at 2:11 PM, Stefan Egli <[email protected]> wrote:
> +0
>
> Note that this also releases SLING-6739 for which the original idea was to
> increase the version to 4.3.0 to stress that internally it embeds and
> re-exports event.api now. But technically I don't see a reason why it
> can't be released as 4.2.6 .. just saying. We can adjust fixversion of
> SLING-6739 accordingly too.

Yes, you are absolutely correct. I should have seen that. Sorry I
missed it (I guess I need a vacation).

Thanks for resolving SLING-6739 - as you say, there isn't really a
need for a minor version increase so solving it this way makes the
most sense.

regards,

Karl

> Cheers,
> Stefan
>
> On 10/08/17 11:59, "Karl Pauls" <[email protected]> wrote:
>
>>I would like to call a vote on the following release,
>>
>>Apache Sling Event 4.2.6
>>
>>We solved 2 issue in this release:
>>https://issues.apache.org/jira/projects/SLING/versions/12341306
>>
>>Staging repository:
>>https://repository.apache.org/content/repositories/orgapachesling-1764/
>>
>>You can use this UNIX script to download the release and verify the
>>signatures:
>>http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
>>
>>Usage:
>>sh check_staged_release.sh 1764 /tmp/sling-staging
>>
>>Please vote to approve these releases:
>>
>>  [ ] +1 Approve the releases
>>  [ ]  0 Don't care
>>  [ ] -1 Don't release, because ...
>
>



-- 
Karl Pauls
[email protected]

Reply via email to