Jena Permissions 4.0 / changelog?

[Claude Warren <cl...@xenei.com>]

I have completed the initial coding of the Permissions to add the HardError
flag (so that the union code will work without a strange
SecurityEvaluator.  But I want to note the addition of the flag as it
changes the old default operation.    I don't find a changelog in our
codebase.  Are there any recommendation for how to note this?  Also, any
instructions for releasing a component after the main code?

Claude

-- 
I like: Like Like - The likeliest place on the web
<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren

Re: Jena Permissions 4.0 / changelog?

[Andy Seaborne <an...@apache.org>]

Claude - how's the code going?
Would doing Jena 4.1.0 early be of help?

(I'd like to know we can get 3 people if we do a release - you'd be able 
to participate in the vote?)

     Andy


On 15/04/2021 07:24, Claude Warren wrote:
> I have completed the initial coding of the Permissions to add the HardError
> flag (so that the union code will work without a strange
> SecurityEvaluator.  But I want to note the addition of the flag as it
> changes the old default operation.    I don't find a changelog in our
> codebase.  Are there any recommendation for how to note this?  Also, any
> instructions for releasing a component after the main code?
> 
> Claude
> 

Re: Jena Permissions 4.0 / changelog?

[Andy Seaborne <an...@apache.org>]

On 15/04/2021 07:24, Claude Warren wrote:
> I have completed the initial coding of the Permissions to add the HardError
> flag (so that the union code will work without a strange
> SecurityEvaluator.  But I want to note the addition of the flag as it
> changes the old default operation.    I don't find a changelog in our
> codebase.

The details of a release are in JIRA

https://s.apache.org/jena-4.0.0-jira

and this is in the [ANN] message.

I write the email summary to pick out the most important points (and 
also see the [VOTE] message).

>  Are there any recommendation for how to note this?  Also, any
> instructions for releasing a component after the main code?

That brings back memories!

When Jena joined Apache, we initially were going to have module 
granularity releases.  You can even see the evidence in some early 
version numbering.

Whole system releases have been the norm and it avoids the obvious 
version clash issues that can arise.

It is the same amount of work to do a whole system release.

We don't have a way to number individual modules except as a fourth 
digit but that would not be semantic versioning for this change.

     Andy


https://cwiki.apache.org/confluence/display/JENA/Release+Process

> 
> Claude
>