Re: [DISCUSS] JIRA components

[Anilkumar Gingade <ag...@pivotal.io>]

Any conclusion on this one...We (our team) are looking at adding missing
components to JIRA tickets.

We can think of adding multiple components (adding sub level), E.g: tools,
jvsd...But having a single component seems to be simple...

In case of "jvsd", "versioning", "system upgrades", have them as separate
components...

Thanks,
-Anil.


On Thu, Feb 25, 2016 at 8:52 AM, Jens Deppe <jd...@pivotal.io> wrote:

> I'm not sure '*tools*' is descriptive enough. What would that cover?
>
> What about *jvsd*?
>
> On Wed, Feb 24, 2016 at 2:21 PM, Anilkumar Gingade <ag...@pivotal.io>
> wrote:
>
> > Do we need to have "versioning or consistency", "PR's" separate; or will
> be
> > part of "region"?
> >
> > And "Pdx", "data" serialization part of "serialization"?
> >
> > AsynQueues, Cache Listeners?
> >
> > -Anil.
> >
> >
> > On Tue, Feb 23, 2016 at 3:36 PM, Anthony Baker <ab...@pivotal.io>
> wrote:
> >
> > > Here are the JIRA components we currently have defined:
> > >
> > > build
> > > client/server
> > > core [*]
> > > docs
> > > extensions
> > > functions
> > > general [*]
> > > hdfs
> > > management [*]
> > > membership
> > > offheap
> > > persistence
> > > querying
> > > serialization
> > > subscriptions [*]
> > > tests
> > > tools
> > > transactions
> > > wan
> > > web-content
> > >
> > >
> > > I would like to remove the components marked with [*] and add more
> > > detailed entries like so:
> > >
> > > build
> > > client queues [renamed from subscriptions]
> > > client/server
> > > compression
> > > configuration
> > > cq
> > > distributed lock service
> > > core
> > > docs
> > > eviction
> > > expiration
> > > functions
> > > gfsh
> > > hibernate
> > > http session (tomcat)
> > > jmx
> > > locator
> > > logging
> > > lucene
> > > membership
> > > memcached
> > > messaging
> > > offheap
> > > persistence
> > > pulse
> > > querying
> > > redis
> > > regions
> > > rest (admin)
> > > rest (dev)
> > > security
> > > serialization
> > > snapshot
> > > statistics
> > > transactions
> > > wan
> > > web-content
> > >
> > >
> > > Thoughts?
> > >
> > > Anthony
> > >
> > >
> > >
> >
>

Re: [DISCUSS] JIRA components

[William Markito <wm...@pivotal.io>]

I've just updated the list of components on JIRA to reflect the list
proposed here which seems to be a good start.

The list can and should evolve of course if something needs to be removed
or added.

Thanks,

On Mon, Feb 29, 2016 at 3:23 PM, Anilkumar Gingade <ag...@pivotal.io>
wrote:

> Any conclusion on this one...We (our team) are looking at adding missing
> components to JIRA tickets.
>
> We can think of adding multiple components (adding sub level), E.g: tools,
> jvsd...But having a single component seems to be simple...
>
> In case of "jvsd", "versioning", "system upgrades", have them as separate
> components...
>
> Thanks,
> -Anil.
>
>
> On Thu, Feb 25, 2016 at 8:52 AM, Jens Deppe <jd...@pivotal.io> wrote:
>
> > I'm not sure '*tools*' is descriptive enough. What would that cover?
> >
> > What about *jvsd*?
> >
> > On Wed, Feb 24, 2016 at 2:21 PM, Anilkumar Gingade <ag...@pivotal.io>
> > wrote:
> >
> > > Do we need to have "versioning or consistency", "PR's" separate; or
> will
> > be
> > > part of "region"?
> > >
> > > And "Pdx", "data" serialization part of "serialization"?
> > >
> > > AsynQueues, Cache Listeners?
> > >
> > > -Anil.
> > >
> > >
> > > On Tue, Feb 23, 2016 at 3:36 PM, Anthony Baker <ab...@pivotal.io>
> > wrote:
> > >
> > > > Here are the JIRA components we currently have defined:
> > > >
> > > > build
> > > > client/server
> > > > core [*]
> > > > docs
> > > > extensions
> > > > functions
> > > > general [*]
> > > > hdfs
> > > > management [*]
> > > > membership
> > > > offheap
> > > > persistence
> > > > querying
> > > > serialization
> > > > subscriptions [*]
> > > > tests
> > > > tools
> > > > transactions
> > > > wan
> > > > web-content
> > > >
> > > >
> > > > I would like to remove the components marked with [*] and add more
> > > > detailed entries like so:
> > > >
> > > > build
> > > > client queues [renamed from subscriptions]
> > > > client/server
> > > > compression
> > > > configuration
> > > > cq
> > > > distributed lock service
> > > > core
> > > > docs
> > > > eviction
> > > > expiration
> > > > functions
> > > > gfsh
> > > > hibernate
> > > > http session (tomcat)
> > > > jmx
> > > > locator
> > > > logging
> > > > lucene
> > > > membership
> > > > memcached
> > > > messaging
> > > > offheap
> > > > persistence
> > > > pulse
> > > > querying
> > > > redis
> > > > regions
> > > > rest (admin)
> > > > rest (dev)
> > > > security
> > > > serialization
> > > > snapshot
> > > > statistics
> > > > transactions
> > > > wan
> > > > web-content
> > > >
> > > >
> > > > Thoughts?
> > > >
> > > > Anthony
> > > >
> > > >
> > > >
> > >
> >
>



-- 

~/William