JDG is the product which encompasses both Library and Server and I do
not want to use that name for the community version. Also for bug
tracking the product uses Bugzilla.
The project on GitHub, which unfortunately is still called
infinispan/jdg, should instead be called "Infinispan Server" and it
should have the following characteristics:
* release-synched with the Infinispan library
* eventually become the only way we distribute the server modules in a
better package
* issues tracked in the community Jira
Does that make things clearer ?
Tristan
On 12/07/2012 04:16 PM, Galder Zamarreño wrote:
On Dec 6, 2012, at 1:16 PM, Mircea Markus <mmarkus(a)redhat.com>
wrote:
> On 6 Dec 2012, at 10:07, Tristan Tarrant 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".
> Do we still want to support non-AS based servers? I think we do want to still have
these as well/
^ Sure, community based support, as we support any of the other community features :)
> If so most of the bugs (but the ones having to do with the integration between
ISPN-servers and AS-servers) will be in the "Remote protocols" component, and it
makes sense for them to appear in the default release notes.
> One way or the other, can't we create an .Server release for each library
release? e.g.
> 5.2.0.Beta12
> 5.2.0.Beta12.Server
^ Why do you wanna have different releases?
Guys, the 'Servers' component was for bugs/features affecting the Infinispan
servers.
Whatever JDG does is JDG's bussiness.
Again, what the heck is the point of doing this?
And remember about product discussions and public dev list ;)
>> 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
>> infinispan-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
> Cheers,
> --
> Mircea Markus
> Infinispan lead (
www.infinispan.org)
>
>
>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Galder Zamarreño
galder(a)redhat.com
twitter.com/galderz
Project Lead, Escalante
http://escalante.io
Engineer, Infinispan
http://infinispan.org
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev