[aerogear-dev] One JIRA instance to rule them all? (was Re: AG JS JIRA)

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

[aerogear-dev] One JIRA instance to rule them all? (was Re: AG JS JIRA)

Matthias Wessendorf
That brings me to something .... :-)


using this approach,e.g 
* android-oauth-3.0.0
* swift-sender-1.0.0
* ios-swift-push 3.0.0

we could go back and just use one JIRA.

That's perhaps less confusion for our users :-) 

They just enter bugs/issues and we are responsible for the actual 'triage' (e.g. set correct components and versions)

:-) 


On Thu, Jul 16, 2015 at 11:01 AM, Matthias Wessendorf <[hidden email]> wrote:
well... the use of components makes it easy - and for versions we could even do something like, for instance in AGJS

node-1.2.0
store-0.7.0

etc



On Thu, Jul 16, 2015 at 10:42 AM, Lukáš Fryč <[hidden email]> wrote:
I know there already  is strong agreement, but my $0.02:

I'm not convinced about AGJS and connection with server-side libraries.


I feel like AGIOS, AGDROID, AGCORDOVA, AGJS are trackers for client-side libs,

AGPUSH, AGSYNC, are trackes for server-side technologies,


consider this use case: if we build eventually a new server-side Swift node-sender library, we won't track it under AGIOS because Swift comes from iOS land.

On Thu, Jul 16, 2015 at 8:42 AM, Matthias Wessendorf <[hidden email]> wrote:
word up👍


On Thursday, July 16, 2015, Daniel Bevenius <[hidden email]> wrote:
+1 Sounds good

On 15 July 2015 at 22:52, Daniel Passos <[hidden email]> wrote:
+1

On Wed, Jul 15, 2015 at 4:21 PM, Bruno Oliveira <[hidden email]> wrote:
+1 makes more sense

On Wed, Jul 15, 2015 at 3:29 PM, Luke Holmquist <[hidden email]> wrote:
Hello all,

we've decided that it would probably be a good idea to move JIRA's related to the node-sender to the AG-JS JIRA instead of having them on the AGUSH JIRA.

i think this makes a bit more sense since this a javascript component.

I've started to move open JIRA's over.  i think i'll probably just leave the existing JIRA's where they are, unless someone feels strongly.


I've also started to create some "component" versions similar to the other projects.

the main JS lib will still be just numbers, like 2.3.0,  and for the node-sender we will now have node-sender-0.8.0, for example


-Luke

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--

-- 
"The measure of a man is what he does with power" - Plato
-
@abstractj
-
Volenti Nihil Difficile

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--
-- Passos

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--
Sent from Gmail Mobile

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--



--

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev
Reply | Threaded
Open this post in threaded view
|

Re: [aerogear-dev] One JIRA instance to rule them all? (was Re: AG JS JIRA)

Lukas Fryc
Pros: Indeed that is super-simple for users,

Cons: it is a bit harder to read or use other JIRA  features like roadmap or agile.

On Thu, Jul 16, 2015 at 11:03 AM, Matthias Wessendorf <[hidden email]> wrote:
That brings me to something .... :-)


using this approach,e.g 
* android-oauth-3.0.0
* swift-sender-1.0.0
* ios-swift-push 3.0.0

we could go back and just use one JIRA.

That's perhaps less confusion for our users :-) 

They just enter bugs/issues and we are responsible for the actual 'triage' (e.g. set correct components and versions)

:-) 


On Thu, Jul 16, 2015 at 11:01 AM, Matthias Wessendorf <[hidden email]> wrote:
well... the use of components makes it easy - and for versions we could even do something like, for instance in AGJS

node-1.2.0
store-0.7.0

etc



On Thu, Jul 16, 2015 at 10:42 AM, Lukáš Fryč <[hidden email]> wrote:
I know there already  is strong agreement, but my $0.02:

I'm not convinced about AGJS and connection with server-side libraries.


I feel like AGIOS, AGDROID, AGCORDOVA, AGJS are trackers for client-side libs,

AGPUSH, AGSYNC, are trackes for server-side technologies,


consider this use case: if we build eventually a new server-side Swift node-sender library, we won't track it under AGIOS because Swift comes from iOS land.

On Thu, Jul 16, 2015 at 8:42 AM, Matthias Wessendorf <[hidden email]> wrote:
word up👍


On Thursday, July 16, 2015, Daniel Bevenius <[hidden email]> wrote:
+1 Sounds good

On 15 July 2015 at 22:52, Daniel Passos <[hidden email]> wrote:
+1

