[jboss-jira] [JBoss JIRA] Resolved: (HIBERNATE-91) Define and document what "supported" and "non-supported" means for dependencies

[Gail Badner (JIRA)]

     [ http://jira.jboss.com/jira/browse/HIBERNATE-91?page=all ]

Gail Badner resolved HIBERNATE-91.
----------------------------------

    Resolution: Won't Fix

> Define and document what "supported" and "non-supported" means for dependencies
> -------------------------------------------------------------------------------
>
>                 Key: HIBERNATE-91
>                 URL: http://jira.jboss.com/jira/browse/HIBERNATE-91
>             Project: Hibernate
>          Issue Type: Sub-task
>            Reporter: Gail Badner
>         Assigned To: Gail Badner
>
> The terms "supported" and "non-supported" need to be defined. Here is a something to start the conversation.
> If a dependency is "supported", Red Hat/JBoss will provide customer support for issues reported on that dependency, but only if the problem is in functionality that Hibernate uses. In addition, Red Hat/JBoss will provide customer support for Hibernate classes that integrate with supported dependencies.
> If a dependency is "non-supported", RedHat/JBoss will not provide any customer support related to that dependency.
> Decisions about which jars are "supported" and which are "non-supported" will be covered in a separate task.
> In general:
> - build-time dependencies are "non-supported"
> - the runtime dependencies that are required for Hibernate to operate will be "supported"
> - the runtime dependencies that are optional (e.g, ehcache, c3p0) will be "non-supported", except for JBoss Cache and dependencies
> The following needs to be done for this task:
> 1) Define "supported" and "non-supported", or other appropriate terms
> 2) Determine if RedHat/JBoss will provide customer support for Hibernate classes that integrate with non-supported dependencies (e.g., classes for integrating with WebSphere transaction manager, or ehcache)
> 3) Decide where the definitions will be documented in the standalone product; possibilities are readme.txt or lib/version.properties

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira