On Dec 6, 2012, at 11:28 AM, Sanne Grinovero <[email protected]> wrote:
> If the release dates / versions won't match I would suggest having a > different JIRA project. ^ +1 I don't see why JDG issues should be entering the ISPN jira project. Issues that affect JDG are being tagged already. > But I think it would be more sensible to have them released at the > same time, with the same build script: I'm all for automating it. > Are there strong reasons to keep the release times (and process) independent? Well, it's project vs product, different build systems…etc and I'm pretty confident the release schedule isn't the same. @Tristan, care to explain better what you're trying to achieve here? > > Sanne > > On 6 December 2012 10:07, Tristan Tarrant <[email protected]> wrote: >> Hi all, >> >> I finally went ahead and created the "Server" component on Jira to hold >> all issues related to the AS-based Infinispan Server (aka JDG server). >> I have renamed the previous "Servers" component to a more appropriate >> "Remote Protocols". >> >> A note about versions: Server versions will be aligned with Library >> versions, but because of the nature of how the server is built and its >> dependency on an Infinispan library release, a Server release will >> happen asynchronously (i.e. a couple of days later). Also we may not >> want Server issues in the Library release notes. How should we handle this ? >> >> Tristan >> _______________________________________________ >> infinispan-dev mailing list >> [email protected] >> https://lists.jboss.org/mailman/listinfo/infinispan-dev > _______________________________________________ > infinispan-dev mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/infinispan-dev -- Galder Zamarreño [email protected] twitter.com/galderz Project Lead, Escalante http://escalante.io Engineer, Infinispan http://infinispan.org _______________________________________________ infinispan-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/infinispan-dev