On Wed, Jul 15, 2015 at 4:21 PM, Bruno Oliveira <[hidden email]> wrote:
+1 makes more sense

On Wed, Jul 15, 2015 at 3:29 PM, Luke Holmquist <[hidden email]> wrote:
Hello all,

we've decided that it would probably be a good idea to move JIRA's related to the node-sender to the AG-JS JIRA instead of having them on the AGUSH JIRA.

i think this makes a bit more sense since this a javascript component.

I've started to move open JIRA's over.  i think i'll probably just leave the existing JIRA's where they are, unless someone feels strongly.


I've also started to create some "component" versions similar to the other projects.

the main JS lib will still be just numbers, like 2.3.0,  and for the node-sender we will now have node-sender-0.8.0, for example


-Luke

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--

-- 
"The measure of a man is what he does with power" - Plato
-
@abstractj
-
Volenti Nihil Difficile

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--
-- Passos

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--
Sent from Gmail Mobile

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--



--

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev
Reply | Threaded
Open this post in threaded view
|

Re: [aerogear-dev] One JIRA instance to rule them all? (was Re: AG JS JIRA)

Matthias Wessendorf
roadmaps is slightly harder to read - because a bunch of different versions are there. 
BUT! it shows activity better :) 

On Thu, Jul 16, 2015 at 11:20 AM, Lukáš Fryč <[hidden email]> wrote:
Pros: Indeed that is super-simple for users,

Cons: it is a bit harder to read or use other JIRA  features like roadmap or agile.

On Thu, Jul 16, 2015 at 11:03 AM, Matthias Wessendorf <[hidden email]> wrote:
That brings me to something .... :-)


using this approach,e.g 
* android-oauth-3.0.0
* swift-sender-1.0.0
* ios-swift-push 3.0.0

we could go back and just use one JIRA.

That's perhaps less confusion for our users :-) 

They just enter bugs/issues and we are responsible for the actual 'triage' (e.g. set correct components and versions)

:-) 


On Thu, Jul 16, 2015 at 11:01 AM, Matthias Wessendorf <[hidden email]> wrote:
well... the use of components makes it easy - and for versions we could even do something like, for instance in AGJS

node-1.2.0
store-0.7.0

etc



On Thu, Jul 16, 2015 at 10:42 AM, Lukáš Fryč <[hidden email]> wrote:
I know there already  is strong agreement, but my $0.02:

I'm not convinced about AGJS and connection with server-side libraries.


I feel like AGIOS, AGDROID, AGCORDOVA, AGJS are trackers for client-side libs,

AGPUSH, AGSYNC, are trackes for server-side technologies,


consider this use case: if we build eventually a new server-side Swift node-sender library, we won't track it under AGIOS because Swift comes from iOS land.

On Thu, Jul 16, 2015 at 8:42 AM, Matthias Wessendorf <[hidden email]> wrote:
word up👍


On Thursday, July 16, 2015, Daniel Bevenius <[hidden email]> wrote:
+1 Sounds good

On 15 July 2015 at 22:52, Daniel Passos <[hidden email]> wrote:
+1

On Wed, Jul 15, 2015 at 4:21 PM, Bruno Oliveira <[hidden email]> wrote:
+1 makes more sense

On Wed, Jul 15, 2015 at 3:29 PM, Luke Holmquist <[hidden email]> wrote:
Hello all,

we've decided that it would probably be a good idea to move JIRA's related to the node-sender to the AG-JS JIRA instead of having them on the AGUSH JIRA.

i think this makes a bit more sense since this a javascript component.

I've started to move open JIRA's over.  i think i'll probably just leave the existing JIRA's where they are, unless someone feels strongly.


I've also started to create some "component" versions similar to the other projects.

the main JS lib will still be just numbers, like 2.3.0,  and for the node-sender we will now have node-sender-0.8.0, for example


-Luke

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--

-- 
"The measure of a man is what he does with power" - Plato
-
@abstractj
-
Volenti Nihil Difficile

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--
-- Passos

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--
Sent from Gmail Mobile

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--



--

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev
Reply | Threaded
Open this post in threaded view
|

Re: [aerogear-dev] One JIRA instance to rule them all? (was Re: AG JS JIRA)

Bruno Oliveira
In reply to this post by Matthias Wessendorf
Do we have any complaints about our current Jira instances? Maybe I missed something.

Nothing against moving all the Jiras to a single instance. But I think that just moving without a rock solid plan, will turn this into a mess.

On Thu, Jul 16, 2015 at 6:03 AM, Matthias Wessendorf <[hidden email]> wrote:
That brings me to something .... :-)


using this approach,e.g 
* android-oauth-3.0.0
* swift-sender-1.0.0
* ios-swift-push 3.0.0

we could go back and just use one JIRA.

That's perhaps less confusion for our users :-) 

They just enter bugs/issues and we are responsible for the actual 'triage' (e.g. set correct components and versions)

:-) 


On Thu, Jul 16, 2015 at 11:01 AM, Matthias Wessendorf <[hidden email]> wrote:
well... the use of components makes it easy - and for versions we could even do something like, for instance in AGJS

node-1.2.0
store-0.7.0

etc



On Thu, Jul 16, 2015 at 10:42 AM, Lukáš Fryč <[hidden email]> wrote:
I know there already  is strong agreement, but my $0.02:

I'm not convinced about AGJS and connection with server-side libraries.


I feel like AGIOS, AGDROID, AGCORDOVA, AGJS are trackers for client-side libs,

AGPUSH, AGSYNC, are trackes for server-side technologies,


consider this use case: if we build eventually a new server-side Swift node-sender library, we won't track it under AGIOS because Swift comes from iOS land.

On Thu, Jul 16, 2015 at 8:42 AM, Matthias Wessendorf <[hidden email]> wrote:
word up👍


On Thursday, July 16, 2015, Daniel Bevenius <[hidden email]> wrote:
+1 Sounds good

On 15 July 2015 at 22:52, Daniel Passos <[hidden email]> wrote:
+1

On Wed, Jul 15, 2015 at 4:21 PM, Bruno Oliveira <[hidden email]> wrote:
+1 makes more sense

On Wed, Jul 15, 2015 at 3:29 PM, Luke Holmquist <[hidden email]> wrote:
Hello all,

we've decided that it would probably be a good idea to move JIRA's related to the node-sender to the AG-JS JIRA instead of having them on the AGUSH JIRA.

i think this makes a bit more sense since this a javascript component.

I've started to move open JIRA's over.  i think i'll probably just leave the existing JIRA's where they are, unless someone feels strongly.


I've also started to create some "component" versions similar to the other projects.

the main JS lib will still be just numbers, like 2.3.0,  and for the node-sender we will now have node-sender-0.8.0, for example


-Luke

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--

-- 
"The measure of a man is what he does with power" - Plato
-
@abstractj
-
Volenti Nihil Difficile

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--
-- Passos

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--
Sent from Gmail Mobile

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--



--

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--

-- 
"The measure of a man is what he does with power" - Plato
-
@abstractj
-
Volenti Nihil Difficile

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev
Reply | Threaded
Open this post in threaded view
|

Re: [aerogear-dev] One JIRA instance to rule them all? (was Re: AG JS JIRA)

Luke Holmquist


On Thu, Jul 16, 2015 at 1:29 PM, Bruno Oliveira <[hidden email]> wrote:
Do we have any complaints about our current Jira instances? Maybe I missed something.

Nothing against moving all the Jiras to a single instance.
Isn't this what we started with,  i'm minus infinity on going back there 
 
But I think that just moving without a rock solid plan, will turn this into a mess.

On Thu, Jul 16, 2015 at 6:03 AM, Matthias Wessendorf <[hidden email]> wrote:
That brings me to something .... :-)


using this approach,e.g 
* android-oauth-3.0.0
* swift-sender-1.0.0
* ios-swift-push 3.0.0

we could go back and just use one JIRA.

That's perhaps less confusion for our users :-) 

They just enter bugs/issues and we are responsible for the actual 'triage' (e.g. set correct components and versions)

:-) 


On Thu, Jul 16, 2015 at 11:01 AM, Matthias Wessendorf <[hidden email]> wrote:
well... the use of components makes it easy - and for versions we could even do something like, for instance in AGJS

node-1.2.0
store-0.7.0

etc



On Thu, Jul 16, 2015 at 10:42 AM, Lukáš Fryč <[hidden email]> wrote:
I know there already  is strong agreement, but my $0.02:

I'm not convinced about AGJS and connection with server-side libraries.


I feel like AGIOS, AGDROID, AGCORDOVA, AGJS are trackers for client-side libs,

AGPUSH, AGSYNC, are trackes for server-side technologies,


consider this use case: if we build eventually a new server-side Swift node-sender library, we won't track it under AGIOS because Swift comes from iOS land.

On Thu, Jul 16, 2015 at 8:42 AM, Matthias Wessendorf <[hidden email]> wrote:
word up👍


