Re: Maven JIRA Projects - Issue Type

2017-08-20 Thread Stephen Connolly 
B please,

On Sat 19 Aug 2017 at 06:54, Karl Heinz Marbaise  wrote:

> Hi,
>
> so based on the feedback I will go back to INFRA and let them configure
> a separate Configuration type "Maven Issue Type Scheme" which contains
> the issue type "Dependency Upgrade"...
>
> Kind regards
> Karl Heinz Marbaise
>
> On 18/08/17 20:52, Karl Heinz Marbaise wrote:
> > Hi to all,
> >
> > I have realized that in MASSEMBLY it is possible to define an issue Type
> > "Dependency Upgrade" which is very feasible for our projects...
> >
> > So I have asked INFRA[1] if we could have that for our other JIRA
> > projects as wellSo the now we can decide between three options:
> >
> >
> > A) switch your other schemes to match MASSEMBLY - meaning in addition to
> > getting 'Dependency Upgrade' you also get add additional 30+ others you
> > dont use.
> >
> > B) Create a Maven Issue Type Scheme, adding 'Dependency Upgrade' to the
> > default.
> >
> > C) Nothing.
> >
> >
> > So I would vote for option "B" ...The question is what do you think?
> > Which options would you like to use in JIRA ?
> >
> >
> > Kind regards
> > Karl Heinz Marbaise
> >
> > More details in the issue.
> >
> > [1]: https://issues.apache.org/jira/browse/INFRA-14898
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
> --
Sent from my phone

Re: Maven JIRA Projects - Issue Type

2017-08-19 Thread Karl Heinz Marbaise 

Hi,

so based on the feedback I will go back to INFRA and let them configure 
a separate Configuration type "Maven Issue Type Scheme" which contains 
the issue type "Dependency Upgrade"...


Kind regards
Karl Heinz Marbaise

On 18/08/17 20:52, Karl Heinz Marbaise wrote:

Hi to all,

I have realized that in MASSEMBLY it is possible to define an issue Type 
"Dependency Upgrade" which is very feasible for our projects...


So I have asked INFRA[1] if we could have that for our other JIRA 
projects as wellSo the now we can decide between three options:



A) switch your other schemes to match MASSEMBLY - meaning in addition to 
getting 'Dependency Upgrade' you also get add additional 30+ others you 
dont use.


B) Create a Maven Issue Type Scheme, adding 'Dependency Upgrade' to the 
default.


C) Nothing.


So I would vote for option "B" ...The question is what do you think? 
Which options would you like to use in JIRA ?



Kind regards
Karl Heinz Marbaise

More details in the issue.

[1]: https://issues.apache.org/jira/browse/INFRA-14898

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Maven JIRA Projects - Issue Type

2017-08-19 Thread Anders Hammar 
B would be great.

/Anders (mobile)

Den 18 aug. 2017 20:53 skrev "Karl Heinz Marbaise" :

> Hi to all,
>
> I have realized that in MASSEMBLY it is possible to define an issue Type
> "Dependency Upgrade" which is very feasible for our projects...
>
> So I have asked INFRA[1] if we could have that for our other JIRA projects
> as wellSo the now we can decide between three options:
>
>
> A) switch your other schemes to match MASSEMBLY - meaning in addition to
> getting 'Dependency Upgrade' you also get add additional 30+ others you
> dont use.
>
> B) Create a Maven Issue Type Scheme, adding 'Dependency Upgrade' to the
> default.
>
> C) Nothing.
>
>
> So I would vote for option "B" ...The question is what do you think? Which
> options would you like to use in JIRA ?
>
>
> Kind regards
> Karl Heinz Marbaise
>
> More details in the issue.
>
> [1]: https://issues.apache.org/jira/browse/INFRA-14898
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Maven JIRA Projects - Issue Type

2017-08-18 Thread Karl Heinz Marbaise 

Hi,

based on the information I see currently the "default" issue types are 
the following which does not contain "Question" and others...


* Bug
* Improvement
* New Feature
* Task
* Test
* Wish
* Sub-Task

Kind regards
Karl Heinz Marbaise

On 18/08/17 21:14, Michael Osipov wrote:

Am 2017-08-18 um 20:59 schrieb Robert Scholte:

I like the idea of having our own scheme for all projects.
That will also give the option to remove types like "Question"; now 
once used we're always asking them to use other ways to get an answer. 
But it is an option, so it is kind of valid to use it.


Fully support that (B). "Question" is just annoying.

On Fri, 18 Aug 2017 20:52:55 +0200, Karl Heinz Marbaise 
 wrote:



Hi to all,

I have realized that in MASSEMBLY it is possible to define an issue 
Type "Dependency Upgrade" which is very feasible for our projects...


So I have asked INFRA[1] if we could have that for our other JIRA 
projects as wellSo the now we can decide between three options:



A) switch your other schemes to match MASSEMBLY - meaning in addition 
to getting 'Dependency Upgrade' you also get add additional 30+ 
others you dont use.


B) Create a Maven Issue Type Scheme, adding 'Dependency Upgrade' to 
the default.


C) Nothing.


So I would vote for option "B" ...The question is what do you think? 
Which options would you like to use in JIRA ?



Kind regards
Karl Heinz Marbaise

More details in the issue.

[1]: https://issues.apache.org/jira/browse/INFRA-14898

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org





-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org





Mit freundlichem Gruß
Karl-Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl-Heinz MarbaiseUSt.IdNr: DE191347579
Hauptstrasse 177
52146 Würselen   http://www.soebes.de

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Maven JIRA Projects - Issue Type

2017-08-18 Thread Arnaud Héritier 
B too

Le ven. 18 août 2017 à 21:14, Michael Osipov  a écrit :

> Am 2017-08-18 um 20:59 schrieb Robert Scholte:
> > I like the idea of having our own scheme for all projects.
> > That will also give the option to remove types like "Question"; now once
> > used we're always asking them to use other ways to get an answer. But it
> > is an option, so it is kind of valid to use it.
>
> Fully support that (B). "Question" is just annoying.
>
> > On Fri, 18 Aug 2017 20:52:55 +0200, Karl Heinz Marbaise
> >  wrote:
> >
> >> Hi to all,
> >>
> >> I have realized that in MASSEMBLY it is possible to define an issue
> >> Type "Dependency Upgrade" which is very feasible for our projects...
> >>
> >> So I have asked INFRA[1] if we could have that for our other JIRA
> >> projects as wellSo the now we can decide between three options:
> >>
> >>
> >> A) switch your other schemes to match MASSEMBLY - meaning in addition
> >> to getting 'Dependency Upgrade' you also get add additional 30+ others
> >> you dont use.
> >>
> >> B) Create a Maven Issue Type Scheme, adding 'Dependency Upgrade' to
> >> the default.
> >>
> >> C) Nothing.
> >>
> >>
> >> So I would vote for option "B" ...The question is what do you think?
> >> Which options would you like to use in JIRA ?
> >>
> >>
> >> Kind regards
> >> Karl Heinz Marbaise
> >>
> >> More details in the issue.
> >>
> >> [1]: https://issues.apache.org/jira/browse/INFRA-14898
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: dev-h...@maven.apache.org
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
> --
-
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

Re: Maven JIRA Projects - Issue Type

2017-08-18 Thread Michael Osipov 

Am 2017-08-18 um 20:59 schrieb Robert Scholte:

I like the idea of having our own scheme for all projects.
That will also give the option to remove types like "Question"; now once 
used we're always asking them to use other ways to get an answer. But it 
is an option, so it is kind of valid to use it.


Fully support that (B). "Question" is just annoying.

On Fri, 18 Aug 2017 20:52:55 +0200, Karl Heinz Marbaise 
 wrote:



Hi to all,

I have realized that in MASSEMBLY it is possible to define an issue 
Type "Dependency Upgrade" which is very feasible for our projects...


So I have asked INFRA[1] if we could have that for our other JIRA 
projects as wellSo the now we can decide between three options:



A) switch your other schemes to match MASSEMBLY - meaning in addition 
to getting 'Dependency Upgrade' you also get add additional 30+ others 
you dont use.


B) Create a Maven Issue Type Scheme, adding 'Dependency Upgrade' to 
the default.


C) Nothing.


So I would vote for option "B" ...The question is what do you think? 
Which options would you like to use in JIRA ?



Kind regards
Karl Heinz Marbaise

More details in the issue.

[1]: https://issues.apache.org/jira/browse/INFRA-14898

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org





-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Maven JIRA Projects - Issue Type

2017-08-18 Thread Robert Scholte 

I like the idea of having our own scheme for all projects.
That will also give the option to remove types like "Question"; now once  
used we're always asking them to use other ways to get an answer. But it  
is an option, so it is kind of valid to use it.


thanks,
Robert

On Fri, 18 Aug 2017 20:52:55 +0200, Karl Heinz Marbaise  
 wrote:



Hi to all,

I have realized that in MASSEMBLY it is possible to define an issue Type  
"Dependency Upgrade" which is very feasible for our projects...


So I have asked INFRA[1] if we could have that for our other JIRA  
projects as wellSo the now we can decide between three options:



A) switch your other schemes to match MASSEMBLY - meaning in addition to  
getting 'Dependency Upgrade' you also get add additional 30+ others you  
dont use.


B) Create a Maven Issue Type Scheme, adding 'Dependency Upgrade' to the  
default.


C) Nothing.


So I would vote for option "B" ...The question is what do you think?  
Which options would you like to use in JIRA ?



Kind regards
Karl Heinz Marbaise

More details in the issue.

[1]: https://issues.apache.org/jira/browse/INFRA-14898

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Maven JIRA Projects - Issue Type

2017-08-18 Thread Karl Heinz Marbaise 

Hi to all,

I have realized that in MASSEMBLY it is possible to define an issue Type 
"Dependency Upgrade" which is very feasible for our projects...


So I have asked INFRA[1] if we could have that for our other JIRA 
projects as wellSo the now we can decide between three options:



A) switch your other schemes to match MASSEMBLY - meaning in addition to 
getting 'Dependency Upgrade' you also get add additional 30+ others you 
dont use.


B) Create a Maven Issue Type Scheme, adding 'Dependency Upgrade' to the 
default.


C) Nothing.


So I would vote for option "B" ...The question is what do you think? 
Which options would you like to use in JIRA ?



Kind regards
Karl Heinz Marbaise

More details in the issue.

[1]: https://issues.apache.org/jira/browse/INFRA-14898

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org