Hi,
a few changes:
- we don't anymore need the KEYS file at the top of the
https://dist.apache.org/repos/dist/release/directory area. See
https://people.apache.org/keys/
So you should be good using the key in
https://people.apache.org/keys/committer/
- I have created the
Shawn McKinney created FC-328:
-
Summary: Role Constraint validations broken
Key: FC-328
URL: https://issues.apache.org/jira/browse/FC-328
Project: FORTRESS
Issue Type: Bug
Affects Versions:
[
https://issues.apache.org/jira/browse/FC-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney updated FC-328:
--
Description:
Does not properly validate whether a role constraint has been enabled globally.
For
> On Sep 8, 2023, at 12:47 PM, Brian Demers wrote:
>
> I've been working on getting SCIMple in release shape, but I've hit a few
> snags along the way.
> Mostly small things, or process related issues.
> For example, there is an issue with generating the javadoc for the Spring
> module
Hi Brian, Shawn,
the directory/Forest/Ldap API dev guide page are pretty accurate, when
it comes to cut a release.
The steps are:
- do a dry run
- deploy a snapshot
- prepare the release
- perform it
- build the site (and javadoc)
- sign the packages (you'll need a GPG key, and it needs to be