On Thursday, July 16, 2015, Daniel Bevenius <[hidden email]> wrote:
+1 Sounds good

On 15 July 2015 at 22:52, Daniel Passos <[hidden email]> wrote:
+1

On Wed, Jul 15, 2015 at 4:21 PM, Bruno Oliveira <[hidden email]> wrote:
+1 makes more sense

On Wed, Jul 15, 2015 at 3:29 PM, Luke Holmquist <[hidden email]> wrote:
Hello all,

we've decided that it would probably be a good idea to move JIRA's related to the node-sender to the AG-JS JIRA instead of having them on the AGUSH JIRA.

i think this makes a bit more sense since this a javascript component.

I've started to move open JIRA's over.  i think i'll probably just leave the existing JIRA's where they are, unless someone feels strongly.


I've also started to create some "component" versions similar to the other projects.

the main JS lib will still be just numbers, like 2.3.0,  and for the node-sender we will now have node-sender-0.8.0, for example


-Luke

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--

-- 
"The measure of a man is what he does with power" - Plato
-
@abstractj
-
Volenti Nihil Difficile

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--
-- Passos

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--
Sent from Gmail Mobile

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--



--

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--

-- 
"The measure of a man is what he does with power" - Plato
-
@abstractj
-
Volenti Nihil Difficile

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev
Reply | Threaded
Open this post in threaded view
|

Re: [aerogear-dev] One JIRA instance to rule them all? (was Re: AG JS JIRA)

Matthias Wessendorf
In reply to this post by Bruno Oliveira
no, it was just a thought - not more ;-)

On Thu, Jul 16, 2015 at 7:29 PM, Bruno Oliveira <[hidden email]> wrote:
Do we have any complaints about our current Jira instances? Maybe I missed something.

Nothing against moving all the Jiras to a single instance. But I think that just moving without a rock solid plan, will turn this into a mess.

On Thu, Jul 16, 2015 at 6:03 AM, Matthias Wessendorf <[hidden email]> wrote:
That brings me to something .... :-)


using this approach,e.g 
* android-oauth-3.0.0
* swift-sender-1.0.0
* ios-swift-push 3.0.0

we could go back and just use one JIRA.

That's perhaps less confusion for our users :-) 

They just enter bugs/issues and we are responsible for the actual 'triage' (e.g. set correct components and versions)

:-) 


On Thu, Jul 16, 2015 at 11:01 AM, Matthias Wessendorf <[hidden email]> wrote:
well... the use of components makes it easy - and for versions we could even do something like, for instance in AGJS

node-1.2.0
store-0.7.0

etc



On Thu, Jul 16, 2015 at 10:42 AM, Lukáš Fryč <[hidden email]> wrote:
I know there already  is strong agreement, but my $0.02:

I'm not convinced about AGJS and connection with server-side libraries.


I feel like AGIOS, AGDROID, AGCORDOVA, AGJS are trackers for client-side libs,

AGPUSH, AGSYNC, are trackes for server-side technologies,


consider this use case: if we build eventually a new server-side Swift node-sender library, we won't track it under AGIOS because Swift comes from iOS land.

On Thu, Jul 16, 2015 at 8:42 AM, Matthias Wessendorf <[hidden email]> wrote:
word up👍


On Thursday, July 16, 2015, Daniel Bevenius <[hidden email]> wrote:
+1 Sounds good

On 15 July 2015 at 22:52, Daniel Passos <[hidden email]> wrote:
+1

On Wed, Jul 15, 2015 at 4:21 PM, Bruno Oliveira <[hidden email]> wrote:
+1 makes more sense

On Wed, Jul 15, 2015 at 3:29 PM, Luke Holmquist <[hidden email]> wrote:
Hello all,

we've decided that it would probably be a good idea to move JIRA's related to the node-sender to the AG-JS JIRA instead of having them on the AGUSH JIRA.

i think this makes a bit more sense since this a javascript component.

I've started to move open JIRA's over.  i think i'll probably just leave the existing JIRA's where they are, unless someone feels strongly.


I've also started to create some "component" versions similar to the other projects.

the main JS lib will still be just numbers, like 2.3.0,  and for the node-sender we will now have node-sender-0.8.0, for example


-Luke

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--

-- 
"The measure of a man is what he does with power" - Plato
-
@abstractj
-
Volenti Nihil Difficile

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--
-- Passos

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--
Sent from Gmail Mobile

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--



--

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--

-- 
"The measure of a man is what he does with power" - Plato
-
@abstractj
-
Volenti Nihil Difficile

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev