Re: Migrate all MyFaces projects to Git

[Thomas Andraschko]

Also deleted the unused branches now!

2018-06-21 17:23 GMT+02:00 Dennis Kieselhorst :

> Great, thank you!
>
> On 2018/06/21 13:59:15, Werner Punz  wrote:
> > Just deleted it...>
>
>

Re: Migrate all MyFaces projects to Git

[Dennis Kieselhorst]

Great, thank you!

On 2018/06/21 13:59:15, Werner Punz  wrote:
> Just deleted it...>

Re: Migrate all MyFaces projects to Git

[Werner Punz]

Just deleted it...

git branch --all
* master
  remotes/origin/1.1.x
  remotes/origin/1.2.x
  remotes/origin/1_1_2
  remotes/origin/1_1_3
  remotes/origin/1_1_4
  remotes/origin/1_1_5
  remotes/origin/1_1_6
  remotes/origin/1_1_6rc1
  remotes/origin/1_1_7
  remotes/origin/1_1_7prepare
  remotes/origin/1_1_8
  remotes/origin/1_2_0
  remotes/origin/1_2_1
  remotes/origin/1_2_2
  remotes/origin/1_2_3
  remotes/origin/1_2_4
  remotes/origin/1_2_5
  remotes/origin/1_2_6
  remotes/origin/1_2_7
  remotes/origin/1_2_8
  remotes/origin/1_2_8prepare
  remotes/origin/1_2_9
  remotes/origin/2.0.8_shade_prototype
  remotes/origin/2.0.8_windowid_prototype
  remotes/origin/2.0.x
  remotes/origin/2.0.x_refactor_shade_duplicate
  remotes/origin/2.1.x
  remotes/origin/2.1.x-client-window
  remotes/origin/2.1.x-copy
  remotes/origin/2.2.x
  remotes/origin/2_0_0
  remotes/origin/2_0_0_alpha
  remotes/origin/2_0_0_beta
  remotes/origin/2_0_0_beta_2
  remotes/origin/2_0_0_beta_3
  remotes/origin/2_0_0prepare
  remotes/origin/2_0_1
  remotes/origin/HEAD -> origin/master
  remotes/origin/master
  remotes/origin/matzew-branch
  remotes/origin/refactor_shared_2_1_x


Cheers

Werner


Am Do., 21. Juni 2018 um 15:55 Uhr schrieb Thomas Andraschko <
andraschko.tho...@gmail.com>:

> No problem! Would be great if you can it!
>
> 2018-06-21 15:51 GMT+02:00 Werner Punz :
>
>> Yes it was me accidentally, and only commits from my side went in (which
>> also are in master)
>> Shall I delete the branch or does someone else want to do it.
>> Btw. sorry that it happened. I did not notice that intellij was pushing
>> the branch as well.
>>
>> Werner
>>
>>
>> Am Do., 21. Juni 2018 um 15:47 Uhr schrieb Eduardo B :
>>
>>> I haven't started any release process after the move to git. So not sure
>>> who created that 2.3.x_ branch. I've been committing the MyFaces 2.3
>>> changes only to master branch.
>>>
>>> Regards,
>>> Eduardo
>>>
>>> On Thu, Jun 21, 2018 at 9:38 AM, Thomas Andraschko <
>>> andraschko.tho...@gmail.com> wrote:
>>>
>>>> Could it be related to the last release? @eduardo?
>>>>
>>>>
>>>>
>>>> 2018-06-21 15:36 GMT+02:00 Dennis Kieselhorst :
>>>>
>>>>> I don't know who created 2.3.x_ and for what reason. 2.3.x is currently
>>>>> on master and that's where we should release the next version.
>>>>>
>>>>> Best
>>>>> Dennis
>>>>>
>>>>> On 2018/06/21 13:30:19, "Paul Nicolucci"  wrote:
>>>>> >
>>>>> > I see we have a master branch on git as well as a "2.3.x_". I've
>>>>> been>
>>>>> > committing changes for version 2.3.x to the master branch should we
>>>>> also>
>>>>> > commit to the 2.3.x_ branch? Just want to ensure I'm doing the
>>>>> correct>
>>>>> > deliveries.>
>>>>> >
>>>>> > I assume we just need to deliver to master for 2.3 changes right now
>>>>> and>
>>>>> > then once we start a 2.4 etc we'll catch the 2.3.x branch up to
>>>>> master
>>>>> and>
>>>>> > do new forward development in master?>
>>>>> >
>>>>> > Thanks,>
>>>>> >
>>>>> > Paul Nicolucci>
>>>>> >
>>>>> >
>>>>> >
>>>>> > From: Dennis Kieselhorst >
>>>>> > To: >
>>>>> > Date: 05/23/2018 06:20 AM>
>>>>> > Subject: Re: Migrate all MyFaces projects to Git>
>>>>> >
>>>>> >
>>>>> >
>>>>> > > AFAICS you merged the 2.3.x into master, right? Shoudln't we remove
>>>>> the>
>>>>> > > 2.3.x branch then?>
>>>>> >
>>>>> > You are right. I was waiting for other opinions regarding 2.4.x in
>>>>> master.>
>>>>> > For now I've removed the 2.3.x branch.>
>>>>> >
>>>>> > Regards>
>>>>> > Dennis>
>>>>> >
>>>>> >
>>>>> >
>>>>> >
>>>>>
>>>>
>>>>
>>>
>

Re: Migrate all MyFaces projects to Git

[Thomas Andraschko]

No problem! Would be great if you can it!

2018-06-21 15:51 GMT+02:00 Werner Punz :

> Yes it was me accidentally, and only commits from my side went in (which
> also are in master)
> Shall I delete the branch or does someone else want to do it.
> Btw. sorry that it happened. I did not notice that intellij was pushing
> the branch as well.
>
> Werner
>
>
> Am Do., 21. Juni 2018 um 15:47 Uhr schrieb Eduardo B :
>
>> I haven't started any release process after the move to git. So not sure
>> who created that 2.3.x_ branch. I've been committing the MyFaces 2.3
>> changes only to master branch.
>>
>> Regards,
>> Eduardo
>>
>> On Thu, Jun 21, 2018 at 9:38 AM, Thomas Andraschko <
>> andraschko.tho...@gmail.com> wrote:
>>
>>> Could it be related to the last release? @eduardo?
>>>
>>>
>>>
>>> 2018-06-21 15:36 GMT+02:00 Dennis Kieselhorst :
>>>
>>>> I don't know who created 2.3.x_ and for what reason. 2.3.x is currently
>>>> on master and that's where we should release the next version.
>>>>
>>>> Best
>>>> Dennis
>>>>
>>>> On 2018/06/21 13:30:19, "Paul Nicolucci"  wrote:
>>>> >
>>>> > I see we have a master branch on git as well as a "2.3.x_". I've been>
>>>> > committing changes for version 2.3.x to the master branch should we
>>>> also>
>>>> > commit to the 2.3.x_ branch? Just want to ensure I'm doing the
>>>> correct>
>>>> > deliveries.>
>>>> >
>>>> > I assume we just need to deliver to master for 2.3 changes right now
>>>> and>
>>>> > then once we start a 2.4 etc we'll catch the 2.3.x branch up to master
>>>> and>
>>>> > do new forward development in master?>
>>>> >
>>>> > Thanks,>
>>>> >
>>>> > Paul Nicolucci>
>>>> >
>>>> >
>>>> >
>>>> > From: Dennis Kieselhorst >
>>>> > To: >
>>>> > Date: 05/23/2018 06:20 AM>
>>>> > Subject: Re: Migrate all MyFaces projects to Git>
>>>> >
>>>> >
>>>> >
>>>> > > AFAICS you merged the 2.3.x into master, right? Shoudln't we remove
>>>> the>
>>>> > > 2.3.x branch then?>
>>>> >
>>>> > You are right. I was waiting for other opinions regarding 2.4.x in
>>>> master.>
>>>> > For now I've removed the 2.3.x branch.>
>>>> >
>>>> > Regards>
>>>> > Dennis>
>>>> >
>>>> >
>>>> >
>>>> >
>>>>
>>>
>>>
>>

Re: Migrate all MyFaces projects to Git

[Werner Punz]

Yes it was me accidentally, and only commits from my side went in (which
also are in master)
Shall I delete the branch or does someone else want to do it.
Btw. sorry that it happened. I did not notice that intellij was pushing the
branch as well.

Werner


Am Do., 21. Juni 2018 um 15:47 Uhr schrieb Eduardo B :

> I haven't started any release process after the move to git. So not sure
> who created that 2.3.x_ branch. I've been committing the MyFaces 2.3
> changes only to master branch.
>
> Regards,
> Eduardo
>
> On Thu, Jun 21, 2018 at 9:38 AM, Thomas Andraschko <
> andraschko.tho...@gmail.com> wrote:
>
>> Could it be related to the last release? @eduardo?
>>
>>
>>
>> 2018-06-21 15:36 GMT+02:00 Dennis Kieselhorst :
>>
>>> I don't know who created 2.3.x_ and for what reason. 2.3.x is currently
>>> on master and that's where we should release the next version.
>>>
>>> Best
>>> Dennis
>>>
>>> On 2018/06/21 13:30:19, "Paul Nicolucci"  wrote:
>>> >
>>> > I see we have a master branch on git as well as a "2.3.x_". I've been>
>>> > committing changes for version 2.3.x to the master branch should we
>>> also>
>>> > commit to the 2.3.x_ branch? Just want to ensure I'm doing the correct>
>>> > deliveries.>
>>> >
>>> > I assume we just need to deliver to master for 2.3 changes right now
>>> and>
>>> > then once we start a 2.4 etc we'll catch the 2.3.x branch up to master
>>> and>
>>> > do new forward development in master?>
>>> >
>>> > Thanks,>
>>> >
>>> > Paul Nicolucci>
>>> >
>>> >
>>> >
>>> > From: Dennis Kieselhorst >
>>> > To: >
>>> > Date: 05/23/2018 06:20 AM>
>>> > Subject: Re: Migrate all MyFaces projects to Git>
>>> >
>>> >
>>> >
>>> > > AFAICS you merged the 2.3.x into master, right? Shoudln't we remove
>>> the>
>>> > > 2.3.x branch then?>
>>> >
>>> > You are right. I was waiting for other opinions regarding 2.4.x in
>>> master.>
>>> > For now I've removed the 2.3.x branch.>
>>> >
>>> > Regards>
>>> > Dennis>
>>> >
>>> >
>>> >
>>> >
>>>
>>
>>
>

Re: Migrate all MyFaces projects to Git

[Thomas Andraschko]

all right :) Werner, can you just remove it?

I will probably do a small cleanup of the branches next month, there are so
many very very old unused branches.

2018-06-21 15:47 GMT+02:00 Eduardo B :

> I haven't started any release process after the move to git. So not sure
> who created that 2.3.x_ branch. I've been committing the MyFaces 2.3
> changes only to master branch.
>
> Regards,
> Eduardo
>
> On Thu, Jun 21, 2018 at 9:38 AM, Thomas Andraschko <
> andraschko.tho...@gmail.com> wrote:
>
>> Could it be related to the last release? @eduardo?
>>
>>
>>
>> 2018-06-21 15:36 GMT+02:00 Dennis Kieselhorst :
>>
>>> I don't know who created 2.3.x_ and for what reason. 2.3.x is currently
>>> on master and that's where we should release the next version.
>>>
>>> Best
>>> Dennis
>>>
>>> On 2018/06/21 13:30:19, "Paul Nicolucci"  wrote:
>>> >
>>> > I see we have a master branch on git as well as a "2.3.x_". I've been>
>>> > committing changes for version 2.3.x to the master branch should we
>>> also>
>>> > commit to the 2.3.x_ branch? Just want to ensure I'm doing the correct>
>>> > deliveries.>
>>> >
>>> > I assume we just need to deliver to master for 2.3 changes right now
>>> and>
>>> > then once we start a 2.4 etc we'll catch the 2.3.x branch up to master
>>> and>
>>> > do new forward development in master?>
>>> >
>>> > Thanks,>
>>> >
>>> > Paul Nicolucci>
>>> >
>>> >
>>> >
>>> > From: Dennis Kieselhorst >
>>> > To: >
>>> > Date: 05/23/2018 06:20 AM>
>>> > Subject: Re: Migrate all MyFaces projects to Git>
>>> >
>>> >
>>> >
>>> > > AFAICS you merged the 2.3.x into master, right? Shoudln't we remove
>>> the>
>>> > > 2.3.x branch then?>
>>> >
>>> > You are right. I was waiting for other opinions regarding 2.4.x in
>>> master.>
>>> > For now I've removed the 2.3.x branch.>
>>> >
>>> > Regards>
>>> > Dennis>
>>> >
>>> >
>>> >
>>> >
>>>
>>
>>
>

Re: Migrate all MyFaces projects to Git

[Eduardo B]

I haven't started any release process after the move to git. So not sure
who created that 2.3.x_ branch. I've been committing the MyFaces 2.3
changes only to master branch.

Regards,
Eduardo

On Thu, Jun 21, 2018 at 9:38 AM, Thomas Andraschko <
andraschko.tho...@gmail.com> wrote:

> Could it be related to the last release? @eduardo?
>
>
>
> 2018-06-21 15:36 GMT+02:00 Dennis Kieselhorst :
>
>> I don't know who created 2.3.x_ and for what reason. 2.3.x is currently
>> on master and that's where we should release the next version.
>>
>> Best
>> Dennis
>>
>> On 2018/06/21 13:30:19, "Paul Nicolucci"  wrote:
>> >
>> > I see we have a master branch on git as well as a "2.3.x_". I've been>
>> > committing changes for version 2.3.x to the master branch should we
>> also>
>> > commit to the 2.3.x_ branch? Just want to ensure I'm doing the correct>
>> > deliveries.>
>> >
>> > I assume we just need to deliver to master for 2.3 changes right now
>> and>
>> > then once we start a 2.4 etc we'll catch the 2.3.x branch up to master
>> and>
>> > do new forward development in master?>
>> >
>> > Thanks,>
>> >
>> > Paul Nicolucci>
>> >
>> >
>> >
>> > From: Dennis Kieselhorst >
>> > To: >
>> > Date: 05/23/2018 06:20 AM>
>> > Subject: Re: Migrate all MyFaces projects to Git>
>> >
>> >
>> >
>> > > AFAICS you merged the 2.3.x into master, right? Shoudln't we remove
>> the>
>> > > 2.3.x branch then?>
>> >
>> > You are right. I was waiting for other opinions regarding 2.4.x in
>> master.>
>> > For now I've removed the 2.3.x branch.>
>> >
>> > Regards>
>> > Dennis>
>> >
>> >
>> >
>> >
>>
>
>

Re: Migrate all MyFaces projects to Git

[Werner Punz]

Ahh...
It could have been me accidentally pushing a local dev branch
At least from what it looks from the history.

(Commit: ed3c03ca2f7517fce95efdf624a07fe8d17defb4)

The best bet probably is to delete it.


Am Do., 21. Juni 2018 um 15:38 Uhr schrieb Thomas Andraschko <
andraschko.tho...@gmail.com>:

> Could it be related to the last release? @eduardo?
>
>
>
> 2018-06-21 15:36 GMT+02:00 Dennis Kieselhorst :
>
>> I don't know who created 2.3.x_ and for what reason. 2.3.x is currently
>> on master and that's where we should release the next version.
>>
>> Best
>> Dennis
>>
>> On 2018/06/21 13:30:19, "Paul Nicolucci"  wrote:
>> >
>> > I see we have a master branch on git as well as a "2.3.x_". I've been>
>> > committing changes for version 2.3.x to the master branch should we
>> also>
>> > commit to the 2.3.x_ branch? Just want to ensure I'm doing the correct>
>> > deliveries.>
>> >
>> > I assume we just need to deliver to master for 2.3 changes right now
>> and>
>> > then once we start a 2.4 etc we'll catch the 2.3.x branch up to master
>> and>
>> > do new forward development in master?>
>> >
>> > Thanks,>
>> >
>> > Paul Nicolucci>
>> >
>> >
>> >
>> > From: Dennis Kieselhorst >
>> > To: >
>> > Date: 05/23/2018 06:20 AM>
>> > Subject: Re: Migrate all MyFaces projects to Git>
>> >
>> >
>> >
>> > > AFAICS you merged the 2.3.x into master, right? Shoudln't we remove
>> the>
>> > > 2.3.x branch then?>
>> >
>> > You are right. I was waiting for other opinions regarding 2.4.x in
>> master.>
>> > For now I've removed the 2.3.x branch.>
>> >
>> > Regards>
>> > Dennis>
>> >
>> >
>> >
>> >
>>
>
>

Re: Migrate all MyFaces projects to Git

[Thomas Andraschko]

Could it be related to the last release? @eduardo?



2018-06-21 15:36 GMT+02:00 Dennis Kieselhorst :

> I don't know who created 2.3.x_ and for what reason. 2.3.x is currently
> on master and that's where we should release the next version.
>
> Best
> Dennis
>
> On 2018/06/21 13:30:19, "Paul Nicolucci"  wrote:
> >
> > I see we have a master branch on git as well as a "2.3.x_". I've been>
> > committing changes for version 2.3.x to the master branch should we also>
> > commit to the 2.3.x_ branch? Just want to ensure I'm doing the correct>
> > deliveries.>
> >
> > I assume we just need to deliver to master for 2.3 changes right now and>
> > then once we start a 2.4 etc we'll catch the 2.3.x branch up to master
> and>
> > do new forward development in master?>
> >
> > Thanks,>
> >
> > Paul Nicolucci>
> >
> >
> >
> > From: Dennis Kieselhorst >
> > To: >
> > Date: 05/23/2018 06:20 AM>
> > Subject: Re: Migrate all MyFaces projects to Git>
> >
> >
> >
> > > AFAICS you merged the 2.3.x into master, right? Shoudln't we remove
> the>
> > > 2.3.x branch then?>
> >
> > You are right. I was waiting for other opinions regarding 2.4.x in
> master.>
> > For now I've removed the 2.3.x branch.>
> >
> > Regards>
> > Dennis>
> >
> >
> >
> >
>

Re: Migrate all MyFaces projects to Git

[Dennis Kieselhorst]

I don't know who created 2.3.x_ and for what reason. 2.3.x is currently
on master and that's where we should release the next version.

Best
Dennis

On 2018/06/21 13:30:19, "Paul Nicolucci"  wrote:
>
> I see we have a master branch on git as well as a "2.3.x_". I've been>
> committing changes for version 2.3.x to the master branch should we also>
> commit to the 2.3.x_ branch? Just want to ensure I'm doing the correct>
> deliveries.>
>
> I assume we just need to deliver to master for 2.3 changes right now and>
> then once we start a 2.4 etc we'll catch the 2.3.x branch up to master
and>
> do new forward development in master?>
>
> Thanks,>
>
> Paul Nicolucci>
>
>
>
> From: Dennis Kieselhorst >
> To: >
> Date: 05/23/2018 06:20 AM>
> Subject: Re: Migrate all MyFaces projects to Git>
>
>
>
> > AFAICS you merged the 2.3.x into master, right? Shoudln't we remove
the>
> > 2.3.x branch then?>
>
> You are right. I was waiting for other opinions regarding 2.4.x in
master.>
> For now I've removed the 2.3.x branch.>
>
> Regards>
> Dennis>
>
>
>
>

Re: Migrate all MyFaces projects to Git

[Werner Punz]

Thanks for asking, I was a little bit puzzled as well.
I ended up committing it into master and cherry picking my changes
into 2.3.x_

Werner



Am Do., 21. Juni 2018 um 15:32 Uhr schrieb Paul Nicolucci <
pnico...@us.ibm.com>:

> I see we have a master branch on git as well as a "2.3.x_". I've been
> committing changes for version 2.3.x to the master branch should we also
> commit to the 2.3.x_ branch? Just want to ensure I'm doing the correct
> deliveries.
>
> I assume we just need to deliver to master for 2.3 changes right now and
> then once we start a 2.4 etc we'll catch the 2.3.x branch up to master and
> do new forward development in master?
>
> Thanks,
>
> Paul Nicolucci
>
> [image: Inactive hide details for Dennis Kieselhorst ---05/23/2018
> 06:20:13 AM---> AFAICS you merged the 2.3.x into master, right? Shou]Dennis
> Kieselhorst ---05/23/2018 06:20:13 AM---> AFAICS you merged the 2.3.x into
> master, right? Shoudln't we remove the > 2.3.x branch then?
>
> From: Dennis Kieselhorst 
> To: 
> Date: 05/23/2018 06:20 AM
> Subject: Re: Migrate all MyFaces projects to Git
> --
>
>
>
> > AFAICS you merged the 2.3.x into master, right? Shoudln't we remove the
> > 2.3.x branch then?
>
> You are right. I was waiting for other opinions regarding 2.4.x in master.
> For now I've removed the 2.3.x branch.
>
> Regards
> Dennis
>
>
>
>
>

Re: Migrate all MyFaces projects to Git

[Thomas Andraschko]

Hm? I thought dennis removed the the 2.3.x branch?

2018-06-21 15:30 GMT+02:00 Paul Nicolucci :

> I see we have a master branch on git as well as a "2.3.x_". I've been
> committing changes for version 2.3.x to the master branch should we also
> commit to the 2.3.x_ branch? Just want to ensure I'm doing the correct
> deliveries.
>
> I assume we just need to deliver to master for 2.3 changes right now and
> then once we start a 2.4 etc we'll catch the 2.3.x branch up to master and
> do new forward development in master?
>
> Thanks,
>
> Paul Nicolucci
>
> [image: Inactive hide details for Dennis Kieselhorst ---05/23/2018
> 06:20:13 AM---> AFAICS you merged the 2.3.x into master, right? Shou]Dennis
> Kieselhorst ---05/23/2018 06:20:13 AM---> AFAICS you merged the 2.3.x into
> master, right? Shoudln't we remove the > 2.3.x branch then?
>
> From: Dennis Kieselhorst 
> To: 
> Date: 05/23/2018 06:20 AM
> Subject: Re: Migrate all MyFaces projects to Git
> --
>
>
>
> > AFAICS you merged the 2.3.x into master, right? Shoudln't we remove the
> > 2.3.x branch then?
>
> You are right. I was waiting for other opinions regarding 2.4.x in master.
> For now I've removed the 2.3.x branch.
>
> Regards
> Dennis
>
>
>
>
>

Re: Migrate all MyFaces projects to Git

[Paul Nicolucci]

I see we have a master branch on git as well as a "2.3.x_". I've been
committing changes for version 2.3.x to the master branch should we also
commit to the 2.3.x_ branch? Just want to ensure I'm doing the correct
deliveries.

I assume we just need to deliver to master for 2.3 changes right now and
then once we start a 2.4 etc we'll catch the 2.3.x branch up to master and
do new forward development in master?

Thanks,

Paul Nicolucci



From:   Dennis Kieselhorst 
To: 
Date:   05/23/2018 06:20 AM
Subject:    Re: Migrate all MyFaces projects to Git



> AFAICS you merged the 2.3.x into master, right? Shoudln't we remove the
> 2.3.x branch then?

You are right. I was waiting for other opinions regarding 2.4.x in master.
For now I've removed the 2.3.x branch.

Regards
Dennis

Re: Migrate all MyFaces projects to Git

[Dennis Kieselhorst]

> AFAICS you merged the 2.3.x into master, right? Shoudln't we remove the
> 2.3.x branch then?

You are right. I was waiting for other opinions regarding 2.4.x in master. For 
now I've removed the 2.3.x branch.

Regards
Dennis

Re: Migrate all MyFaces projects to Git

[Thomas Andraschko]

@dennis

AFAICS you merged the 2.3.x into master, right? Shoudln't we remove the
2.3.x branch then?

2018-05-14 20:48 GMT+02:00 Dennis Kieselhorst :

> So the git migration is finished from INFRA point of view. All active
> projects from SVN have been moved to git and all previous mirrored repos
> have also been transfered (except portlet-bridge which was never setup
> properly and therefore removed).
>
> In total we have now 11 repos: https://github.com/apache/?
> utf8=%E2%9C%93=myfaces
>
> I noticed that not every active MyFaces committer has linked his GitHub
> account properly. If you want to work with GitHub (not mandatory), you have
> to link it via: https://gitbox.apache.org/setup/
>
> Everyone should update the documentation (site, release checklists, ...)
> when coming across old svn references.
>
> Cheers
> Dennis
>

Re: Migrate all MyFaces projects to Git

[Dennis Kieselhorst]

So the git migration is finished from INFRA point of view. All active projects 
from SVN have been moved to git and all previous mirrored repos have also been 
transfered (except portlet-bridge which was never setup properly and therefore 
removed).

In total we have now 11 repos: 
https://github.com/apache/?utf8=%E2%9C%93=myfaces

I noticed that not every active MyFaces committer has linked his GitHub account 
properly. If you want to work with GitHub (not mandatory), you have to link it 
via: https://gitbox.apache.org/setup/

Everyone should update the documentation (site, release checklists, ...) when 
coming across old svn references.

Cheers
Dennis

Re: Migrate all MyFaces projects to Git

[Dennis Kieselhorst]

Build-tools are now also finished, please use 
https://gitbox.apache.org/repos/asf/myfaces-build-tools.git or 
https://github.com/apache/myfaces-build-tools from now (default branch is 
currently wrong on GitHub, needs to be fixed by INFRA).

The site needs an update. Several places still mention SVN, some of these pages 
are even no longer linked in the menu. So far I just put a news entry on the 
main page and updated the doap file.

Re: Migrate all MyFaces projects to Git

[Dennis Kieselhorst]

> > WDYT about deleting some unused branches?
> > IMO we can remove everything, we just need the normal versions like 2.2.x,
> > 1.1.x, ...
> >
> > 2.1.x-client-window, 2.1.x-copy,  2.0.8_windowid_prototype, ... can be
> > removerd.

I agree, feel free to remove them. I just took over what we had in SVN.

> About the 2.3.x branch:
> IMO we could also set the master to 2.4.x and leave the 2.3.x branch as it
> is.
> Or should we until the work on JSF.next starts?

I think we should stick to 2.3.x for a while. It will take some time until JSF 
2.4 and although merging is easier with Git, it simplifies the development for 
now.

Regards
Dennis

Re: Migrate all MyFaces projects to Git

[Dora Rajappan]

 Thanks Dennis. I cloned again today. Its version 2.3.2-SNAPSHOT now. I heard 
jsf 2.3 or 2.4 is last. Since work goes on for 2.3.2 its good to be at 
2.3.2-SNAPSHOT.

On Wednesday, May 9, 2018, 2:02:50 PM GMT+5:30, Thomas Andraschko 
 wrote:  
 
 About the 2.3.x branch:
IMO we could also set the master to 2.4.x and leave the 2.3.x branch as it is.
Or should we until the work on JSF.next starts?


2018-05-09 10:27 GMT+02:00 Thomas Andraschko :

Thanks Dennis!

WDYT about deleting some unused branches?
IMO we can remove everything, we just need the normal versions like 2.2.x, 
1.1.x, ...

2.1.x-client-window, 2.1.x-copy,  2.0.8_windowid_prototype, ... can be removerd.



2018-05-08 22:12 GMT+02:00 Dennis Kieselhorst :

To avoid further confusion I've just done the merge from 2.3.x to master. 
Please have a look, if everything is fine for you. After that we can delete the 
2.3.x branch.

Cheers
Dennis




  

Re: Migrate all MyFaces projects to Git

[Thomas Andraschko]

About the 2.3.x branch:
IMO we could also set the master to 2.4.x and leave the 2.3.x branch as it
is.
Or should we until the work on JSF.next starts?


2018-05-09 10:27 GMT+02:00 Thomas Andraschko :

> Thanks Dennis!
>
> WDYT about deleting some unused branches?
> IMO we can remove everything, we just need the normal versions like 2.2.x,
> 1.1.x, ...
>
> 2.1.x-client-window, 2.1.x-copy,  2.0.8_windowid_prototype, ... can be
> removerd.
>
>
>
> 2018-05-08 22:12 GMT+02:00 Dennis Kieselhorst :
>
>> To avoid further confusion I've just done the merge from 2.3.x to master.
>> Please have a look, if everything is fine for you. After that we can delete
>> the 2.3.x branch.
>>
>> Cheers
>> Dennis
>>
>
>

Re: Migrate all MyFaces projects to Git

[Thomas Andraschko]

Thanks Dennis!

WDYT about deleting some unused branches?
IMO we can remove everything, we just need the normal versions like 2.2.x,
1.1.x, ...

2.1.x-client-window, 2.1.x-copy,  2.0.8_windowid_prototype, ... can be
removerd.



2018-05-08 22:12 GMT+02:00 Dennis Kieselhorst :

> To avoid further confusion I've just done the merge from 2.3.x to master.
> Please have a look, if everything is fine for you. After that we can delete
> the 2.3.x branch.
>
> Cheers
> Dennis
>

Re: Migrate all MyFaces projects to Git

[Dennis Kieselhorst]

To avoid further confusion I've just done the merge from 2.3.x to master. 
Please have a look, if everything is fine for you. After that we can delete the 
2.3.x branch.

Cheers
Dennis

Re: Migrate all MyFaces projects to Git

[Dennis Kieselhorst]

You need to switch to 2.3.x branch. Master still points to 2.2.x because this 
was trunk before the migration.

Re: Migrate all MyFaces projects to Git

[Dora Rajappan]

 It is  2.2.13-SNAPSHOT
On Tuesday, May 8, 2018, 10:07:29 PM GMT+5:30, Dora Rajappan 
 wrote:  
 
  
I could  just clone it.  Thank you. Hope its 2.3.1.On Tuesday, May 8, 2018, 
9:50:58 PM GMT+5:30, Dennis Kieselhorst  wrote:  
 
 So the migration of MyFaces Core is done. Please use 
https://gitbox.apache.org/repos/asf/myfaces.git or 
https://github.com/apache/myfaces from now.

Any volunteer who merges 2.3.x to master (former 2.2.x trunk)? I think it makes 
sense to switch now.

I'll continue with build-tools, it's more difficult then first thought, so it 
will take some extra time.

I was not aware that we already had mirrors for
https://github.com/apache/myfaces-extcdi
https://github.com/apache/myfaces-extval
https://github.com/apache/myfaces-html5
https://github.com/apache/myfaces-portlet-bridge
https://github.com/apache/myfaces-scripting

I'll have them transfered to Gitbox.

Re: Migrate all MyFaces projects to Git

[Dora Rajappan]

 
I could  just clone it.  Thank you. Hope its 2.3.1.On Tuesday, May 8, 2018, 
9:50:58 PM GMT+5:30, Dennis Kieselhorst  wrote:  
 
 So the migration of MyFaces Core is done. Please use 
https://gitbox.apache.org/repos/asf/myfaces.git or 
https://github.com/apache/myfaces from now.

Any volunteer who merges 2.3.x to master (former 2.2.x trunk)? I think it makes 
sense to switch now.

I'll continue with build-tools, it's more difficult then first thought, so it 
will take some extra time.

I was not aware that we already had mirrors for
https://github.com/apache/myfaces-extcdi
https://github.com/apache/myfaces-extval
https://github.com/apache/myfaces-html5
https://github.com/apache/myfaces-portlet-bridge
https://github.com/apache/myfaces-scripting

I'll have them transfered to Gitbox.
  

Re: Migrate all MyFaces projects to Git

[Dennis Kieselhorst]

So the migration of MyFaces Core is done. Please use 
https://gitbox.apache.org/repos/asf/myfaces.git or 
https://github.com/apache/myfaces from now.

Any volunteer who merges 2.3.x to master (former 2.2.x trunk)? I think it makes 
sense to switch now.

I'll continue with build-tools, it's more difficult then first thought, so it 
will take some extra time.

I was not aware that we already had mirrors for
https://github.com/apache/myfaces-extcdi
https://github.com/apache/myfaces-extval
https://github.com/apache/myfaces-html5
https://github.com/apache/myfaces-portlet-bridge
https://github.com/apache/myfaces-scripting

I'll have them transfered to Gitbox.

Re: Migrate all MyFaces projects to Git

[Dennis Kieselhorst]

As you might have read in the INFRA issue we are close to migrate the core repo 
so please do not commit until further notice. This simplifies the migration 
process. I already have a local git repo, just waiting for INFRA to cleanup old 
mirrors.

Re: Migrate all MyFaces projects to Git

[Dennis Kieselhorst]

test has been moved to https://gitbox.apache.org/repos/asf/myfaces-test.git and 
https://github.com/apache/myfaces-test

Re: Migrate all MyFaces projects to Git

[Dennis Kieselhorst]

myfaces-master-pom has been moved to 
https://gitbox.apache.org/repos/asf/myfaces-master-pom.git and 
https://github.com/apache/myfaces-master-pom

I was unable to clone myfaces-core from svn:
Checksum mismatch: 
myfaces/core/branches/2.1.x/shared/src/main/java/org/apache/myfaces/shared/renderkit/html/HtmlResponseWriterImpl.java
 de45947a39de1f3cd2c2d116cad7581f95b95bf9
expected: 9f9d5ed8f999a5e0742aab118c07666f
 got: f5ee553e7065c5c9c84366ed2a2c7185 

I asked infra to run a verify command to ensure that the svn repo is not 
corrupted.

Re: Migrate all MyFaces projects to Git

[Dennis Kieselhorst]

> > I tried to convert the existing svn repo to git, but unfortunately there
> > are historical svn authors like royalts, dave, o_rossmueller,  How
> > to map them? Are there corresponding Apache committer names or should I use
> > dev-n...@apache.org for them?

I found out that those usernames are SourceForge usernames. I was able to map 
them :D

royalts = Thomas Spiegl
dave = Anton Koinov
o_rossmueller = Oliver Rossmueller
tinytoony = Martin Marinschek
prophecyslides = Travis Reeder 

Re: Migrate all MyFaces projects to Git

[Thomas Andraschko]

+1 for dev-null

2018-04-26 14:47 GMT+02:00 Dennis Kieselhorst :

> > I've opened an INFRA issue to get the repos ready:
> https://issues.apache.org/jira/browse/INFRA-16402
>
> Got feedback from INFRA, plan is to update existing myfaces repo first and
> then migrate it to Gitbox.
>
> I tried to convert the existing svn repo to git, but unfortunately there
> are historical svn authors like royalts, dave, o_rossmueller,  How
> to map them? Are there corresponding Apache committer names or should I use
> dev-n...@apache.org for them?
>
> Does anyone know if there's a flag to tell git-svn to default to this
> entry if the key is not in the authors file? I'm using:
> https://git-wip-us.apache.org/authors.txt
>
> Regards
> Dennis
>

Re: Migrate all MyFaces projects to Git

[Dennis Kieselhorst]

> I've opened an INFRA issue to get the repos ready: 
> https://issues.apache.org/jira/browse/INFRA-16402

Got feedback from INFRA, plan is to update existing myfaces repo first and then 
migrate it to Gitbox.

I tried to convert the existing svn repo to git, but unfortunately there are 
historical svn authors like royalts, dave, o_rossmueller,  How to map 
them? Are there corresponding Apache committer names or should I use 
dev-n...@apache.org for them?

Does anyone know if there's a flag to tell git-svn to default to this entry if 
the key is not in the authors file? I'm using: 
https://git-wip-us.apache.org/authors.txt

Regards
Dennis

Re: Migrate all MyFaces projects to Git

[Dennis Kieselhorst]

I've opened an INFRA issue to get the repos ready: 
https://issues.apache.org/jira/browse/INFRA-16402

Re: Migrate all MyFaces projects to Git

[Thomas Andraschko]

Yep thats true.
It was just an idea to minimize required projects.

2018-04-12 10:50 GMT+02:00 Udo Schnurpfeil :

> When you only have the examples folder, it can't work.
>
> About MyFaces-Core: you will need a copy for each version of MyFaces
> 2.0, 2.1, 2.2., 2.3.
>
> Nevertheless, I see no reason to restructure the build process only for
> a git migration.
>
> Regards,
>
> Udo
>
> Am 12.04.18 um 10:33 schrieb Thomas Andraschko:
> > It works fine for my personal projects.
> >
> > /myfaces-tobago/pom.xml
> > /myfaces-tobago/checkstyle.xml
> > /myfaces-tobago/examples/pom.xml
> > /myfaces-tobago/examples/
> >
> > The examples pom inherit from the root pom and the root pom's checkstyle
> > plugin has:
> >
> > checkstyle.xml
> >
> >
> > No problem to build only the examples.
> >
> >
> > 2018-04-12 10:24 GMT+02:00 Udo Schnurpfeil  > >:
> >
> > Sorry for wrong addressing...
> >
> > The maven-checkstyle-plugin and dependency-check-maven CAN load the
> > configuration from the file system. But when you do that, it's no
> longer
> > possible to build only a sub-module, e.g. an example. That's the
> reason
> > why these configuration in a Maven artifact. "It's just available".
> >
> > Regards,
> > Udo
> >
> > Am 12.04.18 um 10:12 schrieb Thomas Andraschko:
> > > Hi Udo, you only sent it to me, now adding dev@myfaces.
> > >
> > >
> > > What do you mean exactly?
> > > This are just checkstyle files, which can be placed inside tobago
> itself.
> > > e.g.
> > > /myfaces-tobago/pom.xml
> > > /myfaces-tobago/checkstyle.xml
> > >
> > > there is no need to give the checkstyle a own project, it coudl be
> just
> > > a project file.
> > >
> > >
> > >
> > > 2018-04-12 10:08 GMT+02:00 Udo Schnurpfeil  
> > > >>:
> > >
> > > Hi Thomas,
> > >
> > > I've checked how to put the tobago-checkstyle stuff inside of
> > > Tobago. The easy way (with 1 release cycle) will not work,
> because
> > > in that case we will have cyclic dependencies.
> > >
> > > The other way would be: Having 2 release numbers and 2
> releases. But
> > > in that case we have no advantage. The number of releases and
> votes
> > > are the same.
> > >
> > > We shouldn't mix the git migration too much with project
> refactoring.
> > >
> > >
> > > What's about /keys and /myfaces-site-skins
> > >  > >?
> > >
> > >
> > > Regards,
> > >
> > > Udo
> > >
> > >
> > > Am 12.04.18 um 09:50 schrieb Thomas Andraschko:
> > >> We should really think about it we need to migrate
> > >> myfaces-build-tools.
> > >> The only active stuff maintained here is the checkstyle, we
> can be
> > >> simply moved the projects.
> > >>
> > >> Extensions is also ExtVal and CODI are not maintained,
> only
> > >> ExtScripting got a small update this year.
> > >>
> > >>
> > >>
> > >> 2018-04-12 8:47 GMT+02:00 Dennis Kieselhorst  
> > >> >>:
> > >>
> > >> Yes, everything is working. It's good idea to do the
> migration.
> > >>
> > >> As far as I can see we need the following repos:
> > >> myfaces (for myfaces-core, already exists as old mirror
> > >> https://github.com/apache/myfaces <
> https://github.com/apache/myfaces>
> > >>  > >)
> > >> myfaces-master-pom
> > >> myfaces-build-tools
> > >> myfaces-extensions
> > >> myfaces-test
> > >>
> > >> The other stuff has not been updated for over a year
> > >> (http://svn.apache.org/viewvc/myfaces/?sortby=date
> > 
> > >>  > >) so looks
> > >> like no need to migrate it?!
> > >>
> > >> Is anyone willing to do further cleanup?
> > >>
> > >> Regards
> > >> Dennis
> > >>
> > >> On 2018/04/11 18:37:23, Thomas Andraschko
> > >>  gmail.com>
> > >> >>
> > wrote:
> > >> > Is everything fine now for tobago and trinidad?
> > >> >
> >

Re: Migrate all MyFaces projects to Git

[Udo Schnurpfeil]

When you only have the examples folder, it can't work.

About MyFaces-Core: you will need a copy for each version of MyFaces
2.0, 2.1, 2.2., 2.3.

Nevertheless, I see no reason to restructure the build process only for
a git migration.

Regards,

Udo

Am 12.04.18 um 10:33 schrieb Thomas Andraschko:
> It works fine for my personal projects.
> 
> /myfaces-tobago/pom.xml
> /myfaces-tobago/checkstyle.xml
> /myfaces-tobago/examples/pom.xml
> /myfaces-tobago/examples/
> 
> The examples pom inherit from the root pom and the root pom's checkstyle
> plugin has:
> 
> checkstyle.xml
> 
> 
> No problem to build only the examples.
> 
> 
> 2018-04-12 10:24 GMT+02:00 Udo Schnurpfeil  >:
> 
> Sorry for wrong addressing...
> 
> The maven-checkstyle-plugin and dependency-check-maven CAN load the
> configuration from the file system. But when you do that, it's no longer
> possible to build only a sub-module, e.g. an example. That's the reason
> why these configuration in a Maven artifact. "It's just available".
> 
> Regards,
> Udo
> 
> Am 12.04.18 um 10:12 schrieb Thomas Andraschko:
> > Hi Udo, you only sent it to me, now adding dev@myfaces.
> >
> >
> > What do you mean exactly?
> > This are just checkstyle files, which can be placed inside tobago 
> itself.
> > e.g.
> > /myfaces-tobago/pom.xml
> > /myfaces-tobago/checkstyle.xml
> >
> > there is no need to give the checkstyle a own project, it coudl be just
> > a project file.
> >
> >
> >
> > 2018-04-12 10:08 GMT+02:00 Udo Schnurpfeil  
> > >>:
> >
> >     Hi Thomas,
> >
> >     I've checked how to put the tobago-checkstyle stuff inside of
> >     Tobago. The easy way (with 1 release cycle) will not work, because
> >     in that case we will have cyclic dependencies.
> >
> >     The other way would be: Having 2 release numbers and 2 releases. But
> >     in that case we have no advantage. The number of releases and votes
> >     are the same.
> >
> >     We shouldn't mix the git migration too much with project 
> refactoring. 
> >
> >
> >     What's about /keys and /myfaces-site-skins
> >      >?
> >
> >
> >     Regards,
> >
> >     Udo
> >
> >
> >     Am 12.04.18 um 09:50 schrieb Thomas Andraschko:
> >>     We should really think about it we need to migrate
> >>     myfaces-build-tools.
> >>     The only active stuff maintained here is the checkstyle, we can be
> >>     simply moved the projects.
> >>
> >>     Extensions is also ExtVal and CODI are not maintained, only
> >>     ExtScripting got a small update this year.
> >>
> >>
> >>
> >>     2018-04-12 8:47 GMT+02:00 Dennis Kieselhorst  
> >>     >>:
> >>
> >>         Yes, everything is working. It's good idea to do the migration.
> >>
> >>         As far as I can see we need the following repos:
> >>         myfaces (for myfaces-core, already exists as old mirror
> >>         https://github.com/apache/myfaces 
> 
> >>          >)
> >>         myfaces-master-pom
> >>         myfaces-build-tools
> >>         myfaces-extensions
> >>         myfaces-test
> >>
> >>         The other stuff has not been updated for over a year
> >>         (http://svn.apache.org/viewvc/myfaces/?sortby=date
> 
> >>          >) so looks
> >>         like no need to migrate it?!
> >>
> >>         Is anyone willing to do further cleanup?
> >>
> >>         Regards
> >>         Dennis
> >>
> >>         On 2018/04/11 18:37:23, Thomas Andraschko
> >>          
> >>          >>
> wrote:
> >>         > Is everything fine now for tobago and trinidad?
> >>         >
> >>         > +1 for migrating core now as 2.3.0 is out, maybe we have to
> >>         wait for 2.3.1
> >>         >
> >>         > we could also do a bit a cleanup and only migrate the active
> >>         projects
> >>         > We must also check e.g. the maven plugins and master poms...
> >>         > E.g. we could remove the checkstyle files and 

Re: Migrate all MyFaces projects to Git

[Thomas Andraschko]

It works fine for my personal projects.

/myfaces-tobago/pom.xml
/myfaces-tobago/checkstyle.xml
/myfaces-tobago/examples/pom.xml
/myfaces-tobago/examples/

The examples pom inherit from the root pom and the root pom's checkstyle
plugin has:

checkstyle.xml


No problem to build only the examples.


2018-04-12 10:24 GMT+02:00 Udo Schnurpfeil :

> Sorry for wrong addressing...
>
> The maven-checkstyle-plugin and dependency-check-maven CAN load the
> configuration from the file system. But when you do that, it's no longer
> possible to build only a sub-module, e.g. an example. That's the reason
> why these configuration in a Maven artifact. "It's just available".
>
> Regards,
> Udo
>
> Am 12.04.18 um 10:12 schrieb Thomas Andraschko:
> > Hi Udo, you only sent it to me, now adding dev@myfaces.
> >
> >
> > What do you mean exactly?
> > This are just checkstyle files, which can be placed inside tobago itself.
> > e.g.
> > /myfaces-tobago/pom.xml
> > /myfaces-tobago/checkstyle.xml
> >
> > there is no need to give the checkstyle a own project, it coudl be just
> > a project file.
> >
> >
> >
> > 2018-04-12 10:08 GMT+02:00 Udo Schnurpfeil  > >:
> >
> > Hi Thomas,
> >
> > I've checked how to put the tobago-checkstyle stuff inside of
> > Tobago. The easy way (with 1 release cycle) will not work, because
> > in that case we will have cyclic dependencies.
> >
> > The other way would be: Having 2 release numbers and 2 releases. But
> > in that case we have no advantage. The number of releases and votes
> > are the same.
> >
> > We shouldn't mix the git migration too much with project
> refactoring.
> >
> >
> > What's about /keys and /myfaces-site-skins
> > ?
> >
> >
> > Regards,
> >
> > Udo
> >
> >
> > Am 12.04.18 um 09:50 schrieb Thomas Andraschko:
> >> We should really think about it we need to migrate
> >> myfaces-build-tools.
> >> The only active stuff maintained here is the checkstyle, we can be
> >> simply moved the projects.
> >>
> >> Extensions is also ExtVal and CODI are not maintained, only
> >> ExtScripting got a small update this year.
> >>
> >>
> >>
> >> 2018-04-12 8:47 GMT+02:00 Dennis Kieselhorst  >> >:
> >>
> >> Yes, everything is working. It's good idea to do the migration.
> >>
> >> As far as I can see we need the following repos:
> >> myfaces (for myfaces-core, already exists as old mirror
> >> https://github.com/apache/myfaces
> >> )
> >> myfaces-master-pom
> >> myfaces-build-tools
> >> myfaces-extensions
> >> myfaces-test
> >>
> >> The other stuff has not been updated for over a year
> >> (http://svn.apache.org/viewvc/myfaces/?sortby=date
> >> ) so looks
> >> like no need to migrate it?!
> >>
> >> Is anyone willing to do further cleanup?
> >>
> >> Regards
> >> Dennis
> >>
> >> On 2018/04/11 18:37:23, Thomas Andraschko
> >>  >> > wrote:
> >> > Is everything fine now for tobago and trinidad?
> >> >
> >> > +1 for migrating core now as 2.3.0 is out, maybe we have to
> >> wait for 2.3.1
> >> >
> >> > we could also do a bit a cleanup and only migrate the active
> >> projects
> >> > We must also check e.g. the maven plugins and master poms...
> >> > E.g. we could remove the checkstyle files and move them to
> >> the tobago and
> >> > core itself instead maintain a projects which contains both...
> >> >
> >> > It think it would be the right momemt to do a cleanup now,
> >> to make it
> >> > easier to maintain in the future.
> >> >
> >> >
> >> > 2017-09-17 20:16 GMT+02:00 Dennis Kieselhorst
> >> >:
> >> >
> >> > >
> >> > > > https://svn.apache.org/repos/asf/myfaces/trinidad-maven/
> >>  has
> >> not been
> >> > > > migrated yet, I've requested a new repo for it.
> >> > > Migration of trinidad-maven is finished:
> >> > > https://github.com/apache/myfaces-trinidad-maven
> >>  or
> >> > >
> >> https://gitbox.apache.org/repos/asf?p=myfaces-trinidad-
> maven.git
> >>  maven.git>
> >> > >
> >> >
> >>
> >>
> >
> >
>

Re: Migrate all MyFaces projects to Git

[Udo Schnurpfeil]

Sorry for wrong addressing...

The maven-checkstyle-plugin and dependency-check-maven CAN load the
configuration from the file system. But when you do that, it's no longer
possible to build only a sub-module, e.g. an example. That's the reason
why these configuration in a Maven artifact. "It's just available".

Regards,
Udo

Am 12.04.18 um 10:12 schrieb Thomas Andraschko:
> Hi Udo, you only sent it to me, now adding dev@myfaces.
> 
> 
> What do you mean exactly?
> This are just checkstyle files, which can be placed inside tobago itself.
> e.g.
> /myfaces-tobago/pom.xml
> /myfaces-tobago/checkstyle.xml
> 
> there is no need to give the checkstyle a own project, it coudl be just
> a project file.
> 
> 
> 
> 2018-04-12 10:08 GMT+02:00 Udo Schnurpfeil  >:
> 
> Hi Thomas,
> 
> I've checked how to put the tobago-checkstyle stuff inside of
> Tobago. The easy way (with 1 release cycle) will not work, because
> in that case we will have cyclic dependencies.
> 
> The other way would be: Having 2 release numbers and 2 releases. But
> in that case we have no advantage. The number of releases and votes
> are the same.
> 
> We shouldn't mix the git migration too much with project refactoring. 
> 
> 
> What's about /keys and /myfaces-site-skins
> ?
> 
> 
> Regards,
> 
> Udo
> 
> 
> Am 12.04.18 um 09:50 schrieb Thomas Andraschko:
>> We should really think about it we need to migrate
>> myfaces-build-tools.
>> The only active stuff maintained here is the checkstyle, we can be
>> simply moved the projects.
>>
>> Extensions is also ExtVal and CODI are not maintained, only
>> ExtScripting got a small update this year.
>>
>>
>>
>> 2018-04-12 8:47 GMT+02:00 Dennis Kieselhorst > >:
>>
>> Yes, everything is working. It's good idea to do the migration.
>>
>> As far as I can see we need the following repos:
>> myfaces (for myfaces-core, already exists as old mirror
>> https://github.com/apache/myfaces
>> )
>> myfaces-master-pom
>> myfaces-build-tools
>> myfaces-extensions
>> myfaces-test
>>
>> The other stuff has not been updated for over a year
>> (http://svn.apache.org/viewvc/myfaces/?sortby=date
>> ) so looks
>> like no need to migrate it?!
>>
>> Is anyone willing to do further cleanup?
>>
>> Regards
>> Dennis
>>
>> On 2018/04/11 18:37:23, Thomas Andraschko
>> > > wrote:
>> > Is everything fine now for tobago and trinidad?
>> >
>> > +1 for migrating core now as 2.3.0 is out, maybe we have to
>> wait for 2.3.1
>> >
>> > we could also do a bit a cleanup and only migrate the active
>> projects
>> > We must also check e.g. the maven plugins and master poms...
>> > E.g. we could remove the checkstyle files and move them to
>> the tobago and
>> > core itself instead maintain a projects which contains both...
>> >
>> > It think it would be the right momemt to do a cleanup now,
>> to make it
>> > easier to maintain in the future.
>> >
>> >
>> > 2017-09-17 20:16 GMT+02:00 Dennis Kieselhorst
>> >:
>> >
>> > >
>> > > > https://svn.apache.org/repos/asf/myfaces/trinidad-maven/
>>  has
>> not been
>> > > > migrated yet, I've requested a new repo for it.
>> > > Migration of trinidad-maven is finished:
>> > > https://github.com/apache/myfaces-trinidad-maven
>>  or
>> > >
>> https://gitbox.apache.org/repos/asf?p=myfaces-trinidad-maven.git
>> 
>> > >
>> >
>>
>>
> 
> 

Re: Migrate all MyFaces projects to Git

[Thomas Andraschko]

Hi Udo, you only sent it to me, now adding dev@myfaces.


What do you mean exactly?
This are just checkstyle files, which can be placed inside tobago itself.
e.g.
/myfaces-tobago/pom.xml
/myfaces-tobago/checkstyle.xml

there is no need to give the checkstyle a own project, it coudl be just a
project file.



2018-04-12 10:08 GMT+02:00 Udo Schnurpfeil :

> Hi Thomas,
>
> I've checked how to put the tobago-checkstyle stuff inside of Tobago. The
> easy way (with 1 release cycle) will not work, because in that case we will
> have cyclic dependencies.
>
> The other way would be: Having 2 release numbers and 2 releases. But in
> that case we have no advantage. The number of releases and votes are the
> same.
>
> We shouldn't mix the git migration too much with project refactoring.
>
>
> What's about /keys and /myfaces-site-skins
> ?
>
>
> Regards,
>
> Udo
>
> Am 12.04.18 um 09:50 schrieb Thomas Andraschko:
>
> We should really think about it we need to migrate myfaces-build-tools.
> The only active stuff maintained here is the checkstyle, we can be simply
> moved the projects.
>
> Extensions is also ExtVal and CODI are not maintained, only
> ExtScripting got a small update this year.
>
>
>
> 2018-04-12 8:47 GMT+02:00 Dennis Kieselhorst :
>
>> Yes, everything is working. It's good idea to do the migration.
>>
>> As far as I can see we need the following repos:
>> myfaces (for myfaces-core, already exists as old mirror
>> https://github.com/apache/myfaces)
>> myfaces-master-pom
>> myfaces-build-tools
>> myfaces-extensions
>> myfaces-test
>>
>> The other stuff has not been updated for over a year (
>> http://svn.apache.org/viewvc/myfaces/?sortby=date) so looks like no need
>> to migrate it?!
>>
>> Is anyone willing to do further cleanup?
>>
>> Regards
>> Dennis
>>
>> On 2018/04/11 18:37:23, Thomas Andraschko 
>> wrote:
>> > Is everything fine now for tobago and trinidad?
>> >
>> > +1 for migrating core now as 2.3.0 is out, maybe we have to wait for
>> 2.3.1
>> >
>> > we could also do a bit a cleanup and only migrate the active projects
>> > We must also check e.g. the maven plugins and master poms...
>> > E.g. we could remove the checkstyle files and move them to the tobago
>> and
>> > core itself instead maintain a projects which contains both...
>> >
>> > It think it would be the right momemt to do a cleanup now, to make it
>> > easier to maintain in the future.
>> >
>> >
>> > 2017-09-17 20:16 GMT+02:00 Dennis Kieselhorst :
>> >
>> > >
>> > > > https://svn.apache.org/repos/asf/myfaces/trinidad-maven/ has not
>> been
>> > > > migrated yet, I've requested a new repo for it.
>> > > Migration of trinidad-maven is finished:
>> > > https://github.com/apache/myfaces-trinidad-maven or
>> > > https://gitbox.apache.org/repos/asf?p=myfaces-trinidad-maven.git
>> > >
>> >
>>
>
>
>

Re: Migrate all MyFaces projects to Git

[Thomas Andraschko]

We should really think about it we need to migrate myfaces-build-tools.
The only active stuff maintained here is the checkstyle, we can be simply
moved the projects.

Extensions is also ExtVal and CODI are not maintained, only
ExtScripting got a small update this year.



2018-04-12 8:47 GMT+02:00 Dennis Kieselhorst :

> Yes, everything is working. It's good idea to do the migration.
>
> As far as I can see we need the following repos:
> myfaces (for myfaces-core, already exists as old mirror
> https://github.com/apache/myfaces)
> myfaces-master-pom
> myfaces-build-tools
> myfaces-extensions
> myfaces-test
>
> The other stuff has not been updated for over a year (
> http://svn.apache.org/viewvc/myfaces/?sortby=date) so looks like no need
> to migrate it?!
>
> Is anyone willing to do further cleanup?
>
> Regards
> Dennis
>
> On 2018/04/11 18:37:23, Thomas Andraschko 
> wrote:
> > Is everything fine now for tobago and trinidad?
> >
> > +1 for migrating core now as 2.3.0 is out, maybe we have to wait for
> 2.3.1
> >
> > we could also do a bit a cleanup and only migrate the active projects
> > We must also check e.g. the maven plugins and master poms...
> > E.g. we could remove the checkstyle files and move them to the tobago and
> > core itself instead maintain a projects which contains both...
> >
> > It think it would be the right momemt to do a cleanup now, to make it
> > easier to maintain in the future.
> >
> >
> > 2017-09-17 20:16 GMT+02:00 Dennis Kieselhorst :
> >
> > >
> > > > https://svn.apache.org/repos/asf/myfaces/trinidad-maven/ has not
> been
> > > > migrated yet, I've requested a new repo for it.
> > > Migration of trinidad-maven is finished:
> > > https://github.com/apache/myfaces-trinidad-maven or
> > > https://gitbox.apache.org/repos/asf?p=myfaces-trinidad-maven.git
> > >
> >
>

Re: Migrate all MyFaces projects to Git

[Dennis Kieselhorst]

Yes, everything is working. It's good idea to do the migration.

As far as I can see we need the following repos:
myfaces (for myfaces-core, already exists as old mirror 
https://github.com/apache/myfaces)
myfaces-master-pom
myfaces-build-tools
myfaces-extensions
myfaces-test

The other stuff has not been updated for over a year 
(http://svn.apache.org/viewvc/myfaces/?sortby=date) so looks like no need to 
migrate it?!

Is anyone willing to do further cleanup?

Regards
Dennis

On 2018/04/11 18:37:23, Thomas Andraschko  wrote: 
> Is everything fine now for tobago and trinidad?
> 
> +1 for migrating core now as 2.3.0 is out, maybe we have to wait for 2.3.1
> 
> we could also do a bit a cleanup and only migrate the active projects
> We must also check e.g. the maven plugins and master poms...
> E.g. we could remove the checkstyle files and move them to the tobago and
> core itself instead maintain a projects which contains both...
> 
> It think it would be the right momemt to do a cleanup now, to make it
> easier to maintain in the future.
> 
> 
> 2017-09-17 20:16 GMT+02:00 Dennis Kieselhorst :
> 
> >
> > > https://svn.apache.org/repos/asf/myfaces/trinidad-maven/ has not been
> > > migrated yet, I've requested a new repo for it.
> > Migration of trinidad-maven is finished:
> > https://github.com/apache/myfaces-trinidad-maven or
> > https://gitbox.apache.org/repos/asf?p=myfaces-trinidad-maven.git
> >
> 

Re: Migrate all MyFaces projects to Git

[Thomas Andraschko]

Is everything fine now for tobago and trinidad?

+1 for migrating core now as 2.3.0 is out, maybe we have to wait for 2.3.1

we could also do a bit a cleanup and only migrate the active projects
We must also check e.g. the maven plugins and master poms...
E.g. we could remove the checkstyle files and move them to the tobago and
core itself instead maintain a projects which contains both...

It think it would be the right momemt to do a cleanup now, to make it
easier to maintain in the future.


2017-09-17 20:16 GMT+02:00 Dennis Kieselhorst :

>
> > https://svn.apache.org/repos/asf/myfaces/trinidad-maven/ has not been
> > migrated yet, I've requested a new repo for it.
> Migration of trinidad-maven is finished:
> https://github.com/apache/myfaces-trinidad-maven or
> https://gitbox.apache.org/repos/asf?p=myfaces-trinidad-maven.git
>

Re: Migrate all MyFaces projects to Git

[Dennis Kieselhorst]

> https://svn.apache.org/repos/asf/myfaces/trinidad-maven/ has not been
> migrated yet, I've requested a new repo for it.
Migration of trinidad-maven is finished:
https://github.com/apache/myfaces-trinidad-maven or
https://gitbox.apache.org/repos/asf?p=myfaces-trinidad-maven.git

Re: Migrate all MyFaces projects to Git

[Dennis Kieselhorst]

I finally managed to migrate trinidad.

Please use https://gitbox.apache.org/repos/asf/myfaces-trinidad.git or
https://github.com/apache/myfaces-trinidad from now on. SVN has been
marked as readonly.

https://svn.apache.org/repos/asf/myfaces/trinidad-maven/ has not been
migrated yet, I've requested a new repo for it.

Dennis

Re: Migrate all MyFaces projects to Git

[Bernd Bohmann]

Big +1 from my side.

Bernd

On Fri, Sep 15, 2017 at 9:23 AM, Dennis Kieselhorst  wrote:

> On 2017-09-08 09:49, Dennis Kieselhorst  wrote:
> > Trinidad will follow till Sunday.
>
> Short update on Trinidad git migration.
>
> I used the following command:
> git svn clone --stdlayout --no-metadata --authors-file=authors.txt
> https://svn.apache.org/repos/asf/myfaces/trinidad/ trinidad-tmp
>
> This is running for almost a week now and consuming more and more memory
> and cpu. I already used a cloud instance to speed this up.
>
> I suggest to add --ignore-paths for all branches except trinidad-1.2.x,
> trinidad-2.0.x and trinidad-2.1.x. All other branches haven't been
> touched for at least three years. They will still be available in SVN in
> readonly mode.
>
> Any objections or other suggestions?
>
> Regards
> Dennis
>

Re: Migrate all MyFaces projects to Git

[Dennis Kieselhorst]

On 2017-09-08 09:49, Dennis Kieselhorst  wrote:
> Trinidad will follow till Sunday.

Short update on Trinidad git migration.

I used the following command:
git svn clone --stdlayout --no-metadata --authors-file=authors.txt
https://svn.apache.org/repos/asf/myfaces/trinidad/ trinidad-tmp

This is running for almost a week now and consuming more and more memory
and cpu. I already used a cloud instance to speed this up.

I suggest to add --ignore-paths for all branches except trinidad-1.2.x,
trinidad-2.0.x and trinidad-2.1.x. All other branches haven't been
touched for at least three years. They will still be available in SVN in
readonly mode.

Any objections or other suggestions?

Regards
Dennis

Re: Migrate all MyFaces projects to Git

[Dennis Kieselhorst]

> Finally I have a working setup to migrate the subversion history to git.
> I already started with Tobago yesterday, Trinidad will follow till
Sunday.
>
> The result for Tobago is the following, will send another mail after
> having pushed this to Gitbox:

Tobago is finished: https://gitbox.apache.org/repos/asf/myfaces-tobago.git

Please no longer use svn for Tobago, I've requested to set it to readonly.

Cheers
Dennis

Re: Migrate all MyFaces projects to Git

[Dennis Kieselhorst]

Finally I have a working setup to migrate the subversion history to git.
I already started with Tobago yesterday, Trinidad will follow till Sunday.

The result for Tobago is the following, will send another mail after
having pushed this to Gitbox:
  origin/TOBAGO-1719
  origin/lofwyr
  origin/lofwyr@345942
  origin/lofwyr@394425
  origin/tags/1.0.9-RC1
  origin/tags/start
  origin/tags/start@345942
  origin/tags/start@345944
  origin/tags/start@394425
  origin/tags/tobago-1.0.10
  origin/tags/tobago-1.0.11
  origin/tags/tobago-1.0.12
  origin/tags/tobago-1.0.13
  origin/tags/tobago-1.0.14
  origin/tags/tobago-1.0.15
  origin/tags/tobago-1.0.16
  origin/tags/tobago-1.0.17
  origin/tags/tobago-1.0.18
  origin/tags/tobago-1.0.19
  origin/tags/tobago-1.0.20
  origin/tags/tobago-1.0.21
  origin/tags/tobago-1.0.22
  origin/tags/tobago-1.0.23
  origin/tags/tobago-1.0.24
  origin/tags/tobago-1.0.25
  origin/tags/tobago-1.0.26
  origin/tags/tobago-1.0.27
  origin/tags/tobago-1.0.28
  origin/tags/tobago-1.0.29
  origin/tags/tobago-1.0.30
  origin/tags/tobago-1.0.31
  origin/tags/tobago-1.0.32
  origin/tags/tobago-1.0.33
  origin/tags/tobago-1.0.34
  origin/tags/tobago-1.0.35
  origin/tags/tobago-1.0.36
  origin/tags/tobago-1.0.37
  origin/tags/tobago-1.0.38
  origin/tags/tobago-1.0.39
  origin/tags/tobago-1.0.40
  origin/tags/tobago-1.0.40-SNAPSHOT
  origin/tags/tobago-1.0.41
  origin/tags/tobago-1.0.42
  origin/tags/tobago-1.0.7
  origin/tags/tobago-1.0.8
  origin/tags/tobago-1.0.9
  origin/tags/tobago-1.0.9-RC1
  origin/tags/tobago-1.5.0
  origin/tags/tobago-1.5.0-alpha-1
  origin/tags/tobago-1.5.0-alpha-2
  origin/tags/tobago-1.5.0-beta-1
  origin/tags/tobago-1.5.0-beta-2
  origin/tags/tobago-1.5.1
  origin/tags/tobago-1.5.10
  origin/tags/tobago-1.5.11
  origin/tags/tobago-1.5.12
  origin/tags/tobago-1.5.13
  origin/tags/tobago-1.5.2
  origin/tags/tobago-1.5.3
  origin/tags/tobago-1.5.4
  origin/tags/tobago-1.5.5
  origin/tags/tobago-1.5.6
  origin/tags/tobago-1.5.7
  origin/tags/tobago-1.5.8
  origin/tags/tobago-1.5.9
  origin/tags/tobago-1.6.0-beta-1
  origin/tags/tobago-1.6.0-beta-2
  origin/tags/tobago-2.0.0
  origin/tags/tobago-2.0.0-alpha-1
  origin/tags/tobago-2.0.0-alpha-2
  origin/tags/tobago-2.0.0-alpha-3
  origin/tags/tobago-2.0.0-beta-1
  origin/tags/tobago-2.0.0-beta-2
  origin/tags/tobago-2.0.0-beta-3
  origin/tags/tobago-2.0.0-beta-4
  origin/tags/tobago-2.0.1
  origin/tags/tobago-2.0.10
  origin/tags/tobago-2.0.2
  origin/tags/tobago-2.0.3
  origin/tags/tobago-2.0.4
  origin/tags/tobago-2.0.5
  origin/tags/tobago-2.0.6
  origin/tags/tobago-2.0.7
  origin/tags/tobago-2.0.8
  origin/tags/tobago-2.0.8.TEST
  origin/tags/tobago-2.0.9
  origin/tags/tobago-2.0.9.TEST
  origin/tags/tobago-2.1.0
  origin/tags/tobago-3.0.0
  origin/tags/tobago-3.0.0-alpha-1
  origin/tags/tobago-3.0.0-alpha-2
  origin/tags/tobago-3.0.0-alpha-3
  origin/tags/tobago-3.0.0-alpha-4
  origin/tags/tobago-3.0.0-alpha-5
  origin/tags/tobago-3.0.0-alpha-6
  origin/tags/tobago-3.0.0-alpha-7
  origin/tags/tobago-3.0.0-beta-1
  origin/tags/tobago-3.0.1
  origin/tags/tobago-3.0.2
  origin/tags/tobago-3.0.3
  origin/tags/tobago-3.0.4
  origin/tags/tobago-3.0.5
  origin/tags/tobago_1_0_0
  origin/tags/tobago_1_0_0@346356
  origin/tags/tobago_1_0_0@394425
  origin/tags/tobago_1_0_1
  origin/tags/tobago_1_0_1@346360
  origin/tags/tobago_1_0_1@394425
  origin/tags/tobago_1_0_2
  origin/tags/tobago_1_0_2@346372
  origin/tags/tobago_1_0_2@394425
  origin/tags/tobago_1_0_3
  origin/tags/tobago_1_0_3@346511
  origin/tags/tobago_1_0_3@394425
  origin/tags/tobago_1_0_4
  origin/tags/tobago_1_0_4@346520
  origin/tags/tobago_1_0_4@394425
  origin/tags/tobago_1_0_5
  origin/tags/tobago_1_0_5@347230
  origin/tags/tobago_1_0_5@394425
  origin/tags/tobago_1_0_6
  origin/tags/tobago_1_0_6@347498
  origin/tags/tobago_1_0_6@394425
  origin/tags/tobago_before_vb_for_all
  origin/tags/tobago_before_vb_for_all@346141
  origin/tags/tobago_before_vb_for_all@394425
  origin/tobago-1.0.x
  origin/tobago-1.1.x-progress-layout
  origin/tobago-1.5.x
  origin/tobago-1.6.x-old-apt-generator
  origin/tobago-1.6.x-old-facelets
  origin/tobago-2.0.x
  origin/tobago-3.0.x
  origin/tobago-3.0.x-before-bootstrap-for-all-renderers
  origin/tobago-3.0.x-develop-standard-ajax
  origin/tobago-tree-table
  origin/trunk
  origin/trunk@394425

Regards
Dennis

Re: Migrate all MyFaces projects to Git

[Bernd Bohmann]

The repos are online:

https://gitbox.apache.org/repos/asf/myfaces-tobago.git

https://github.com/apache/myfaces-tobago


https://gitbox.apache.org/repos/asf/myfaces-trinidad.git

https://github.com/apache/myfaces-trinidad


But the myfaces-committers list is a little bit short.

https://github.com/orgs/apache/teams/myfaces-committers/members


PLEASE  visit

https://gitbox.apache.org/setup/

and merge your Apache and GitHub account

that we can schedule the svn repo move to git

Regards


Bernd

On Tue, Aug 15, 2017 at 6:04 PM, Bernd Bohmann  wrote:

> issue created
>
> https://issues.apache.org/jira/browse/INFRA-14883
>
> Regards
>
> Bernd
>
> On Thu, Aug 10, 2017 at 9:45 PM, Dennis Kieselhorst 
> wrote:
>
>> Lazy consensus is fine, please go ahead and file an infra issue. It will
>> take some time anyway.
>>
>
>

Re: Migrate all MyFaces projects to Git

[Bernd Bohmann]

issue created

https://issues.apache.org/jira/browse/INFRA-14883

Regards

Bernd

On Thu, Aug 10, 2017 at 9:45 PM, Dennis Kieselhorst  wrote:

> Lazy consensus is fine, please go ahead and file an infra issue. It will
> take some time anyway.
>

Re: Migrate all MyFaces projects to Git

[Dennis Kieselhorst]

Lazy consensus is fine, please go ahead and file an infra issue. It will
take some time anyway.

Re: Migrate all MyFaces projects to Git

[Bernd Bohmann]

Proposal migration to git:
We should request migration to gitbox without issues support on github.
I would like to keep Jira as bugtracking tool. We can revisit this later.
We should migrate only active maintained projects.
Candidates are:
Tobago and Trinidad
MyFaces Core

Any objections?
Is a formal vote required or is lazy consensus enough?

I can request Tobago and Trinidad migration. If successful and after some
testing we can request migration of Core as well.

Regards

Bernd


On Fri, Jul 28, 2017 at 11:04 AM, Dora Rajappan 
wrote:

> mojarra download url of github.com is also mirror and it actually goes to
> java.net domain.
> https://maven.java.net/content/repositories/releases/
> org/glassfish/javax.faces/2.3.2/
>
>
> On Friday, July 28, 2017, 2:22:03 PM GMT+5:30, Dora Rajappan <
> dorarajap...@yahoo.com> wrote:
>
>
> Hi ,
>
>  Thanks for the information on Git hub for apache. I found mojarra latest
> downloads in github.com and understand the domain is a trusted site from
> this discussion. https://github.com/javaserverfaces/mojarra/
> releases/tag/2.3.2.
>
> Nice to know myfaces projects are going to apache git. I can find the
> myfaces mirrors already in github.com!
>
> Thanks & Regards,
> Dora Rajappan,
> 9986201824.
>
>
>
> On Thursday, July 27, 2017, 9:03:55 PM GMT+5:30, Bernd Bohmann <
> bernd.bohm...@googlemail.com> wrote:
>
>
> Hello Dora
>
> this is not possible for apache projects
>
> see: https://git-wip-us.apache.org
>
> and
>
> https://www.apache.org/dev/writable-git
>
> but there are readonly mirrors at https://github.com/apache
>
> Regards
>
> Bernd
>
> On Thu, Jul 27, 2017 at 4:10 PM, Dora Rajappan 
> wrote:
>
> Is it github.com where you are going to migrate myfaces to?
>
>
> On Thursday, July 27, 2017, 7:06:06 PM GMT+5:30, Bernd Bohmann <
> bernd.bohm...@googlemail.com> wrote:
>
>
> for Trinidad as well
>
> On Thu, Jul 27, 2017 at 2:29 PM, Udo Schnurpfeil 
> wrote:
>
> Hi,
>
> for Tobago I think, we can do it now!
>
> Regards,
>
> Udo
>
> Am 27.07.17 um 13:03 schrieb Bernd Bohmann:
> > Ok
> >
> > we have some agreement about moving to git.
> > Now we should define some time line.
> > Any suggestions from the active subprojects?
> >
> > Something like
> > 'I would like to move to git after blah blah release'
> > 'I would like to move now'
> > 'I would like to move in 2 weeks'
> > or whatever
> >
> > I can support the migration to git.
> >
> > Regards
> >
> > Bernd
> >
> >
> >
> >
> > On Thu, Apr 20, 2017 at 5:16 PM, Kito Mann  > > wrote:
> >
> > Ah, this may be why it's worked for me -- smaller projects with
> > defined release cycles.
> >
> > Anyway, I never meant to imply that git == git flow. We will need
> > some sort of process, though, and the DeltaSpike one seems like a
> > good place to start.
> >
> > ___
> >
> > Kito D. Mann | @kito99 | Author, JSF in Action
> > Web Components, Polymer, JSF, PrimeFaces, Java EE training and
> > consulting
> > Virtua, Inc. | virtua.tech
> > JSFCentral.com | @jsfcentral | knowesis.io  -
> > fresh Web Components info
> > +1 203-998-0403 
> >
> > * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
> > 
> > * Listen to the Enterprise Java Newscast:
> http://enterprisejavanews.com
> >
> >
> > On Thu, Apr 20, 2017 at 8:02 AM, Mark Struberg  > > wrote:
> >
> > gitflow is pure pita ;)
> > It basically only works for companies where you have a single
> > manager who decides what goes in and what not.
> >
> > But GIT != gitflow. gitflow has nothing to do with the GIT scm
> > itself, but is just a fancy name for a development process with
> > an explicit build-branch and a build-master.
> >
> > +0 on moving to GIT.
> > SVN works good enough imo, but GIT ofc also would work.
> >
> > LIeGrue,
> > strub
> >
> > > Am 19.04.2017 um 12:57 schrieb Kito Mann  >  > :
> > >
> > > +1
> > >
> > > Wha's wrong with GitFlow?
> > >
> > > ___
> > >
> > > Kito D. Mann | @kito99 | Author, JSF in Action
> > > Web Components, Polymer, JSF, PrimeFaces, Java EE training and
> > consulting
> > > Virtua, Inc. | virtua.tech
> > > JSFCentral.com | @jsfcentral | knowesis.io
> >  - fresh Web Components info
> > > +1 203-998-0403 
> > >
> > > * See me speak at the ng-conf April 5th-8th:
> http://bit.ly/2mw7HBj
> > > * Listen to the Enterprise Java Newscast:
> > http://enterprisejavanews.com
> > >
> > >
> > > On 

Re: Migrate all MyFaces projects to Git

[Dora Rajappan]

mojarra download url of github.com is also mirror and it actually goes to 
java.net 
domain.https://maven.java.net/content/repositories/releases/org/glassfish/javax.faces/2.3.2/


On Friday, July 28, 2017, 2:22:03 PM GMT+5:30, Dora Rajappan 
 wrote:

Hi ,
 Thanks for the information on Git hub for apache. I found mojarra latest 
downloads in github.com and understand the domain is a trusted site from this 
discussion. https://github.com/javaserverfaces/mojarra/releases/tag/2.3.2.    
Nice to know myfaces projects are going to apache git. I can find the myfaces 
mirrors already in github.com!
Thanks & Regards,Dora Rajappan,9986201824.


On Thursday, July 27, 2017, 9:03:55 PM GMT+5:30, Bernd Bohmann 
 wrote:

Hello Dora
this is not possible for apache projects
see: https://git-wip-us.apache.org

and
https://www.apache.org/dev/writable-git

but there are readonly mirrors at https://github.com/apache
Regards
Bernd
On Thu, Jul 27, 2017 at 4:10 PM, Dora Rajappan  wrote:

Is it github.com where you are going to migrate myfaces to?

On Thursday, July 27, 2017, 7:06:06 PM GMT+5:30, Bernd Bohmann 
 wrote:

for Trinidad as well
On Thu, Jul 27, 2017 at 2:29 PM, Udo Schnurpfeil  wrote:

Hi,

for Tobago I think, we can do it now!

Regards,

Udo

Am 27.07.17 um 13:03 schrieb Bernd Bohmann:
> Ok
>
> we have some agreement about moving to git.
> Now we should define some time line.
> Any suggestions from the active subprojects?
>
> Something like
> 'I would like to move to git after blah blah release'
> 'I would like to move now'
> 'I would like to move in 2 weeks'
> or whatever
>
> I can support the migration to git.
>
> Regards
>
> Bernd
>
>
>
>
> On Thu, Apr 20, 2017 at 5:16 PM, Kito Mann  > wrote:
>
>     Ah, this may be why it's worked for me -- smaller projects with
>     defined release cycles.
>
>     Anyway, I never meant to imply that git == git flow. We will need
>     some sort of process, though, and the DeltaSpike one seems like a
>     good place to start.
>
>     ___
>
>     Kito D. Mann | @kito99 | Author, JSF in Action
>     Web Components, Polymer, JSF, PrimeFaces, Java EE training and
>     consulting
>     Virtua, Inc. | virtua.tech
>     JSFCentral.com | @jsfcentral | knowesis.io  -
>     fresh Web Components info
>     +1 203-998-0403 
>
>     * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
>     
>     * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
>
>
>     On Thu, Apr 20, 2017 at 8:02 AM, Mark Struberg      > wrote:
>
>         gitflow is pure pita ;)
>         It basically only works for companies where you have a single
>         manager who decides what goes in and what not.
>
>         But GIT != gitflow. gitflow has nothing to do with the GIT scm
>         itself, but is just a fancy name for a development process with
>         an explicit build-branch and a build-master.
>
>         +0 on moving to GIT.
>         SVN works good enough imo, but GIT ofc also would work.
>
>         LIeGrue,
>         strub
>
>         > Am 19.04.2017 um 12:57 schrieb Kito Mann           > :
>         >
>         > +1
>         >
>         > Wha's wrong with GitFlow?
>         >
>         > ___
>         >
>         > Kito D. Mann | @kito99 | Author, JSF in Action
>         > Web Components, Polymer, JSF, PrimeFaces, Java EE training and
>         consulting
>         > Virtua, Inc. | virtua.tech
>         > JSFCentral.com | @jsfcentral | knowesis.io
>          - fresh Web Components info
>         > +1 203-998-0403 
>         >
>         > * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
>         > * Listen to the Enterprise Java Newscast:
>         http://enterprisejavanews.com
>         >
>         >
>         > On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann
>                  > wrote:
>         > Hello
>         >
>         > I think the changes will be not so complicated. The deltaspike
>         pom looks nice :-)
>         > If someone talks about git-flow process i'm out.
>         >
>         > Regards
>         >
>         > Bernd
>         >
>         > On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe
>         > wrote:
>         > +1
>         >
>         > Change the release process is a pain, but I agree there are
>         some benefits moving to git.
>         >
>         > But when I see here:
>         >
>         > https://github.com/apache/ myfaces
>         
>         >
>         > It says:
>         >

Re: Migrate all MyFaces projects to Git

[Dora Rajappan]

Hi ,
 Thanks for the information on Git hub for apache. I found mojarra latest 
downloads in github.com and understand the domain is a trusted site from this 
discussion. https://github.com/javaserverfaces/mojarra/releases/tag/2.3.2.    
Nice to know myfaces projects are going to apache git. I can find the myfaces 
mirrors already in github.com!
Thanks & Regards,Dora Rajappan,9986201824.


On Thursday, July 27, 2017, 9:03:55 PM GMT+5:30, Bernd Bohmann 
 wrote:

Hello Dora
this is not possible for apache projects
see: https://git-wip-us.apache.org

and
https://www.apache.org/dev/writable-git

but there are readonly mirrors at https://github.com/apache
Regards
Bernd
On Thu, Jul 27, 2017 at 4:10 PM, Dora Rajappan  wrote:

Is it github.com where you are going to migrate myfaces to?

On Thursday, July 27, 2017, 7:06:06 PM GMT+5:30, Bernd Bohmann 
 wrote:

for Trinidad as well
On Thu, Jul 27, 2017 at 2:29 PM, Udo Schnurpfeil  wrote:

Hi,

for Tobago I think, we can do it now!

Regards,

Udo

Am 27.07.17 um 13:03 schrieb Bernd Bohmann:
> Ok
>
> we have some agreement about moving to git.
> Now we should define some time line.
> Any suggestions from the active subprojects?
>
> Something like
> 'I would like to move to git after blah blah release'
> 'I would like to move now'
> 'I would like to move in 2 weeks'
> or whatever
>
> I can support the migration to git.
>
> Regards
>
> Bernd
>
>
>
>
> On Thu, Apr 20, 2017 at 5:16 PM, Kito Mann  > wrote:
>
>     Ah, this may be why it's worked for me -- smaller projects with
>     defined release cycles.
>
>     Anyway, I never meant to imply that git == git flow. We will need
>     some sort of process, though, and the DeltaSpike one seems like a
>     good place to start.
>
>     ___
>
>     Kito D. Mann | @kito99 | Author, JSF in Action
>     Web Components, Polymer, JSF, PrimeFaces, Java EE training and
>     consulting
>     Virtua, Inc. | virtua.tech
>     JSFCentral.com | @jsfcentral | knowesis.io  -
>     fresh Web Components info
>     +1 203-998-0403 
>
>     * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
>     
>     * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
>
>
>     On Thu, Apr 20, 2017 at 8:02 AM, Mark Struberg      > wrote:
>
>         gitflow is pure pita ;)
>         It basically only works for companies where you have a single
>         manager who decides what goes in and what not.
>
>         But GIT != gitflow. gitflow has nothing to do with the GIT scm
>         itself, but is just a fancy name for a development process with
>         an explicit build-branch and a build-master.
>
>         +0 on moving to GIT.
>         SVN works good enough imo, but GIT ofc also would work.
>
>         LIeGrue,
>         strub
>
>         > Am 19.04.2017 um 12:57 schrieb Kito Mann           > :
>         >
>         > +1
>         >
>         > Wha's wrong with GitFlow?
>         >
>         > ___
>         >
>         > Kito D. Mann | @kito99 | Author, JSF in Action
>         > Web Components, Polymer, JSF, PrimeFaces, Java EE training and
>         consulting
>         > Virtua, Inc. | virtua.tech
>         > JSFCentral.com | @jsfcentral | knowesis.io
>          - fresh Web Components info
>         > +1 203-998-0403 
>         >
>         > * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
>         > * Listen to the Enterprise Java Newscast:
>         http://enterprisejavanews.com
>         >
>         >
>         > On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann
>                  > wrote:
>         > Hello
>         >
>         > I think the changes will be not so complicated. The deltaspike
>         pom looks nice :-)
>         > If someone talks about git-flow process i'm out.
>         >
>         > Regards
>         >
>         > Bernd
>         >
>         > On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe
>         > wrote:
>         > +1
>         >
>         > Change the release process is a pain, but I agree there are
>         some benefits moving to git.
>         >
>         > But when I see here:
>         >
>         > https://github.com/apache/ myfaces
>         
>         >
>         > It says:
>         >
>         > mirrored from git://git.apache.org/myfaces. git
>         
>         >
>         > But I have never checked where that file is or how to change it.
>         >
>         > Looking in deltaspike, the svn repo only has the site 

Re: Migrate all MyFaces projects to Git

[Bernd Bohmann]

And we need a formal vote

Regards

Bernd

On Thu, Jul 27, 2017 at 8:47 PM, Bernd Bohmann  wrote:

> We should define a workflow like this:
>
> https://wiki.apache.org/nutch/UsingGit
>
> And we should aware that commiters must enable 2 factor auth on Github and
> add the github id to the apache profile
> see: https://gitbox.apache.org/setup/
>
> On Thu, Jul 27, 2017 at 7:09 PM, Bernd Bohmann <
> bernd.bohm...@googlemail.com> wrote:
>
>> I'm fine with everything with better integration.
>>
>> Bernd
>>
>>
>> Am 27.07.2017 17:50 schrieb "Dennis Kieselhorst" :
>>
>> In the meantime infra launched Gitbox with even better GitHub
>> integration, so in my view we should use that from the beginning:
>> http://gitbox.apache.org
>>
>>
>>
>

Re: Migrate all MyFaces projects to Git

[Bernd Bohmann]

We should define a workflow like this:

https://wiki.apache.org/nutch/UsingGit

And we should aware that commiters must enable 2 factor auth on Github and
add the github id to the apache profile
see: https://gitbox.apache.org/setup/

On Thu, Jul 27, 2017 at 7:09 PM, Bernd Bohmann  wrote:

> I'm fine with everything with better integration.
>
> Bernd
>
>
> Am 27.07.2017 17:50 schrieb "Dennis Kieselhorst" :
>
> In the meantime infra launched Gitbox with even better GitHub
> integration, so in my view we should use that from the beginning:
> http://gitbox.apache.org
>
>
>

Re: Migrate all MyFaces projects to Git

[Bernd Bohmann]

I'm fine with everything with better integration.

Bernd

Am 27.07.2017 17:50 schrieb "Dennis Kieselhorst" :

In the meantime infra launched Gitbox with even better GitHub
integration, so in my view we should use that from the beginning:
http://gitbox.apache.org

Re: Migrate all MyFaces projects to Git

[Dennis Kieselhorst]

In the meantime infra launched Gitbox with even better GitHub
integration, so in my view we should use that from the beginning:
http://gitbox.apache.org

Re: Migrate all MyFaces projects to Git

[Bernd Bohmann]

Hello Dora

this is not possible for apache projects

see: https://git-wip-us.apache.org

and

https://www.apache.org/dev/writable-git

but there are readonly mirrors at https://github.com/apache

Regards

Bernd

On Thu, Jul 27, 2017 at 4:10 PM, Dora Rajappan 
wrote:

> Is it github.com where you are going to migrate myfaces to?
>
>
> On Thursday, July 27, 2017, 7:06:06 PM GMT+5:30, Bernd Bohmann <
> bernd.bohm...@googlemail.com> wrote:
>
>
> for Trinidad as well
>
> On Thu, Jul 27, 2017 at 2:29 PM, Udo Schnurpfeil 
> wrote:
>
> Hi,
>
> for Tobago I think, we can do it now!
>
> Regards,
>
> Udo
>
> Am 27.07.17 um 13:03 schrieb Bernd Bohmann:
> > Ok
> >
> > we have some agreement about moving to git.
> > Now we should define some time line.
> > Any suggestions from the active subprojects?
> >
> > Something like
> > 'I would like to move to git after blah blah release'
> > 'I would like to move now'
> > 'I would like to move in 2 weeks'
> > or whatever
> >
> > I can support the migration to git.
> >
> > Regards
> >
> > Bernd
> >
> >
> >
> >
> > On Thu, Apr 20, 2017 at 5:16 PM, Kito Mann  > > wrote:
> >
> > Ah, this may be why it's worked for me -- smaller projects with
> > defined release cycles.
> >
> > Anyway, I never meant to imply that git == git flow. We will need
> > some sort of process, though, and the DeltaSpike one seems like a
> > good place to start.
> >
> > ___
> >
> > Kito D. Mann | @kito99 | Author, JSF in Action
> > Web Components, Polymer, JSF, PrimeFaces, Java EE training and
> > consulting
> > Virtua, Inc. | virtua.tech
> > JSFCentral.com | @jsfcentral | knowesis.io  -
> > fresh Web Components info
> > +1 203-998-0403 
> >
> > * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
> > 
> > * Listen to the Enterprise Java Newscast:
> http://enterprisejavanews.com
> >
> >
> > On Thu, Apr 20, 2017 at 8:02 AM, Mark Struberg  > > wrote:
> >
> > gitflow is pure pita ;)
> > It basically only works for companies where you have a single
> > manager who decides what goes in and what not.
> >
> > But GIT != gitflow. gitflow has nothing to do with the GIT scm
> > itself, but is just a fancy name for a development process with
> > an explicit build-branch and a build-master.
> >
> > +0 on moving to GIT.
> > SVN works good enough imo, but GIT ofc also would work.
> >
> > LIeGrue,
> > strub
> >
> > > Am 19.04.2017 um 12:57 schrieb Kito Mann  > > :
> > >
> > > +1
> > >
> > > Wha's wrong with GitFlow?
> > >
> > > ___
> > >
> > > Kito D. Mann | @kito99 | Author, JSF in Action
> > > Web Components, Polymer, JSF, PrimeFaces, Java EE training and
> > consulting
> > > Virtua, Inc. | virtua.tech
> > > JSFCentral.com | @jsfcentral | knowesis.io
> >  - fresh Web Components info
> > > +1 203-998-0403 
> > >
> > > * See me speak at the ng-conf April 5th-8th:
> http://bit.ly/2mw7HBj
> > > * Listen to the Enterprise Java Newscast:
> > http://enterprisejavanews.com
> > >
> > >
> > > On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann
> >  >  >> wrote:
> > > Hello
> > >
> > > I think the changes will be not so complicated. The deltaspike
> > pom looks nice :-)
> > > If someone talks about git-flow process i'm out.
> > >
> > > Regards
> > >
> > > Bernd
> > >
> > > On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe
> > > wrote:
> > > +1
> > >
> > > Change the release process is a pain, but I agree there are
> > some benefits moving to git.
> > >
> > > But when I see here:
> > >
> > > https://github.com/apache/ myfaces
> 
> >  >
> > >
> > > It says:
> > >
> > > mirrored from git://git.apache.org/myfaces. git
> 
> >  >
> > >
> > > But I have never checked where that file is or how to change
> it.
> > >
> > > Looking in deltaspike, the svn repo only has the site (for the
> > CMS) and 

