[infinispan-issues] [JBoss JIRA] Commented: (ISPN-942) Add an (automatic) validation process to infinispan releases
[
https://issues.jboss.org/browse/ISPN-942?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño commented on ISPN-942:
---------------------------------------
One way to verify this would be to have a 3rd party testsuite run that consumes the maven
artifacts when these are in staging area, however, these testsuites might be geared
towards one version or the other. IOW, I'd imagine that Hibernate 2LC would work with
5.x (it's currently integration 4.2.x), but failures with 5.x might be due to
integration code changes required, rather than the release being wrong.
Add an (automatic) validation process to infinispan releases
-------------------------------------------------------------
Key: ISPN-942
URL: https://issues.jboss.org/browse/ISPN-942
Project: Infinispan
Issue Type: Task
Affects Versions: 4.2.1.CR3
Reporter: Mircea Markus
Assignee: Manik Surtani
Fix For: 4.2.1.FINAL
In order to avoid problems with releases a release validation process should be created.
The following problems were encountered in the past and should be checked by this release
process:
- incorrect XSD (ISPN-934)
- upload problems to SF (e.g. today the release script silently failed to upload the
binaries to SF as they changed their certificate)
- wrong binaries being deployed under the "right" name(e.g. a 4.x release was
performed from trunk and not from the 4.2.x branch)
Any others?
All these cause a lot of community frustration and time to debug and fix.
These can potentially be automated.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira