10:13 a.m.
Hi,
Now Cordova has it’s own jira project and therefore it’s own version number, but in github
the plugins have their own repository. Would it make sense to move all the plugins into
one central github repository and when making a release to release all of them?
Wdyt?
Erik Jan
10:16 a.m.
On Tue, May 27, 2014 at 4:13 PM, Erik Jan de Wit <edewit(a)redhat.com> wrote:
Hi,
Now Cordova has it’s own jira project and therefore it’s own version
number, but in github the plugins have their own repository. Would it make
sense to move all the plugins into one central github repository and when
making a release to release all of them?
That means we get a few new release of the geo-plugin, while we really have
just changed things on the push-plugin (as an example) ?
-Matthias
Wdyt?
Erik Jan
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
10:21 a.m.
We get a release of AeroGear Cordova and all it’s components. I know if you want to find
out what changed for each plugin and version, that will be less ideal. If you have a
suggestion to have it tracked better I’m all ears
On 27 May,2014, at 16:16 , Matthias Wessendorf <matzew(a)apache.org> wrote:
On Tue, May 27, 2014 at 4:13 PM, Erik Jan de Wit <edewit(a)redhat.com> wrote:
Hi,
Now Cordova has it’s own jira project and therefore it’s own version number, but in
github the plugins have their own repository. Would it make sense to move all the plugins
into one central github repository and when making a release to release all of them?
That means we get a few new release of the geo-plugin, while we really have just changed
things on the push-plugin (as an example) ?
-Matthias
Wdyt?
Erik Jan
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
10:28 a.m.
On the practical side, it makes it a bit harder to install a Cordova plugin
from a git repo (because you need to point to a subdir) via Eclipse Thym
and Cordova CLI.
--
Gorkem
On Tue, May 27, 2014 at 10:21 AM, Erik Jan de Wit <edewit(a)redhat.com> wrote:
We get a release of AeroGear Cordova and all it’s components. I know
if
you want to find out what changed for each plugin and version, that will be
less ideal. If you have a suggestion to have it tracked better I’m all ears
On 27 May,2014, at 16:16 , Matthias Wessendorf <matzew(a)apache.org> wrote:
On Tue, May 27, 2014 at 4:13 PM, Erik Jan de Wit <edewit(a)redhat.com>wrote:
> Hi,
>
> Now Cordova has it’s own jira project and therefore it’s own version
> number, but in github the plugins have their own repository. Would it make
> sense to move all the plugins into one central github repository and when
> making a release to release all of them?
>
That means we get a few new release of the geo-plugin, while we really
have just changed things on the push-plugin (as an example) ?
-Matthias
>
> Wdyt?
> Erik Jan
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
10:51 a.m.
That is a very good point… so if we keep them as separate repos how do we manage multiple
versions / releases in jira
On 27 May,2014, at 16:28 , Gorkem Ercan <gorkem.ercan(a)gmail.com> wrote:
On the practical side, it makes it a bit harder to install a Cordova
plugin from a git repo (because you need to point to a subdir) via Eclipse Thym and
Cordova CLI.
--
Gorkem
On Tue, May 27, 2014 at 10:21 AM, Erik Jan de Wit <edewit(a)redhat.com> wrote:
We get a release of AeroGear Cordova and all it’s components. I know if you want to find
out what changed for each plugin and version, that will be less ideal. If you have a
suggestion to have it tracked better I’m all ears
On 27 May,2014, at 16:16 , Matthias Wessendorf <matzew(a)apache.org> wrote:
>
>
>
> On Tue, May 27, 2014 at 4:13 PM, Erik Jan de Wit <edewit(a)redhat.com> wrote:
> Hi,
>
> Now Cordova has it’s own jira project and therefore it’s own version number, but in
github the plugins have their own repository. Would it make sense to move all the plugins
into one central github repository and when making a release to release all of them?
>
>
> That means we get a few new release of the geo-plugin, while we really have just
changed things on the push-plugin (as an example) ?
>
> -Matthias
>
>
> Wdyt?
> Erik Jan
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
10:56 a.m.
Would tagging all repos with the same version number as the jira version
number on a release work?
--
Gorkem
On Tue, May 27, 2014 at 10:51 AM, Erik Jan de Wit <edewit(a)redhat.com> wrote:
That is a very good point… so if we keep them as separate repos how
do we
manage multiple versions / releases in jira
On 27 May,2014, at 16:28 , Gorkem Ercan <gorkem.ercan(a)gmail.com> wrote:
On the practical side, it makes it a bit harder to install a Cordova
plugin from a git repo (because you need to point to a subdir) via Eclipse
Thym and Cordova CLI.
--
Gorkem
On Tue, May 27, 2014 at 10:21 AM, Erik Jan de Wit <edewit(a)redhat.com>wrote:
> We get a release of AeroGear Cordova and all it’s components. I know if
> you want to find out what changed for each plugin and version, that will be
> less ideal. If you have a suggestion to have it tracked better I’m all ears
>
> On 27 May,2014, at 16:16 , Matthias Wessendorf <matzew(a)apache.org> wrote:
>
>
>
>
> On Tue, May 27, 2014 at 4:13 PM, Erik Jan de Wit <edewit(a)redhat.com>wrote:
>
>> Hi,
>>
>> Now Cordova has it’s own jira project and therefore it’s own version
>> number, but in github the plugins have their own repository. Would it make
>> sense to move all the plugins into one central github repository and when
>> making a release to release all of them?
>>
>
>
> That means we get a few new release of the geo-plugin, while we really
> have just changed things on the push-plugin (as an example) ?
>
> -Matthias
>
>
>>
>> Wdyt?
>> Erik Jan
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
4:27 a.m.
What about Arquillian approach in JIRA? geo_0.5.0, push_0.5.1, etc. Component
prefix for version. It is working quite well for a few years [1].
Karel
[1]
https://issues.jboss.org/browse/ARQ/?selectedTab=com.atlassian.jira.jira-...
On Tue, 27 May 2014 16:51:23 +0200
Erik Jan de Wit <edewit(a)redhat.com> wrote:
That is a very good point… so if we keep them as separate repos how
do we
manage multiple versions / releases in jira
On 27 May,2014, at 16:28 , Gorkem Ercan <gorkem.ercan(a)gmail.com> wrote:
> On the practical side, it makes it a bit harder to install a Cordova plugin
> from a git repo (because you need to point to a subdir) via Eclipse Thym
> and Cordova CLI. -- Gorkem
>
>
> On Tue, May 27, 2014 at 10:21 AM, Erik Jan de Wit <edewit(a)redhat.com> wrote:
> We get a release of AeroGear Cordova and all it’s components. I know if you
> want to find out what changed for each plugin and version, that will be
> less ideal. If you have a suggestion to have it tracked better I’m all ears
>
> On 27 May,2014, at 16:16 , Matthias Wessendorf <matzew(a)apache.org> wrote:
>
>>
>>
>>
>> On Tue, May 27, 2014 at 4:13 PM, Erik Jan de Wit <edewit(a)redhat.com>
wrote:
>> Hi,
>>
>> Now Cordova has it’s own jira project and therefore it’s own version
>> number, but in github the plugins have their own repository. Would it make
>> sense to move all the plugins into one central github repository and when
>> making a release to release all of them?
>>
>>
>> That means we get a few new release of the geo-plugin, while we really
>> have just changed things on the push-plugin (as an example) ?
>>
>> -Matthias
>>
>>
>> Wdyt?
>> Erik Jan
>>
______________________________________https://github.com/arquillian/arqui...
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
4:44 a.m.
On 2 Jun,2014, at 10:27 , Karel Piwko <kpiwko(a)redhat.com> wrote:
What about Arquillian approach in JIRA? geo_0.5.0, push_0.5.1, etc.
Component
prefix for version. It is working quite well for a few years [1].
Yeah, that sound good, I’ll use this approach, Matthias also proposed this and Gorkem had
a good point not not merge the git repos. That leaves this as the best option.
10:16 a.m.
What do you mean by a central repository? Example?
On 2014-05-27, Erik Jan de Wit wrote:
Hi,
Now Cordova has it’s own jira project and therefore it’s own version number, but in
github the plugins have their own repository. Would it make sense to move all the plugins
into one central github repository and when making a release to release all of them?
Wdyt?
Erik Jan
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
abstractj
10:19 a.m.
by repository I mean git repository
On 27 May,2014, at 16:16 , Bruno Oliveira <bruno(a)abstractj.org> wrote:
What do you mean by a central repository? Example?
On 2014-05-27, Erik Jan de Wit wrote:
> Hi,
>
> Now Cordova has it’s own jira project and therefore it’s own version number, but in
github the plugins have their own repository. Would it make sense to move all the plugins
into one central github repository and when making a release to release all of them?
>
> Wdyt?
> Erik Jan
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
abstractj
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
3:17 p.m.
I assume we are all talking about a git repositories here. By central
repository do you mean create something like /aerogear/cordova.git - and put everything
inside?
If yes, I would vote for separated repositories.
On 2014-05-27, Erik Jan de Wit wrote:
by repository I mean git repository
On 27 May,2014, at 16:16 , Bruno Oliveira <bruno(a)abstractj.org> wrote:
> What do you mean by a central repository? Example?
>
> On 2014-05-27, Erik Jan de Wit wrote:
>> Hi,
>>
>> Now Cordova has it’s own jira project and therefore it’s own version number, but
in github the plugins have their own repository. Would it make sense to move all the
plugins into one central github repository and when making a release to release all of
them?
>>
>> Wdyt?
>> Erik Jan
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> --
>
> abstractj
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
abstractj
3:03 a.m.
On Tue, May 27, 2014 at 4:13 PM, Erik Jan de Wit <edewit(a)redhat.com> wrote:
Hi,
Now Cordova has it’s own jira project and therefore it’s own version
number, but in github the plugins have their own repository. Would it make
sense to move all the plugins into one central github repository and when
making a release to release all of them?
To address the 'version' issue, I guess we can have a schema like below
inside of the Cordova JIRA:
crypto-x.y.z
geo-x.y.z
push-x.y.z
etc
That way we can still track the different components, on their own versions
- and do specific releases in JIRA as well
Wdyt?
Erik Jan
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
3614
days inactive
3620
days old
11 comments
5 participants
participants (5)
-
Bruno Oliveira -
Erik Jan de Wit -
Gorkem Ercan -
Karel Piwko -
Matthias Wessendorf