Re: [DISCUSS] also move the Meecrowave repo to GITbox?

[Romain Manni-Bucau]

PS: think we are ready to release, tomcat and cxf are upgraded now on
trunk. I'll wait a few days for reviews and if noone beats me at releasing
I think I will do it next week, this way we can move to git end of the
month probably?

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



Le dim. 12 mai 2019 à 19:41, Gerhard Petracek  a
écrit :

> +1
>
> regards,
> gerhard
>
>
>
> Am Do., 9. Mai 2019 um 08:52 Uhr schrieb Mark Struberg
> :
> >
> > hi folks!
> >
> > Since we now already moved OWB itself and the meecrowave-examples,
> should we also move Meecrowave to GIT?
> > This is affect the last remaining project sticking with SVN (except the
> site which will remain SVN).
> >
> > wdyt?
> >
> > I'm +1 for moving meecrowave to GIT as well.
> >
> > LieGrue,
> > strub
> >
>

Re: [DISCUSS] also move the Meecrowave repo to GITbox?

[Gerhard Petracek]

+1

regards,
gerhard



Am Do., 9. Mai 2019 um 08:52 Uhr schrieb Mark Struberg
:
>
> hi folks!
>
> Since we now already moved OWB itself and the meecrowave-examples, should we 
> also move Meecrowave to GIT?
> This is affect the last remaining project sticking with SVN (except the site 
> which will remain SVN).
>
> wdyt?
>
> I'm +1 for moving meecrowave to GIT as well.
>
> LieGrue,
> strub
>

Re: [DISCUSS] also move the Meecrowave repo to GITbox?

[Jean-Louis MONTEIRO]

+1

Le jeu. 9 mai 2019 à 09:28, Mark Struberg  a
écrit :

> +1 to tc+fixes release with svn then move.
>
> LieGrue,
> strub
>
> > Am 09.05.2019 um 09:24 schrieb Reinhard Sandtner <
> reinhard.sandt...@gmail.com>:
> >
> > +1
> >
> > Von meinem iPhone gesendet
> >
> >> Am 09.05.2019 um 09:15 schrieb Thomas Andraschko <
> andraschko.tho...@gmail.com>:
> >>
> >> +1
> >>
> >> Am Do., 9. Mai 2019 um 09:01 Uhr schrieb Romain Manni-Bucau <
> >> rmannibu...@gmail.com>:
> >>
> >>> +1 but maybe after next release - we didnt cut one since last fixes
> right?
> >>> What about post tomcat+johnzon upgrades?
> >>>
> >>> Le jeu. 9 mai 2019 à 08:52, Mark Struberg 
> a
> >>> écrit :
> >>>
>  hi folks!
> 
>  Since we now already moved OWB itself and the meecrowave-examples,
> should
>  we also move Meecrowave to GIT?
>  This is affect the last remaining project sticking with SVN (except
> the
>  site which will remain SVN).
> 
>  wdyt?
> 
>  I'm +1 for moving meecrowave to GIT as well.
> 
>  LieGrue,
>  strub
> 
> 
> >>>
>
>

Re: [DISCUSS] also move the Meecrowave repo to GITbox?

[Mark Struberg]

+1 to tc+fixes release with svn then move.

LieGrue,
strub

> Am 09.05.2019 um 09:24 schrieb Reinhard Sandtner 
> :
> 
> +1
> 
> Von meinem iPhone gesendet
> 
>> Am 09.05.2019 um 09:15 schrieb Thomas Andraschko 
>> :
>> 
>> +1
>> 
>> Am Do., 9. Mai 2019 um 09:01 Uhr schrieb Romain Manni-Bucau <
>> rmannibu...@gmail.com>:
>> 
>>> +1 but maybe after next release - we didnt cut one since last fixes right?
>>> What about post tomcat+johnzon upgrades?
>>> 
>>> Le jeu. 9 mai 2019 à 08:52, Mark Struberg  a
>>> écrit :
>>> 
 hi folks!
 
 Since we now already moved OWB itself and the meecrowave-examples, should
 we also move Meecrowave to GIT?
 This is affect the last remaining project sticking with SVN (except the
 site which will remain SVN).
 
 wdyt?
 
 I'm +1 for moving meecrowave to GIT as well.
 
 LieGrue,
 strub
 
 
>>> 

Re: [DISCUSS] also move the Meecrowave repo to GITbox?

[Reinhard Sandtner]

+1

Von meinem iPhone gesendet

> Am 09.05.2019 um 09:15 schrieb Thomas Andraschko 
> :
> 
> +1
> 
> Am Do., 9. Mai 2019 um 09:01 Uhr schrieb Romain Manni-Bucau <
> rmannibu...@gmail.com>:
> 
>> +1 but maybe after next release - we didnt cut one since last fixes right?
>> What about post tomcat+johnzon upgrades?
>> 
>> Le jeu. 9 mai 2019 à 08:52, Mark Struberg  a
>> écrit :
>> 
>>> hi folks!
>>> 
>>> Since we now already moved OWB itself and the meecrowave-examples, should
>>> we also move Meecrowave to GIT?
>>> This is affect the last remaining project sticking with SVN (except the
>>> site which will remain SVN).
>>> 
>>> wdyt?
>>> 
>>> I'm +1 for moving meecrowave to GIT as well.
>>> 
>>> LieGrue,
>>> strub
>>> 
>>> 
>> 

Re: [DISCUSS] also move the Meecrowave repo to GITbox?

[Thomas Andraschko]

+1

Am Do., 9. Mai 2019 um 09:01 Uhr schrieb Romain Manni-Bucau <
rmannibu...@gmail.com>:

> +1 but maybe after next release - we didnt cut one since last fixes right?
> What about post tomcat+johnzon upgrades?
>
> Le jeu. 9 mai 2019 à 08:52, Mark Struberg  a
> écrit :
>
> > hi folks!
> >
> > Since we now already moved OWB itself and the meecrowave-examples, should
> > we also move Meecrowave to GIT?
> > This is affect the last remaining project sticking with SVN (except the
> > site which will remain SVN).
> >
> > wdyt?
> >
> > I'm +1 for moving meecrowave to GIT as well.
> >
> > LieGrue,
> > strub
> >
> >
>

Re: [DISCUSS] also move the Meecrowave repo to GITbox?

[Romain Manni-Bucau]

+1 but maybe after next release - we didnt cut one since last fixes right?
What about post tomcat+johnzon upgrades?

Le jeu. 9 mai 2019 à 08:52, Mark Struberg  a
écrit :

> hi folks!
>
> Since we now already moved OWB itself and the meecrowave-examples, should
> we also move Meecrowave to GIT?
> This is affect the last remaining project sticking with SVN (except the
> site which will remain SVN).
>
> wdyt?
>
> I'm +1 for moving meecrowave to GIT as well.
>
> LieGrue,
> strub
>
>

[DISCUSS] also move the Meecrowave repo to GITbox?

[Mark Struberg]

hi folks!

Since we now already moved OWB itself and the meecrowave-examples, should we 
also move Meecrowave to GIT?
This is affect the last remaining project sticking with SVN (except the site 
which will remain SVN).

wdyt?

I'm +1 for moving meecrowave to GIT as well.

LieGrue,
strub