[jboss-as7-dev] Master Lockdown (needed for EAP 6.1 Alpha)

[Paul Ferraro]

When do you plan to branch master, so that postponed items (e.g.
singleton deployments, cross-site replication, etc.) can sill be worked
on?

On Thu, 2012-12-06 at 15:33 -0600, Jason Greene wrote:
> Hello everyone,
> 
> We are going to be starting the basis for EAP 6.1 using the master branch, which will freeze on Jan 8. Please notify me immediately if you have unfinished or unstable features currently in master. We need to stabilize, disable, remove, or mark tech preview anything that is incomplete and not on the high-priority feature list below [1]. Also starting today, any pull request introducing a new feature that is not on the priority list will not be merged.
> 
> As an example, patching and ha singleton will not be merged, they will be consumed for 6.2.
> 
> If you have any questions just let me know.
> 
> Thanks!
> 
> [1] High Priority 6.1 Alpha List:
> 
> PRODMGT-196 - Dynamic remoting configuration using InitialContext (in progress)
> PRODMGT-247 - Trusted EJB Security context propagation (in progress)
> PRODMGT-254 - Interceptor support for custom protocol data in ejb invocations (in progress)
> PRODMGT-46  - Centralize Datasource Password Encryption (Done)
> PRODMGT-195 - Expand usage of property substitution in management model (Done)
> JBPAPP-1456 - PCKS11 keystore support (done)
> JBPAPP-923  - Key alias is not managable (Done)
> PRODMGT-200 - Application specific logging configuration (done) 
> AS7-5768    - Module based RARs
> 
> 
> 
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev