Broken tools from GIT migration

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

Broken tools from GIT migration

Andrea Pescetti-2
Unless the discussion about this happened off-list, the SVN to Git
migration resulted in breaking some tools without any plans to fix them.
I'm listing the ones I found so far, and the course of action I propose
for each. As usual, 72 hours for lazy consensus before acting (but I can
take care of all I propose below).

1) Fisheye https://fisheye.apache.org/changelog/openoffice

"We have an instance of Atlassian FishEye for source browsing,
searching, reporting and visualization of main trunk (main development
area)." (source.html)

Proposal: link to Github https://github.com/apache/openoffice for the
short term; when Opengrok is ready, link to it; tell Infra to explicitly
kill the Fisheye instance. Or (if someone wants to take over since they
do use Fisheye) ask Infra to link it to the new repository.

2) OpenGrok

This is already dead. I know Peter has it on his radar but I think we
only have the empty VM for the time being. So, no action pending
restoration of the service, and when it is restored it will of course
point to Git.

3) Open Hub tracker https://www.openhub.net/p/openoffice

"Our SVN tree is read by the Open Hub tracker to generate some various
statistics. Note that the migration from the legacy Mercurial repository
to SVN at Apache has caused pre-existing files to be double-counted. But
the contribution history should be intact." (source.html)

Proposal: tell them to please stop tracking; their data have always been
wrong anyway, as they were tracking the wrong branches. If someone still
wants OpenOffice to be on OpenHub instead, please take over, find who
the admins are in our PMC and ask them to put the new repository URL.

4) Bugzilla annotator

Most of you should be aware that writing "#i123456#" in a commit log
would automatically post that commit to Bugzilla as a comment for issue
123456. The magic is done by a Python bot running on the MWiki server
and parsing SVN logs.

Proposal: stop the Python script (obviously); if at least one other
committer writes here that he thinks this feature is useful, I can
modify the Python script to use Git and/or turn it into a Git hook; this
may require substantial work.

5) Devtools

Our devtools are code and should have been included in the migration to
Git. I didn't notice they were left out.

Proposal: talk to Infra to see if we can easily add them retaining
history, or just copy them over from SVN and push this to Git. We could
discuss for ages where they belong to, but some of them are definitely
related to the source tree and as first approximation I would move
(i.e., "keep") them there.

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Broken tools from GIT migration

Peter Kovacs-3

1) fisheye
The instance has been broken for quite some time. I had a talk with infra, and my impression was they are not very engaged to fix it.

Proposal: ask infra to fix it with migration to git or to remove us from fisheye.
2) openGrok
Software is installed. Git migration is on todo list. See cwiki.
Not workable atm. :(
3) open hub
+1
4)Bugzilla annotator
Yea we should update. I am not sure on the solution thought. Not mission critical more convenience. There was a discussion but I am not sure on results.
5) dev tools.
Imho should be not mixed with source code.
We can request own repository. I think even for each tool.

I will post link for todo list later today., OK?


Am 15. August 2019 08:34:55 MESZ schrieb Andrea Pescetti <[hidden email]>:

>Unless the discussion about this happened off-list, the SVN to Git
>migration resulted in breaking some tools without any plans to fix
>them.
>I'm listing the ones I found so far, and the course of action I propose
>
>for each. As usual, 72 hours for lazy consensus before acting (but I
>can
>take care of all I propose below).
>
>1) Fisheye https://fisheye.apache.org/changelog/openoffice
>
>"We have an instance of Atlassian FishEye for source browsing,
>searching, reporting and visualization of main trunk (main development
>area)." (source.html)
>
>Proposal: link to Github https://github.com/apache/openoffice for the
>short term; when Opengrok is ready, link to it; tell Infra to
>explicitly
>kill the Fisheye instance. Or (if someone wants to take over since they
>
>do use Fisheye) ask Infra to link it to the new repository.
>
>2) OpenGrok
>
>This is already dead. I know Peter has it on his radar but I think we
>only have the empty VM for the time being. So, no action pending
>restoration of the service, and when it is restored it will of course
>point to Git.
>
>3) Open Hub tracker https://www.openhub.net/p/openoffice
>
>"Our SVN tree is read by the Open Hub tracker to generate some various
>statistics. Note that the migration from the legacy Mercurial
>repository
>to SVN at Apache has caused pre-existing files to be double-counted.
>But
>the contribution history should be intact." (source.html)
>
>Proposal: tell them to please stop tracking; their data have always
>been
>wrong anyway, as they were tracking the wrong branches. If someone
>still
>wants OpenOffice to be on OpenHub instead, please take over, find who
>the admins are in our PMC and ask them to put the new repository URL.
>
>4) Bugzilla annotator
>
>Most of you should be aware that writing "#i123456#" in a commit log
>would automatically post that commit to Bugzilla as a comment for issue
>
>123456. The magic is done by a Python bot running on the MWiki server
>and parsing SVN logs.
>
>Proposal: stop the Python script (obviously); if at least one other
>committer writes here that he thinks this feature is useful, I can
>modify the Python script to use Git and/or turn it into a Git hook;
>this
>may require substantial work.
>
>5) Devtools
>
>Our devtools are code and should have been included in the migration to
>
>Git. I didn't notice they were left out.
>
>Proposal: talk to Infra to see if we can easily add them retaining
>history, or just copy them over from SVN and push this to Git. We could
>
>discuss for ages where they belong to, but some of them are definitely
>related to the source tree and as first approximation I would move
>(i.e., "keep") them there.
>
>Regards,
>   Andrea.
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [hidden email]
>For additional commands, e-mail: [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Broken tools from GIT migration

Matthias Seidel
In reply to this post by Andrea Pescetti-2
Hi Andrea,

Am 15.08.19 um 08:34 schrieb Andrea Pescetti:

> Unless the discussion about this happened off-list, the SVN to Git
> migration resulted in breaking some tools without any plans to fix
> them. I'm listing the ones I found so far, and the course of action I
> propose for each. As usual, 72 hours for lazy consensus before acting
> (but I can take care of all I propose below).
>
> 1) Fisheye https://fisheye.apache.org/changelog/openoffice
>
> "We have an instance of Atlassian FishEye for source browsing,
> searching, reporting and visualization of main trunk (main development
> area)." (source.html)
>
> Proposal: link to Github https://github.com/apache/openoffice for the
> short term; when Opengrok is ready, link to it; tell Infra to
> explicitly kill the Fisheye instance. Or (if someone wants to take
> over since they do use Fisheye) ask Infra to link it to the new
> repository.
>
> 2) OpenGrok
>
> This is already dead. I know Peter has it on his radar but I think we
> only have the empty VM for the time being. So, no action pending
> restoration of the service, and when it is restored it will of course
> point to Git.
>
> 3) Open Hub tracker https://www.openhub.net/p/openoffice
>
> "Our SVN tree is read by the Open Hub tracker to generate some various
> statistics. Note that the migration from the legacy Mercurial
> repository to SVN at Apache has caused pre-existing files to be
> double-counted. But the contribution history should be intact."
> (source.html)
>
> Proposal: tell them to please stop tracking; their data have always
> been wrong anyway, as they were tracking the wrong branches. If
> someone still wants OpenOffice to be on OpenHub instead, please take
> over, find who the admins are in our PMC and ask them to put the new
> repository URL.
Yes, the data on OpenHub is totally outdated. Admins are Jim and Ariel.
I think we should close it down...

>
> 4) Bugzilla annotator
>
> Most of you should be aware that writing "#i123456#" in a commit log
> would automatically post that commit to Bugzilla as a comment for
> issue 123456. The magic is done by a Python bot running on the MWiki
> server and parsing SVN logs.
>
> Proposal: stop the Python script (obviously); if at least one other
> committer writes here that he thinks this feature is useful, I can
> modify the Python script to use Git and/or turn it into a Git hook;
> this may require substantial work.
Did it work since the move to the new VM? I have never tried since then...
However, it was a useful function and we could parse the logs on Gitbox
instead:

https://gitbox.apache.org/repos/asf?p=openoffice.git;a=log;h=refs/heads/trunk

>
> 5) Devtools
>
> Our devtools are code and should have been included in the migration
> to Git. I didn't notice they were left out.
>
> Proposal: talk to Infra to see if we can easily add them retaining
> history, or just copy them over from SVN and push this to Git. We
> could discuss for ages where they belong to, but some of them are
> definitely related to the source tree and as first approximation I
> would move (i.e., "keep") them there.
Seems reasonable to me.

Regards,

   Matthias

>
> Regards,
>   Andrea.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


smime.p7s (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Broken tools from GIT migration

Carl Marcum-3
In reply to this post by Andrea Pescetti-2
Hi Andrea,


On 8/15/19 2:34 AM, Andrea Pescetti wrote:

> ...
>
> 5) Devtools
>
> Our devtools are code and should have been included in the migration
> to Git. I didn't notice they were left out.
>
> Proposal: talk to Infra to see if we can easily add them retaining
> history, or just copy them over from SVN and push this to Git. We
> could discuss for ages where they belong to, but some of them are
> definitely related to the source tree and as first approximation I
> would move (i.e., "keep") them there.

Yes there are a few things in devtools I will work on as time permits.

Thanks,

Carl


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Broken tools from GIT migration

Jim Jagielski
In reply to this post by Andrea Pescetti-2


> On Aug 15, 2019, at 2:34 AM, Andrea Pescetti <[hidden email]> wrote:
>
> 3) Open Hub tracker https://www.openhub.net/p/openoffice
>
> "Our SVN tree is read by the Open Hub tracker to generate some various statistics. Note that the migration from the legacy Mercurial repository to SVN at Apache has caused pre-existing files to be double-counted. But the contribution history should be intact." (source.html)
>
> Proposal: tell them to please stop tracking; their data have always been wrong anyway, as they were tracking the wrong branches. If someone still wants OpenOffice to be on OpenHub instead, please take over, find who the admins are in our PMC and ask them to put the new repository URL.
>

I'll fix this.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[discussion] DEV tools(was: Broken tools from GIT migration)

Peter Kovacs-3
In reply to this post by Andrea Pescetti-2
Hello all,

I went through the dev tools. Okay except for Netbeans integration they
are rather small conveniance tools.

So I would go for:

dev_tools:

aoo-stats/    
bootstrap-connector/
build-scripts/
bz-tools/
genUpdateFeed/    
guno-extension/
lazybones-templates/
list-stats/
release-scripts/
scripts/
sdk-examples/
updateVersion/
test.c


netbeans_plugins

netbeansintegration/

leave in the the svn Repo (because we do not need them now)

svn-stats/

hg2svn/

Background:

I would split them because we already have a lot of code in the repo,
and I think for those it is not an issue to have a different repo to
download.

For Netbeans separation. I plan a generic netbeans plugin to work with
oo, so we couldcluster that together.

And for the last leave the svn stuff in the svn we will not loose them
anywhere soon. If we need svn-stats we need to create a git-stats
anyhow, which would be new. even if we migrate the code.


On 15.08.19 08:34, Andrea Pescetti wrote:

> 5) Devtools
>
> Our devtools are code and should have been included in the migration
> to Git. I didn't notice they were left out.
>
> Proposal: talk to Infra to see if we can easily add them retaining
> history, or just copy them over from SVN and push this to Git. We
> could discuss for ages where they belong to, but some of them are
> definitely related to the source tree and as first approximation I
> would move (i.e., "keep") them there.
>
> Regards,
>   Andrea.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [discussion] DEV tools(was: Broken tools from GIT migration)

Marcus (OOo)
Am 17.08.19 um 11:51 schrieb Peter Kovacs:
> I went through the dev tools. Okay except for Netbeans integration they
> are rather small conveniance tools.
>
> So I would go for:
>
> dev_tools:
>
> aoo-stats/

don't move this to Git as the stats are affecting the website only. So
they have to stay in SVN.

Thanks

Marcus



> On 15.08.19 08:34, Andrea Pescetti wrote:
>> 5) Devtools
>>
>> Our devtools are code and should have been included in the migration
>> to Git. I didn't notice they were left out.
>>
>> Proposal: talk to Infra to see if we can easily add them retaining
>> history, or just copy them over from SVN and push this to Git. We
>> could discuss for ages where they belong to, but some of them are
>> definitely related to the source tree and as first approximation I
>> would move (i.e., "keep") them there.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]