Seperate release schedule for transports and stores to core?

[iancooper]

Because the core (Brighter and ServiceActivator) have fewer dependencies, it may make sense to release them on a different schedule to the transports and stores, where there are more frequent updates of the depended upon libraries for those transports i.e. if AWS release a new SNS/SQS SDK update, we may only need to update our transport (which likely won't break tests) and re-release that package not Brighter of ServiceActivator.

This would mean we could ripple matching libs for the latest releases of these downstream whilst keeping core changes to once a quarter, or other frequency that is not burdensome for consumers.

Thoughts? @holytshirt ??