[RESULT] [VOTE] Apache Syncope 3.0.0
Hi all, after 72 hours, the vote for Syncope 3.0.0 [1] *passes* with 5 PMC + 2 non-PMC votes. +1 (PMC / binding) * Fabio Martelli * Andrea Patricelli * Jean-Baptiste Onofré * Marco Di Sabatino * Francesco Chicchiriccò +1 (non binding) * Samuel Garofalo * Lorenzo Di Cola 0 -1 Thanks to everyone participating. I will now copy this release to Syncope' dist directory, promote the artifacts to the central Maven repository and publish to DockerHub. Best regards. [1] https://lists.apache.org/thread/02s3op8x83vmcsd282c33zktcsd8qcwc -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[ANN] Apache Syncope 3.0.0
The Apache Syncope team is pleased to announce the release of Syncope 3.0.0 Apache Syncope is an Open Source system for managing digital identities in enterprise environments, implemented in Java EE technology . Syncope 3.0 Maggiore is now a full-fledged IAM system covering provisioning, reconciliation and reporting needs (as with earlier releases), access management and API management. The release will be available within 24h from: https://syncope.apache.org/downloads Read the full change log available here: https://s.apache.org/syncope300 We welcome your help and feedback. For more information on how to report problems, and to get involved, visit the project website at http://syncope.apache.org/ The Apache Syncope Team
[GitHub] [syncope] mmoayyed merged pull request #390: SYNCOPE-1709: Persist Jobs' current status in the database to support multi-node deployments
mmoayyed merged PR #390: URL: https://github.com/apache/syncope/pull/390 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@syncope.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (SYNCOPE-1709) Persist Jobs' current status in the database to support multi-node deployments
[ https://issues.apache.org/jira/browse/SYNCOPE-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17633910#comment-17633910 ] ASF subversion and git services commented on SYNCOPE-1709: -- Commit f1cd7ccec1382a696d9e09b3454a227de9f8 in syncope's branch refs/heads/master from Misagh Moayyed [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=f1cd7ccec1 ] SYNCOPE-1709: Persist Jobs' current status in the database to support multi-node deployments (#390) Co-authored-by: Francesco Chicchiriccò > Persist Jobs' current status in the database to support multi-node > deployments > --- > > Key: SYNCOPE-1709 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1709 > Project: Syncope > Issue Type: Improvement >Affects Versions: 2.1.12, 3.0.0-M2 >Reporter: Misagh Moayyed >Assignee: Misagh Moayyed >Priority: Major > Fix For: 2.1.13, 3.0.1 > > > When jobs, particularly (long-running) reports, are scheduled/asked to run > and there are multiple Syncope core nodes available in the cluster, the > current method of obtaining the job status via Spring and Quartz fails to > report back the status accurately, specially when the job bean is scheduled > on one node and the status check query is performed on another. > To support this scenario, job status details would be persisted in the > backend database in a new table, and the job engine would be responsible to > add/update/delete details in this table. Status query checks would then look > into this table to report back current status instead of obtaining the status > from the Spring bean responsible for execution. > it was discussed that the initial changeset would go into master and be > targeted to Syncope v3, and then may be backported to 2.x pending feasibility > and complication. -- This message was sent by Atlassian Jira (v8.20.10#820010)