Re: Migrate all MyFaces projects to Git

[Dora Rajappan]

Is it github.com where you are going to migrate myfaces to?

On Thursday, July 27, 2017, 7:06:06 PM GMT+5:30, Bernd Bohmann 
 wrote:

for Trinidad as well
On Thu, Jul 27, 2017 at 2:29 PM, Udo Schnurpfeil  wrote:

Hi,

for Tobago I think, we can do it now!

Regards,

Udo

Am 27.07.17 um 13:03 schrieb Bernd Bohmann:
> Ok
>
> we have some agreement about moving to git.
> Now we should define some time line.
> Any suggestions from the active subprojects?
>
> Something like
> 'I would like to move to git after blah blah release'
> 'I would like to move now'
> 'I would like to move in 2 weeks'
> or whatever
>
> I can support the migration to git.
>
> Regards
>
> Bernd
>
>
>
>
> On Thu, Apr 20, 2017 at 5:16 PM, Kito Mann  > wrote:
>
>     Ah, this may be why it's worked for me -- smaller projects with
>     defined release cycles.
>
>     Anyway, I never meant to imply that git == git flow. We will need
>     some sort of process, though, and the DeltaSpike one seems like a
>     good place to start.
>
>     ___
>
>     Kito D. Mann | @kito99 | Author, JSF in Action
>     Web Components, Polymer, JSF, PrimeFaces, Java EE training and
>     consulting
>     Virtua, Inc. | virtua.tech
>     JSFCentral.com | @jsfcentral | knowesis.io  -
>     fresh Web Components info
>     +1 203-998-0403 
>
>     * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
>     
>     * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
>
>
>     On Thu, Apr 20, 2017 at 8:02 AM, Mark Struberg      > wrote:
>
>         gitflow is pure pita ;)
>         It basically only works for companies where you have a single
>         manager who decides what goes in and what not.
>
>         But GIT != gitflow. gitflow has nothing to do with the GIT scm
>         itself, but is just a fancy name for a development process with
>         an explicit build-branch and a build-master.
>
>         +0 on moving to GIT.
>         SVN works good enough imo, but GIT ofc also would work.
>
>         LIeGrue,
>         strub
>
>         > Am 19.04.2017 um 12:57 schrieb Kito Mann          > :
>         >
>         > +1
>         >
>         > Wha's wrong with GitFlow?
>         >
>         > ___
>         >
>         > Kito D. Mann | @kito99 | Author, JSF in Action
>         > Web Components, Polymer, JSF, PrimeFaces, Java EE training and
>         consulting
>         > Virtua, Inc. | virtua.tech
>         > JSFCentral.com | @jsfcentral | knowesis.io
>          - fresh Web Components info
>         > +1 203-998-0403 
>         >
>         > * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
>         > * Listen to the Enterprise Java Newscast:
>         http://enterprisejavanews.com
>         >
>         >
>         > On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann
>                  > wrote:
>         > Hello
>         >
>         > I think the changes will be not so complicated. The deltaspike
>         pom looks nice :-)
>         > If someone talks about git-flow process i'm out.
>         >
>         > Regards
>         >
>         > Bernd
>         >
>         > On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe
>         > wrote:
>         > +1
>         >
>         > Change the release process is a pain, but I agree there are
>         some benefits moving to git.
>         >
>         > But when I see here:
>         >
>         > https://github.com/apache/ myfaces
>         
>         >
>         > It says:
>         >
>         > mirrored from git://git.apache.org/myfaces. git
>         
>         >
>         > But I have never checked where that file is or how to change it.
>         >
>         > Looking in deltaspike, the svn repo only has the site (for the
>         CMS) and the source code lives on git. If that so, we still need
>         the svn, so I agree it is a good idea to move only some
>         subprojects to git.
>         >
>         > regards,
>         >
>         > Leonardo Uribe
>         >
>         >
>         >       Virus-free. www.avast.com 
>         >
>         > 2017-04-17 11:40 GMT-05:00 Grant Smith          > :
>         > +1
>         >
>         > Couldn't agree more.
>         >
>         > Grant Smith - V.P. Information Technology
>         > Marathon Computer Systems, LLC.
>         >
>         > On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann
>         

Re: Migrate all MyFaces projects to Git

[Bernd Bohmann]

for Trinidad as well

On Thu, Jul 27, 2017 at 2:29 PM, Udo Schnurpfeil  wrote:

> Hi,
>
> for Tobago I think, we can do it now!
>
> Regards,
>
> Udo
>
> Am 27.07.17 um 13:03 schrieb Bernd Bohmann:
> > Ok
> >
> > we have some agreement about moving to git.
> > Now we should define some time line.
> > Any suggestions from the active subprojects?
> >
> > Something like
> > 'I would like to move to git after blah blah release'
> > 'I would like to move now'
> > 'I would like to move in 2 weeks'
> > or whatever
> >
> > I can support the migration to git.
> >
> > Regards
> >
> > Bernd
> >
> >
> >
> >
> > On Thu, Apr 20, 2017 at 5:16 PM, Kito Mann  > > wrote:
> >
> > Ah, this may be why it's worked for me -- smaller projects with
> > defined release cycles.
> >
> > Anyway, I never meant to imply that git == git flow. We will need
> > some sort of process, though, and the DeltaSpike one seems like a
> > good place to start.
> >
> > ___
> >
> > Kito D. Mann | @kito99 | Author, JSF in Action
> > Web Components, Polymer, JSF, PrimeFaces, Java EE training and
> > consulting
> > Virtua, Inc. | virtua.tech
> > JSFCentral.com | @jsfcentral | knowesis.io  -
> > fresh Web Components info
> > +1 203-998-0403 
> >
> > * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
> > 
> > * Listen to the Enterprise Java Newscast:
> http://enterprisejavanews.com
> >
> >
> > On Thu, Apr 20, 2017 at 8:02 AM, Mark Struberg  > > wrote:
> >
> > gitflow is pure pita ;)
> > It basically only works for companies where you have a single
> > manager who decides what goes in and what not.
> >
> > But GIT != gitflow. gitflow has nothing to do with the GIT scm
> > itself, but is just a fancy name for a development process with
> > an explicit build-branch and a build-master.
> >
> > +0 on moving to GIT.
> > SVN works good enough imo, but GIT ofc also would work.
> >
> > LIeGrue,
> > strub
> >
> > > Am 19.04.2017 um 12:57 schrieb Kito Mann  > >:
> > >
> > > +1
> > >
> > > Wha's wrong with GitFlow?
> > >
> > > ___
> > >
> > > Kito D. Mann | @kito99 | Author, JSF in Action
> > > Web Components, Polymer, JSF, PrimeFaces, Java EE training and
> > consulting
> > > Virtua, Inc. | virtua.tech
> > > JSFCentral.com | @jsfcentral | knowesis.io
> >  - fresh Web Components info
> > > +1 203-998-0403 
> > >
> > > * See me speak at the ng-conf April 5th-8th:
> http://bit.ly/2mw7HBj
> > > * Listen to the Enterprise Java Newscast:
> > http://enterprisejavanews.com
> > >
> > >
> > > On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann
> >  > > wrote:
> > > Hello
> > >
> > > I think the changes will be not so complicated. The deltaspike
> > pom looks nice :-)
> > > If someone talks about git-flow process i'm out.
> > >
> > > Regards
> > >
> > > Bernd
> > >
> > > On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe
> > > wrote:
> > > +1
> > >
> > > Change the release process is a pain, but I agree there are
> > some benefits moving to git.
> > >
> > > But when I see here:
> > >
> > > https://github.com/apache/myfaces
> > 
> > >
> > > It says:
> > >
> > > mirrored from git://git.apache.org/myfaces.git
> > 
> > >
> > > But I have never checked where that file is or how to change
> it.
> > >
> > > Looking in deltaspike, the svn repo only has the site (for the
> > CMS) and the source code lives on git. If that so, we still need
> > the svn, so I agree it is a good idea to move only some
> > subprojects to git.
> > >
> > > regards,
> > >
> > > Leonardo Uribe
> > >
> > >
> > >   Virus-free. www.avast.com 
> > >
> > > 2017-04-17 11:40 GMT-05:00 Grant Smith  > >:
> > > +1
> > >
> > > Couldn't agree more.
> > >
> > > Grant Smith - V.P. Information Technology
> > > Marathon Computer Systems, LLC.
> > >
> >   

Re: Migrate all MyFaces projects to Git

[Udo Schnurpfeil]

Hi,

for Tobago I think, we can do it now!

Regards,

Udo

Am 27.07.17 um 13:03 schrieb Bernd Bohmann:
> Ok
> 
> we have some agreement about moving to git.
> Now we should define some time line.
> Any suggestions from the active subprojects?
> 
> Something like 
> 'I would like to move to git after blah blah release'
> 'I would like to move now'
> 'I would like to move in 2 weeks'
> or whatever
> 
> I can support the migration to git.
> 
> Regards 
> 
> Bernd
> 
> 
>  
> 
> On Thu, Apr 20, 2017 at 5:16 PM, Kito Mann  > wrote:
> 
> Ah, this may be why it's worked for me -- smaller projects with
> defined release cycles.
> 
> Anyway, I never meant to imply that git == git flow. We will need
> some sort of process, though, and the DeltaSpike one seems like a
> good place to start.
> 
> ___
> 
> Kito D. Mann | @kito99 | Author, JSF in Action
> Web Components, Polymer, JSF, PrimeFaces, Java EE training and
> consulting
> Virtua, Inc. | virtua.tech 
> JSFCentral.com | @jsfcentral | knowesis.io  -
> fresh Web Components info
> +1 203-998-0403 
> 
> * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
> 
> * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
> 
> 
> On Thu, Apr 20, 2017 at 8:02 AM, Mark Struberg  > wrote:
> 
> gitflow is pure pita ;)
> It basically only works for companies where you have a single
> manager who decides what goes in and what not.
> 
> But GIT != gitflow. gitflow has nothing to do with the GIT scm
> itself, but is just a fancy name for a development process with
> an explicit build-branch and a build-master.
> 
> +0 on moving to GIT.
> SVN works good enough imo, but GIT ofc also would work.
> 
> LIeGrue,
> strub
> 
> > Am 19.04.2017 um 12:57 schrieb Kito Mann  >:
> >
> > +1
> >
> > Wha's wrong with GitFlow?
> >
> > ___
> >
> > Kito D. Mann | @kito99 | Author, JSF in Action
> > Web Components, Polymer, JSF, PrimeFaces, Java EE training and
> consulting
> > Virtua, Inc. | virtua.tech
> > JSFCentral.com | @jsfcentral | knowesis.io
>  - fresh Web Components info
> > +1 203-998-0403 
> >
> > * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
> > * Listen to the Enterprise Java Newscast:
> http://enterprisejavanews.com
> >
> >
> > On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann
>  > wrote:
> > Hello
> >
> > I think the changes will be not so complicated. The deltaspike
> pom looks nice :-)
> > If someone talks about git-flow process i'm out.
> >
> > Regards
> >
> > Bernd
> >
> > On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe
> > wrote:
> > +1
> >
> > Change the release process is a pain, but I agree there are
> some benefits moving to git.
> >
> > But when I see here:
> >
> > https://github.com/apache/myfaces
> 
> >
> > It says:
> >
> > mirrored from git://git.apache.org/myfaces.git
> 
> >
> > But I have never checked where that file is or how to change it.
> >
> > Looking in deltaspike, the svn repo only has the site (for the
> CMS) and the source code lives on git. If that so, we still need
> the svn, so I agree it is a good idea to move only some
> subprojects to git.
> >
> > regards,
> >
> > Leonardo Uribe
> >
> >
> >   Virus-free. www.avast.com 
> >
> > 2017-04-17 11:40 GMT-05:00 Grant Smith  >:
> > +1
> >
> > Couldn't agree more.
> >
> > Grant Smith - V.P. Information Technology
> > Marathon Computer Systems, LLC.
> >
> > On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann
> >
> wrote:
> > From my side a big
> >
> > +1
> >
> > I'm still happy with subversion but for others the
> collaboration is easier and the project visibility a little bit
> better.
> 

Re: Migrate all MyFaces projects to Git

[Bernd Bohmann]

Ok

we have some agreement about moving to git.
Now we should define some time line.
Any suggestions from the active subprojects?

Something like
'I would like to move to git after blah blah release'
'I would like to move now'
'I would like to move in 2 weeks'
or whatever

I can support the migration to git.

Regards

Bernd




On Thu, Apr 20, 2017 at 5:16 PM, Kito Mann  wrote:

> Ah, this may be why it's worked for me -- smaller projects with defined
> release cycles.
>
> Anyway, I never meant to imply that git == git flow. We will need some
> sort of process, though, and the DeltaSpike one seems like a good place to
> start.
>
> ___
>
> Kito D. Mann | @kito99 | Author, JSF in Action
> Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting
> Virtua, Inc. | virtua.tech
> JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
> +1 203-998-0403 <(203)%20998-0403>
>
> * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
> 
> * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
>
>
> On Thu, Apr 20, 2017 at 8:02 AM, Mark Struberg  wrote:
>
>> gitflow is pure pita ;)
>> It basically only works for companies where you have a single manager who
>> decides what goes in and what not.
>>
>> But GIT != gitflow. gitflow has nothing to do with the GIT scm itself,
>> but is just a fancy name for a development process with an explicit
>> build-branch and a build-master.
>>
>> +0 on moving to GIT.
>> SVN works good enough imo, but GIT ofc also would work.
>>
>> LIeGrue,
>> strub
>>
>> > Am 19.04.2017 um 12:57 schrieb Kito Mann :
>> >
>> > +1
>> >
>> > Wha's wrong with GitFlow?
>> >
>> > ___
>> >
>> > Kito D. Mann | @kito99 | Author, JSF in Action
>> > Web Components, Polymer, JSF, PrimeFaces, Java EE training and
>> consulting
>> > Virtua, Inc. | virtua.tech
>> > JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
>> > +1 203-998-0403
>> >
>> > * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
>> > * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
>> >
>> >
>> > On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann <
>> bernd.bohm...@googlemail.com> wrote:
>> > Hello
>> >
>> > I think the changes will be not so complicated. The deltaspike pom
>> looks nice :-)
>> > If someone talks about git-flow process i'm out.
>> >
>> > Regards
>> >
>> > Bernd
>> >
>> > On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe 
>> wrote:
>> > +1
>> >
>> > Change the release process is a pain, but I agree there are some
>> benefits moving to git.
>> >
>> > But when I see here:
>> >
>> > https://github.com/apache/myfaces
>> >
>> > It says:
>> >
>> > mirrored from git://git.apache.org/myfaces.git
>> >
>> > But I have never checked where that file is or how to change it.
>> >
>> > Looking in deltaspike, the svn repo only has the site (for the CMS) and
>> the source code lives on git. If that so, we still need the svn, so I agree
>> it is a good idea to move only some subprojects to git.
>> >
>> > regards,
>> >
>> > Leonardo Uribe
>> >
>> >
>> >   Virus-free. www.avast.com
>> >
>> > 2017-04-17 11:40 GMT-05:00 Grant Smith :
>> > +1
>> >
>> > Couldn't agree more.
>> >
>> > Grant Smith - V.P. Information Technology
>> > Marathon Computer Systems, LLC.
>> >
>> > On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann <
>> bernd.bohm...@atanion.com> wrote:
>> > From my side a big
>> >
>> > +1
>> >
>> > I'm still happy with subversion but for others the collaboration is
>> easier and the project visibility a little bit better.
>> >
>> > Regards
>> >
>> > Bernd
>> >
>> > Am 13.04.2017 09:41 schrieb "Thomas Andraschko" <
>> andraschko.tho...@gmail.com>:
>> > +0
>> > I usually just work on MF core and there it doesn't make much
>> difference.
>> >
>> > 2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst :
>> > Hi,
>> >
>> > have you ever thought of migrating to Git? I see more and more Apache
>> > projects moving. In the past SVN or Git didn't make any difference to me
>> > but now I'm thinking that as an Open Source project you need to be
>> > present on GitHub to get Pull Requests from the community. It's much
>> > more fun contributing there than attaching patches to JIRA issues.
>> >
>> > We could start with Trinidad and Tobago to avoid conflicts with the 2.3
>> > release.
>> >
>> > Cheers
>> > Dennis
>> >
>> >
>> >
>> >
>> >
>>
>>
>

Re: Migrate all MyFaces projects to Git

[Kito Mann]

Ah, this may be why it's worked for me -- smaller projects with defined
release cycles.

Anyway, I never meant to imply that git == git flow. We will need some sort
of process, though, and the DeltaSpike one seems like a good place to start.

___

Kito D. Mann | @kito99 | Author, JSF in Action
Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting
Virtua, Inc. | virtua.tech
JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
+1 203-998-0403

* See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj

* Listen to the Enterprise Java Newscast: http://enterprisejavanews.com


On Thu, Apr 20, 2017 at 8:02 AM, Mark Struberg  wrote:

> gitflow is pure pita ;)
> It basically only works for companies where you have a single manager who
> decides what goes in and what not.
>
> But GIT != gitflow. gitflow has nothing to do with the GIT scm itself, but
> is just a fancy name for a development process with an explicit
> build-branch and a build-master.
>
> +0 on moving to GIT.
> SVN works good enough imo, but GIT ofc also would work.
>
> LIeGrue,
> strub
>
> > Am 19.04.2017 um 12:57 schrieb Kito Mann :
> >
> > +1
> >
> > Wha's wrong with GitFlow?
> >
> > ___
> >
> > Kito D. Mann | @kito99 | Author, JSF in Action
> > Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting
> > Virtua, Inc. | virtua.tech
> > JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
> > +1 203-998-0403
> >
> > * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
> > * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
> >
> >
> > On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann <
> bernd.bohm...@googlemail.com> wrote:
> > Hello
> >
> > I think the changes will be not so complicated. The deltaspike pom looks
> nice :-)
> > If someone talks about git-flow process i'm out.
> >
> > Regards
> >
> > Bernd
> >
> > On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe 
> wrote:
> > +1
> >
> > Change the release process is a pain, but I agree there are some
> benefits moving to git.
> >
> > But when I see here:
> >
> > https://github.com/apache/myfaces
> >
> > It says:
> >
> > mirrored from git://git.apache.org/myfaces.git
> >
> > But I have never checked where that file is or how to change it.
> >
> > Looking in deltaspike, the svn repo only has the site (for the CMS) and
> the source code lives on git. If that so, we still need the svn, so I agree
> it is a good idea to move only some subprojects to git.
> >
> > regards,
> >
> > Leonardo Uribe
> >
> >
> >   Virus-free. www.avast.com
> >
> > 2017-04-17 11:40 GMT-05:00 Grant Smith :
> > +1
> >
> > Couldn't agree more.
> >
> > Grant Smith - V.P. Information Technology
> > Marathon Computer Systems, LLC.
> >
> > On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann <
> bernd.bohm...@atanion.com> wrote:
> > From my side a big
> >
> > +1
> >
> > I'm still happy with subversion but for others the collaboration is
> easier and the project visibility a little bit better.
> >
> > Regards
> >
> > Bernd
> >
> > Am 13.04.2017 09:41 schrieb "Thomas Andraschko" <
> andraschko.tho...@gmail.com>:
> > +0
> > I usually just work on MF core and there it doesn't make much difference.
> >
> > 2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst :
> > Hi,
> >
> > have you ever thought of migrating to Git? I see more and more Apache
> > projects moving. In the past SVN or Git didn't make any difference to me
> > but now I'm thinking that as an Open Source project you need to be
> > present on GitHub to get Pull Requests from the community. It's much
> > more fun contributing there than attaching patches to JIRA issues.
> >
> > We could start with Trinidad and Tobago to avoid conflicts with the 2.3
> > release.
> >
> > Cheers
> > Dennis
> >
> >
> >
> >
> >
>
>

Re: Migrate all MyFaces projects to Git

[Bill Lucy]

I prefer working with GIT, and agree with the points already made in this
thread about its benefits.  I'm not sure how much pain a meaningful
transition will cause - from that perspective, starting with the components
is a great idea.

+1

Regards,
Bill

On Thu, Apr 20, 2017 at 8:24 AM, Bernd Bohmann  wrote:

> Thanks Mark
>
> gitflow is not solving any technical problem. It's just more complicated
> and it's looks good from a high level perspective.
>
> Regards
>
> Bernd
>
> On Thu, Apr 20, 2017 at 2:02 PM, Mark Struberg  wrote:
>
>> gitflow is pure pita ;)
>> It basically only works for companies where you have a single manager who
>> decides what goes in and what not.
>>
>> But GIT != gitflow. gitflow has nothing to do with the GIT scm itself,
>> but is just a fancy name for a development process with an explicit
>> build-branch and a build-master.
>>
>> +0 on moving to GIT.
>> SVN works good enough imo, but GIT ofc also would work.
>>
>> LIeGrue,
>> strub
>>
>> > Am 19.04.2017 um 12:57 schrieb Kito Mann :
>> >
>> > +1
>> >
>> > Wha's wrong with GitFlow?
>> >
>> > ___
>> >
>> > Kito D. Mann | @kito99 | Author, JSF in Action
>> > Web Components, Polymer, JSF, PrimeFaces, Java EE training and
>> consulting
>> > Virtua, Inc. | virtua.tech
>> > JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
>> > +1 203-998-0403
>> >
>> > * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
>> > * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
>> >
>> >
>> > On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann <
>> bernd.bohm...@googlemail.com> wrote:
>> > Hello
>> >
>> > I think the changes will be not so complicated. The deltaspike pom
>> looks nice :-)
>> > If someone talks about git-flow process i'm out.
>> >
>> > Regards
>> >
>> > Bernd
>> >
>> > On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe 
>> wrote:
>> > +1
>> >
>> > Change the release process is a pain, but I agree there are some
>> benefits moving to git.
>> >
>> > But when I see here:
>> >
>> > https://github.com/apache/myfaces
>> >
>> > It says:
>> >
>> > mirrored from git://git.apache.org/myfaces.git
>> >
>> > But I have never checked where that file is or how to change it.
>> >
>> > Looking in deltaspike, the svn repo only has the site (for the CMS) and
>> the source code lives on git. If that so, we still need the svn, so I agree
>> it is a good idea to move only some subprojects to git.
>> >
>> > regards,
>> >
>> > Leonardo Uribe
>> >
>> >
>> >   Virus-free. www.avast.com
>> >
>> > 2017-04-17 11:40 GMT-05:00 Grant Smith :
>> > +1
>> >
>> > Couldn't agree more.
>> >
>> > Grant Smith - V.P. Information Technology
>> > Marathon Computer Systems, LLC.
>> >
>> > On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann <
>> bernd.bohm...@atanion.com> wrote:
>> > From my side a big
>> >
>> > +1
>> >
>> > I'm still happy with subversion but for others the collaboration is
>> easier and the project visibility a little bit better.
>> >
>> > Regards
>> >
>> > Bernd
>> >
>> > Am 13.04.2017 09:41 schrieb "Thomas Andraschko" <
>> andraschko.tho...@gmail.com>:
>> > +0
>> > I usually just work on MF core and there it doesn't make much
>> difference.
>> >
>> > 2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst :
>> > Hi,
>> >
>> > have you ever thought of migrating to Git? I see more and more Apache
>> > projects moving. In the past SVN or Git didn't make any difference to me
>> > but now I'm thinking that as an Open Source project you need to be
>> > present on GitHub to get Pull Requests from the community. It's much
>> > more fun contributing there than attaching patches to JIRA issues.
>> >
>> > We could start with Trinidad and Tobago to avoid conflicts with the 2.3
>> > release.
>> >
>> > Cheers
>> > Dennis
>> >
>> >
>> >
>> >
>> >
>>
>>
>

Re: Migrate all MyFaces projects to Git

[Bernd Bohmann]

Thanks Mark

gitflow is not solving any technical problem. It's just more complicated
and it's looks good from a high level perspective.

Regards

Bernd

On Thu, Apr 20, 2017 at 2:02 PM, Mark Struberg  wrote:

> gitflow is pure pita ;)
> It basically only works for companies where you have a single manager who
> decides what goes in and what not.
>
> But GIT != gitflow. gitflow has nothing to do with the GIT scm itself, but
> is just a fancy name for a development process with an explicit
> build-branch and a build-master.
>
> +0 on moving to GIT.
> SVN works good enough imo, but GIT ofc also would work.
>
> LIeGrue,
> strub
>
> > Am 19.04.2017 um 12:57 schrieb Kito Mann :
> >
> > +1
> >
> > Wha's wrong with GitFlow?
> >
> > ___
> >
> > Kito D. Mann | @kito99 | Author, JSF in Action
> > Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting
> > Virtua, Inc. | virtua.tech
> > JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
> > +1 203-998-0403
> >
> > * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
> > * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
> >
> >
> > On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann <
> bernd.bohm...@googlemail.com> wrote:
> > Hello
> >
> > I think the changes will be not so complicated. The deltaspike pom looks
> nice :-)
> > If someone talks about git-flow process i'm out.
> >
> > Regards
> >
> > Bernd
> >
> > On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe 
> wrote:
> > +1
> >
> > Change the release process is a pain, but I agree there are some
> benefits moving to git.
> >
> > But when I see here:
> >
> > https://github.com/apache/myfaces
> >
> > It says:
> >
> > mirrored from git://git.apache.org/myfaces.git
> >
> > But I have never checked where that file is or how to change it.
> >
> > Looking in deltaspike, the svn repo only has the site (for the CMS) and
> the source code lives on git. If that so, we still need the svn, so I agree
> it is a good idea to move only some subprojects to git.
> >
> > regards,
> >
> > Leonardo Uribe
> >
> >
> >   Virus-free. www.avast.com
> >
> > 2017-04-17 11:40 GMT-05:00 Grant Smith :
> > +1
> >
> > Couldn't agree more.
> >
> > Grant Smith - V.P. Information Technology
> > Marathon Computer Systems, LLC.
> >
> > On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann <
> bernd.bohm...@atanion.com> wrote:
> > From my side a big
> >
> > +1
> >
> > I'm still happy with subversion but for others the collaboration is
> easier and the project visibility a little bit better.
> >
> > Regards
> >
> > Bernd
> >
> > Am 13.04.2017 09:41 schrieb "Thomas Andraschko" <
> andraschko.tho...@gmail.com>:
> > +0
> > I usually just work on MF core and there it doesn't make much difference.
> >
> > 2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst :
> > Hi,
> >
> > have you ever thought of migrating to Git? I see more and more Apache
> > projects moving. In the past SVN or Git didn't make any difference to me
> > but now I'm thinking that as an Open Source project you need to be
> > present on GitHub to get Pull Requests from the community. It's much
> > more fun contributing there than attaching patches to JIRA issues.
> >
> > We could start with Trinidad and Tobago to avoid conflicts with the 2.3
> > release.
> >
> > Cheers
> > Dennis
> >
> >
> >
> >
> >
>
>

Re: Migrate all MyFaces projects to Git

[Mark Struberg]

gitflow is pure pita ;)
It basically only works for companies where you have a single manager who 
decides what goes in and what not. 

But GIT != gitflow. gitflow has nothing to do with the GIT scm itself, but is 
just a fancy name for a development process with an explicit build-branch and a 
build-master.

+0 on moving to GIT. 
SVN works good enough imo, but GIT ofc also would work.

LIeGrue,
strub

> Am 19.04.2017 um 12:57 schrieb Kito Mann :
> 
> +1
> 
> Wha's wrong with GitFlow?
> 
> ___
> 
> Kito D. Mann | @kito99 | Author, JSF in Action
> Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting
> Virtua, Inc. | virtua.tech 
> JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
> +1 203-998-0403
> 
> * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
> * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
> 
> 
> On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann  
> wrote:
> Hello
> 
> I think the changes will be not so complicated. The deltaspike pom looks nice 
> :-) 
> If someone talks about git-flow process i'm out.
> 
> Regards
> 
> Bernd
> 
> On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe  wrote:
> +1
> 
> Change the release process is a pain, but I agree there are some benefits 
> moving to git.
> 
> But when I see here:
> 
> https://github.com/apache/myfaces
> 
> It says:
> 
> mirrored from git://git.apache.org/myfaces.git
> 
> But I have never checked where that file is or how to change it.
> 
> Looking in deltaspike, the svn repo only has the site (for the CMS) and the 
> source code lives on git. If that so, we still need the svn, so I agree it is 
> a good idea to move only some subprojects to git.
> 
> regards,
> 
> Leonardo Uribe
> 
> 
>   Virus-free. www.avast.com
> 
> 2017-04-17 11:40 GMT-05:00 Grant Smith :
> +1 
> 
> Couldn't agree more.
> 
> Grant Smith - V.P. Information Technology
> Marathon Computer Systems, LLC.
> 
> On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann  
> wrote:
> From my side a big
> 
> +1
> 
> I'm still happy with subversion but for others the collaboration is easier 
> and the project visibility a little bit better.
> 
> Regards
> 
> Bernd
> 
> Am 13.04.2017 09:41 schrieb "Thomas Andraschko" :
> +0
> I usually just work on MF core and there it doesn't make much difference.
> 
> 2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst :
> Hi,
> 
> have you ever thought of migrating to Git? I see more and more Apache
> projects moving. In the past SVN or Git didn't make any difference to me
> but now I'm thinking that as an Open Source project you need to be
> present on GitHub to get Pull Requests from the community. It's much
> more fun contributing there than attaching patches to JIRA issues.
> 
> We could start with Trinidad and Tobago to avoid conflicts with the 2.3
> release.
> 
> Cheers
> Dennis
> 
> 
> 
> 
> 

Re: Migrate all MyFaces projects to Git

[Gerhard Petracek]

hi @ all,

just fyi:
[1] works very well for ds since the beginning.

regards,
gerhard

[1] https://deltaspike.apache.org/suggested-git-workflows.html



2017-04-19 14:45 GMT+02:00 Kito Mann :

> Hello Bernd,
>
> I like GitFlow for coordinating with multiple developers. However, if
> everyone is sending pull requests anyway, it's not quite as useful. It
> makes sense when you have multiple developers that are committing to a
> "develop" branch and provides guidelines for working with master for new
> releases and hot fixes.
>
> ___
>
> Kito D. Mann | @kito99 | Author, JSF in Action
> Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting
> Virtua, Inc. | virtua.tech
> JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
> +1 203-998-0403 <(203)%20998-0403>
>
> * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
> 
> * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
>
>
> On Wed, Apr 19, 2017 at 8:38 AM, Bernd Bohmann <
> bernd.bohm...@googlemail.com> wrote:
>
>> Until now, nobody could explain me the real technical improvement of
>> GitFlow.
>> We are talking about using git and not GitFlow. Git does not require
>> GitFlow
>>
>> At Apache we are only using process as much as needed and not as possible!
>> And my personal advice is:
>> Start with a model as simple as possible.
>>
>> Regards
>>
>> Bernd
>>
>>
>>
>>
>>
>>
>>
>> On Wed, Apr 19, 2017 at 12:57 PM, Kito Mann  wrote:
>>
>>> +1
>>>
>>> Wha's wrong with GitFlow?
>>>
>>> ___
>>>
>>> Kito D. Mann | @kito99 | Author, JSF in Action
>>> Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting
>>> Virtua, Inc. | virtua.tech
>>> JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
>>> +1 203-998-0403 <(203)%20998-0403>
>>>
>>> * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
>>> 
>>> * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
>>>
>>>
>>> On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann <
>>> bernd.bohm...@googlemail.com> wrote:
>>>
 Hello

 I think the changes will be not so complicated. The deltaspike pom
 looks nice :-)
 If someone talks about git-flow process i'm out.

 Regards

 Bernd

 On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe 
 wrote:

> +1
>
> Change the release process is a pain, but I agree there are some
> benefits moving to git.
>
> But when I see here:
>
> https://github.com/apache/myfaces
>
> It says:
>
> mirrored from git://git.apache.org/myfaces.git
>
> But I have never checked where that file is or how to change it.
>
> Looking in deltaspike, the svn repo only has the site (for the CMS)
> and the source code lives on git. If that so, we still need the svn, so I
> agree it is a good idea to move only some subprojects to git.
>
> regards,
>
> Leonardo Uribe
>
>
>
> 
>  Virus-free.
> www.avast.com
> 
> <#m_-6826021186946778376_m_-135240448576325838_m_-1665615671155989291_m_312095376341812428_m_228356912083513587_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> 2017-04-17 11:40 GMT-05:00 Grant Smith :
>
>> +1
>>
>> Couldn't agree more.
>>
>> Grant Smith - V.P. Information Technology
>> Marathon Computer Systems, LLC.
>>
>> On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann <
>> bernd.bohm...@atanion.com> wrote:
>>
>>> From my side a big
>>>
>>> +1
>>>
>>> I'm still happy with subversion but for others the collaboration is
>>> easier and the project visibility a little bit better.
>>>
>>> Regards
>>>
>>> Bernd
>>>
>>> Am 13.04.2017 09:41 schrieb "Thomas Andraschko" <
>>> andraschko.tho...@gmail.com>:
>>>
 +0
 I usually just work on MF core and there it doesn't make much
 difference.

 2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst :

> Hi,
>
> have you ever thought of migrating to Git? I see more and more
> Apache
> projects moving. In the past SVN or Git didn't make any difference
> to me
> but now I'm thinking that as an Open Source project you need to be
> present on GitHub to get Pull Requests from the community. It's
> much
> more fun contributing there than attaching patches to JIRA issues.
>
> We could start with Trinidad and Tobago to avoid conflicts with
> the 2.3
> release.
>
> Cheers
> Dennis

Re: Migrate all MyFaces projects to Git

[Kito Mann]

Hello Bernd,

I like GitFlow for coordinating with multiple developers. However, if
everyone is sending pull requests anyway, it's not quite as useful. It
makes sense when you have multiple developers that are committing to a
"develop" branch and provides guidelines for working with master for new
releases and hot fixes.

___

Kito D. Mann | @kito99 | Author, JSF in Action
Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting
Virtua, Inc. | virtua.tech
JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
+1 203-998-0403

* See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj

* Listen to the Enterprise Java Newscast: http://enterprisejavanews.com


On Wed, Apr 19, 2017 at 8:38 AM, Bernd Bohmann  wrote:

> Until now, nobody could explain me the real technical improvement of
> GitFlow.
> We are talking about using git and not GitFlow. Git does not require
> GitFlow
>
> At Apache we are only using process as much as needed and not as possible!
> And my personal advice is:
> Start with a model as simple as possible.
>
> Regards
>
> Bernd
>
>
>
>
>
>
>
> On Wed, Apr 19, 2017 at 12:57 PM, Kito Mann  wrote:
>
>> +1
>>
>> Wha's wrong with GitFlow?
>>
>> ___
>>
>> Kito D. Mann | @kito99 | Author, JSF in Action
>> Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting
>> Virtua, Inc. | virtua.tech
>> JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
>> +1 203-998-0403 <(203)%20998-0403>
>>
>> * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
>> 
>> * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
>>
>>
>> On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann <
>> bernd.bohm...@googlemail.com> wrote:
>>
>>> Hello
>>>
>>> I think the changes will be not so complicated. The deltaspike pom looks
>>> nice :-)
>>> If someone talks about git-flow process i'm out.
>>>
>>> Regards
>>>
>>> Bernd
>>>
>>> On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe 
>>> wrote:
>>>
 +1

 Change the release process is a pain, but I agree there are some
 benefits moving to git.

 But when I see here:

 https://github.com/apache/myfaces

 It says:

 mirrored from git://git.apache.org/myfaces.git

 But I have never checked where that file is or how to change it.

 Looking in deltaspike, the svn repo only has the site (for the CMS) and
 the source code lives on git. If that so, we still need the svn, so I agree
 it is a good idea to move only some subprojects to git.

 regards,

 Leonardo Uribe



 
  Virus-free.
 www.avast.com
 
 <#m_-135240448576325838_m_-1665615671155989291_m_312095376341812428_m_228356912083513587_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

 2017-04-17 11:40 GMT-05:00 Grant Smith :

> +1
>
> Couldn't agree more.
>
> Grant Smith - V.P. Information Technology
> Marathon Computer Systems, LLC.
>
> On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann <
> bernd.bohm...@atanion.com> wrote:
>
>> From my side a big
>>
>> +1
>>
>> I'm still happy with subversion but for others the collaboration is
>> easier and the project visibility a little bit better.
>>
>> Regards
>>
>> Bernd
>>
>> Am 13.04.2017 09:41 schrieb "Thomas Andraschko" <
>> andraschko.tho...@gmail.com>:
>>
>>> +0
>>> I usually just work on MF core and there it doesn't make much
>>> difference.
>>>
>>> 2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst :
>>>
 Hi,

 have you ever thought of migrating to Git? I see more and more
 Apache
 projects moving. In the past SVN or Git didn't make any difference
 to me
 but now I'm thinking that as an Open Source project you need to be
 present on GitHub to get Pull Requests from the community. It's much
 more fun contributing there than attaching patches to JIRA issues.

 We could start with Trinidad and Tobago to avoid conflicts with the
 2.3
 release.

 Cheers
 Dennis

>>>
>>>
>

>>>
>>
>

Re: Migrate all MyFaces projects to Git

[Bernd Bohmann]

Until now, nobody could explain me the real technical improvement of
GitFlow.
We are talking about using git and not GitFlow. Git does not require
GitFlow

At Apache we are only using process as much as needed and not as possible!
And my personal advice is:
Start with a model as simple as possible.

Regards

Bernd







On Wed, Apr 19, 2017 at 12:57 PM, Kito Mann  wrote:

> +1
>
> Wha's wrong with GitFlow?
>
> ___
>
> Kito D. Mann | @kito99 | Author, JSF in Action
> Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting
> Virtua, Inc. | virtua.tech
> JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
> +1 203-998-0403 <(203)%20998-0403>
>
> * See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj
> 
> * Listen to the Enterprise Java Newscast: http://enterprisejavanews.com
>
>
> On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann <
> bernd.bohm...@googlemail.com> wrote:
>
>> Hello
>>
>> I think the changes will be not so complicated. The deltaspike pom looks
>> nice :-)
>> If someone talks about git-flow process i'm out.
>>
>> Regards
>>
>> Bernd
>>
>> On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe 
>> wrote:
>>
>>> +1
>>>
>>> Change the release process is a pain, but I agree there are some
>>> benefits moving to git.
>>>
>>> But when I see here:
>>>
>>> https://github.com/apache/myfaces
>>>
>>> It says:
>>>
>>> mirrored from git://git.apache.org/myfaces.git
>>>
>>> But I have never checked where that file is or how to change it.
>>>
>>> Looking in deltaspike, the svn repo only has the site (for the CMS) and
>>> the source code lives on git. If that so, we still need the svn, so I agree
>>> it is a good idea to move only some subprojects to git.
>>>
>>> regards,
>>>
>>> Leonardo Uribe
>>>
>>>
>>>
>>> 
>>>  Virus-free.
>>> www.avast.com
>>> 
>>> <#m_-1665615671155989291_m_312095376341812428_m_228356912083513587_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>>
>>> 2017-04-17 11:40 GMT-05:00 Grant Smith :
>>>
 +1

 Couldn't agree more.

 Grant Smith - V.P. Information Technology
 Marathon Computer Systems, LLC.

 On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann <
 bernd.bohm...@atanion.com> wrote:

> From my side a big
>
> +1
>
> I'm still happy with subversion but for others the collaboration is
> easier and the project visibility a little bit better.
>
> Regards
>
> Bernd
>
> Am 13.04.2017 09:41 schrieb "Thomas Andraschko" <
> andraschko.tho...@gmail.com>:
>
>> +0
>> I usually just work on MF core and there it doesn't make much
>> difference.
>>
>> 2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst :
>>
>>> Hi,
>>>
>>> have you ever thought of migrating to Git? I see more and more Apache
>>> projects moving. In the past SVN or Git didn't make any difference
>>> to me
>>> but now I'm thinking that as an Open Source project you need to be
>>> present on GitHub to get Pull Requests from the community. It's much
>>> more fun contributing there than attaching patches to JIRA issues.
>>>
>>> We could start with Trinidad and Tobago to avoid conflicts with the
>>> 2.3
>>> release.
>>>
>>> Cheers
>>> Dennis
>>>
>>
>>

>>>
>>
>

Re: Migrate all MyFaces projects to Git

[Kito Mann]

+1

Wha's wrong with GitFlow?

___

Kito D. Mann | @kito99 | Author, JSF in Action
Web Components, Polymer, JSF, PrimeFaces, Java EE training and consulting
Virtua, Inc. | virtua.tech
JSFCentral.com | @jsfcentral | knowesis.io - fresh Web Components info
+1 203-998-0403

* See me speak at the ng-conf April 5th-8th: http://bit.ly/2mw7HBj

* Listen to the Enterprise Java Newscast: http://enterprisejavanews.com


On Wed, Apr 19, 2017 at 4:29 AM, Bernd Bohmann  wrote:

> Hello
>
> I think the changes will be not so complicated. The deltaspike pom looks
> nice :-)
> If someone talks about git-flow process i'm out.
>
> Regards
>
> Bernd
>
> On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe  wrote:
>
>> +1
>>
>> Change the release process is a pain, but I agree there are some benefits
>> moving to git.
>>
>> But when I see here:
>>
>> https://github.com/apache/myfaces
>>
>> It says:
>>
>> mirrored from git://git.apache.org/myfaces.git
>>
>> But I have never checked where that file is or how to change it.
>>
>> Looking in deltaspike, the svn repo only has the site (for the CMS) and
>> the source code lives on git. If that so, we still need the svn, so I agree
>> it is a good idea to move only some subprojects to git.
>>
>> regards,
>>
>> Leonardo Uribe
>>
>>
>>
>> 
>>  Virus-free.
>> www.avast.com
>> 
>> <#m_312095376341812428_m_228356912083513587_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>> 2017-04-17 11:40 GMT-05:00 Grant Smith :
>>
>>> +1
>>>
>>> Couldn't agree more.
>>>
>>> Grant Smith - V.P. Information Technology
>>> Marathon Computer Systems, LLC.
>>>
>>> On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann <
>>> bernd.bohm...@atanion.com> wrote:
>>>
 From my side a big

 +1

 I'm still happy with subversion but for others the collaboration is
 easier and the project visibility a little bit better.

 Regards

 Bernd

 Am 13.04.2017 09:41 schrieb "Thomas Andraschko" <
 andraschko.tho...@gmail.com>:

> +0
> I usually just work on MF core and there it doesn't make much
> difference.
>
> 2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst :
>
>> Hi,
>>
>> have you ever thought of migrating to Git? I see more and more Apache
>> projects moving. In the past SVN or Git didn't make any difference to
>> me
>> but now I'm thinking that as an Open Source project you need to be
>> present on GitHub to get Pull Requests from the community. It's much
>> more fun contributing there than attaching patches to JIRA issues.
>>
>> We could start with Trinidad and Tobago to avoid conflicts with the
>> 2.3
>> release.
>>
>> Cheers
>> Dennis
>>
>
>
>>>
>>
>

Re: Migrate all MyFaces projects to Git

[Bernd Bohmann]

Hello

I think the changes will be not so complicated. The deltaspike pom looks
nice :-)
If someone talks about git-flow process i'm out.

Regards

Bernd

On Wed, Apr 19, 2017 at 12:28 AM, Leonardo Uribe  wrote:

> +1
>
> Change the release process is a pain, but I agree there are some benefits
> moving to git.
>
> But when I see here:
>
> https://github.com/apache/myfaces
>
> It says:
>
> mirrored from git://git.apache.org/myfaces.git
>
> But I have never checked where that file is or how to change it.
>
> Looking in deltaspike, the svn repo only has the site (for the CMS) and
> the source code lives on git. If that so, we still need the svn, so I agree
> it is a good idea to move only some subprojects to git.
>
> regards,
>
> Leonardo Uribe
>
>
>
> 
>  Virus-free.
> www.avast.com
> 
> <#m_228356912083513587_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> 2017-04-17 11:40 GMT-05:00 Grant Smith :
>
>> +1
>>
>> Couldn't agree more.
>>
>> Grant Smith - V.P. Information Technology
>> Marathon Computer Systems, LLC.
>>
>> On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann > > wrote:
>>
>>> From my side a big
>>>
>>> +1
>>>
>>> I'm still happy with subversion but for others the collaboration is
>>> easier and the project visibility a little bit better.
>>>
>>> Regards
>>>
>>> Bernd
>>>
>>> Am 13.04.2017 09:41 schrieb "Thomas Andraschko" <
>>> andraschko.tho...@gmail.com>:
>>>
 +0
 I usually just work on MF core and there it doesn't make much
 difference.

 2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst :

> Hi,
>
> have you ever thought of migrating to Git? I see more and more Apache
> projects moving. In the past SVN or Git didn't make any difference to
> me
> but now I'm thinking that as an Open Source project you need to be
> present on GitHub to get Pull Requests from the community. It's much
> more fun contributing there than attaching patches to JIRA issues.
>
> We could start with Trinidad and Tobago to avoid conflicts with the 2.3
> release.
>
> Cheers
> Dennis
>


>>
>

Re: Migrate all MyFaces projects to Git

[Leonardo Uribe]

+1

Change the release process is a pain, but I agree there are some benefits
moving to git.

But when I see here:

https://github.com/apache/myfaces

It says:

mirrored from git://git.apache.org/myfaces.git

But I have never checked where that file is or how to change it.

Looking in deltaspike, the svn repo only has the site (for the CMS) and the
source code lives on git. If that so, we still need the svn, so I agree it
is a good idea to move only some subprojects to git.

regards,

Leonardo Uribe



Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2017-04-17 11:40 GMT-05:00 Grant Smith :

> +1
>
> Couldn't agree more.
>
> Grant Smith - V.P. Information Technology
> Marathon Computer Systems, LLC.
>
> On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann 
> wrote:
>
>> From my side a big
>>
>> +1
>>
>> I'm still happy with subversion but for others the collaboration is
>> easier and the project visibility a little bit better.
>>
>> Regards
>>
>> Bernd
>>
>> Am 13.04.2017 09:41 schrieb "Thomas Andraschko" <
>> andraschko.tho...@gmail.com>:
>>
>>> +0
>>> I usually just work on MF core and there it doesn't make much difference.
>>>
>>> 2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst :
>>>
 Hi,

 have you ever thought of migrating to Git? I see more and more Apache
 projects moving. In the past SVN or Git didn't make any difference to me
 but now I'm thinking that as an Open Source project you need to be
 present on GitHub to get Pull Requests from the community. It's much
 more fun contributing there than attaching patches to JIRA issues.

 We could start with Trinidad and Tobago to avoid conflicts with the 2.3
 release.

 Cheers
 Dennis

>>>
>>>
>

Re: Migrate all MyFaces projects to Git

[Grant Smith]

+1

Couldn't agree more.

Grant Smith - V.P. Information Technology
Marathon Computer Systems, LLC.

On Thu, Apr 13, 2017 at 2:39 AM, Bernd Bohmann 
wrote:

> From my side a big
>
> +1
>
> I'm still happy with subversion but for others the collaboration is easier
> and the project visibility a little bit better.
>
> Regards
>
> Bernd
>
> Am 13.04.2017 09:41 schrieb "Thomas Andraschko" <
> andraschko.tho...@gmail.com>:
>
>> +0
>> I usually just work on MF core and there it doesn't make much difference.
>>
>> 2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst :
>>
>>> Hi,
>>>
>>> have you ever thought of migrating to Git? I see more and more Apache
>>> projects moving. In the past SVN or Git didn't make any difference to me
>>> but now I'm thinking that as an Open Source project you need to be
>>> present on GitHub to get Pull Requests from the community. It's much
>>> more fun contributing there than attaching patches to JIRA issues.
>>>
>>> We could start with Trinidad and Tobago to avoid conflicts with the 2.3
>>> release.
>>>
>>> Cheers
>>> Dennis
>>>
>>
>>

Re: Migrate all MyFaces projects to Git

[Bernd Bohmann]

>From my side a big

+1

I'm still happy with subversion but for others the collaboration is easier
and the project visibility a little bit better.

Regards

Bernd

Am 13.04.2017 09:41 schrieb "Thomas Andraschko" :

> +0
> I usually just work on MF core and there it doesn't make much difference.
>
> 2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst :
>
>> Hi,
>>
>> have you ever thought of migrating to Git? I see more and more Apache
>> projects moving. In the past SVN or Git didn't make any difference to me
>> but now I'm thinking that as an Open Source project you need to be
>> present on GitHub to get Pull Requests from the community. It's much
>> more fun contributing there than attaching patches to JIRA issues.
>>
>> We could start with Trinidad and Tobago to avoid conflicts with the 2.3
>> release.
>>
>> Cheers
>> Dennis
>>
>
>

Re: Migrate all MyFaces projects to Git

[Thomas Andraschko]

+0
I usually just work on MF core and there it doesn't make much difference.

2017-04-13 8:57 GMT+02:00 Dennis Kieselhorst :

> Hi,
>
> have you ever thought of migrating to Git? I see more and more Apache
> projects moving. In the past SVN or Git didn't make any difference to me
> but now I'm thinking that as an Open Source project you need to be
> present on GitHub to get Pull Requests from the community. It's much
> more fun contributing there than attaching patches to JIRA issues.
>
> We could start with Trinidad and Tobago to avoid conflicts with the 2.3
> release.
>
> Cheers
> Dennis
>