You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sis.apache.org by Martin Desruisseaux <ma...@geomatys.com> on 2015/11/23 19:16:00 UTC
INFRA issue created - please avoid commits for now
Hello all
I created the ticket for the infra team:
https://issues.apache.org/jira/browse/INFRA-10826
We should not commit anything on the JDK8 branch until this issue is
resolved (either fixed or closed as "will not fix").
Thanks,
Martin
Re: INFRA issue created - please avoid commits for now
Posted by Martin Desruisseaux <ma...@geomatys.com>.
Le 06/12/15 14:36, Martin Desruisseaux a écrit :
> I'm not completely sure if what infra is looking for would allow us to
> clean history even months after the fact. I will try to read again
> infra emails more carefully and report back on this question.
>From my understanding of infra emails, they may have a solution for this
kind of situation in the future. But in the meantime adding new commits
will probably not make a difference provided that we do not refer the
deleted files in new commits.
Martin
Re: INFRA issue created - please avoid commits for now
Posted by Martin Desruisseaux <ma...@geomatys.com>.
Le 07/12/15 11:14, Marc Le Bihan a écrit :
> How much time will take the plan to resume commits and updates on JDK8 ?
There is no delay - it can be now.
The proposed delay was for the merges with JDK7 and other branches, not
for commits on JDK8 branch.
Martin
Re: INFRA issue created - please avoid commits for now
Posted by Marc Le Bihan <ml...@gmail.com>.
How much time will take the plan to resume commits and updates on JDK8 ?
I would like to receive the updates from the JDK 8 branch as soon as
possible : I think the push --force can be done later.
I fear a bit from having been excluded from updates since 15 days. Because
If I commit without updating, problems will surely come quicky. And the day
you will try to do the merge, you might encounter some troubles.
-----Message d'origine-----
From: Martin Desruisseaux
Sent: Monday, December 07, 2015 10:23 AM
To: dev@sis.apache.org
Subject: Re: INFRA issue created - please avoid commits for now
Hello Marc
Yes, the plan is to resume commits on JDK8 like before.
The reason for avoiding the merge with other branches is that the binary
files is only in the history of JDK8 branch for now. If we want to avoid
to bring this history into trunk, we need to do the "push --force" on
JDK8 branch first.
Martin
Le 07/12/15 04:48, Marc Le Bihan a écrit :
> If I commit now, I will commit my work in a position that in SVN is
> "15 days ago", because currently I am no more receiving updates from
> this branch since 15 days ?
> Isn't it for me : committing in the void, if I don't receive any
> updates in exchange ?
>
> Resume all the things you have done with branch JDK 8 please.
> Let us return to normal work (commit and updates), and later you will
> see if you really to something with git or not.
Re: INFRA issue created - please avoid commits for now
Posted by Martin Desruisseaux <ma...@geomatys.com>.
Hello Marc
Yes, the plan is to resume commits on JDK8 like before.
The reason for avoiding the merge with other branches is that the binary
files is only in the history of JDK8 branch for now. If we want to avoid
to bring this history into trunk, we need to do the "push --force" on
JDK8 branch first.
Martin
Le 07/12/15 04:48, Marc Le Bihan a écrit :
> If I commit now, I will commit my work in a position that in SVN is
> "15 days ago", because currently I am no more receiving updates from
> this branch since 15 days ?
> Isn't it for me : committing in the void, if I don't receive any
> updates in exchange ?
>
> Resume all the things you have done with branch JDK 8 please.
> Let us return to normal work (commit and updates), and later you will
> see if you really to something with git or not.
Re: INFRA issue created - please avoid commits for now
Posted by Marc Le Bihan <ml...@gmail.com>.
I don't understand what we are doing.
If I commit now, I will commit my work in a position that in SVN is "15 days
ago", because currently I am no more receiving updates from this branch
since 15 days ?
Isn't it for me : committing in the void, if I don't receive any updates in
exchange ?
Resume all the things you have done with branch JDK 8 please.
Let us return to normal work (commit and updates), and later you will see if
you really to something with git or not.
Marc.
-----Message d'origine-----
From: Martin Desruisseaux
Sent: Sunday, December 06, 2015 6:32 PM
To: dev@sis.apache.org
Subject: Re: INFRA issue created - please avoid commits for now
Let resume commits on the JDK8 branch since we closed INFRA-10826
anyway. But we would not merge with other branches or trunk yet. If we
move to git, I would like to try a "push --force" before those merges.
Note that if we move to Git, SVN would not be completely abandoned. It
is still required for the Apache release process since SVN is better
suited than Git for binary files (because the history weight stay on the
server side only). We may also keep
http://svn.apache.org/repos/asf/sis/data/ for the same reason. We also
have the web site and the IP review pages which can stay on SVN for now.
Martin
Le 06/12/15 15:06, Marc Le Bihan a écrit :
> I think : 1) Ignore the 3 Mb binary file and resume activity. It will
> allow me to update and commit a last time my work.
>
> 2) Ask infra to switch the SIS project from SVN to Git
> 3) Abandon SVN.
Re: INFRA issue created - please avoid commits for now
Posted by Martin Desruisseaux <ma...@geomatys.com>.
Let resume commits on the JDK8 branch since we closed INFRA-10826
anyway. But we would not merge with other branches or trunk yet. If we
move to git, I would like to try a "push --force" before those merges.
Note that if we move to Git, SVN would not be completely abandoned. It
is still required for the Apache release process since SVN is better
suited than Git for binary files (because the history weight stay on the
server side only). We may also keep
http://svn.apache.org/repos/asf/sis/data/ for the same reason. We also
have the web site and the IP review pages which can stay on SVN for now.
Martin
Le 06/12/15 15:06, Marc Le Bihan a écrit :
> I think : 1) Ignore the 3 Mb binary file and resume activity. It will
> allow me to update and commit a last time my work.
>
> 2) Ask infra to switch the SIS project from SVN to Git
> 3) Abandon SVN.
Re: INFRA issue created - please avoid commits for now
Posted by Marc Le Bihan <ml...@gmail.com>.
I think :
1) Ignore the 3 Mb binary file and resume activity.
It will allow me to update and commit a last time my work.
2) Ask infra to switch the SIS project from SVN to Git
3) Abandon SVN.
-----Message d'origine-----
From: Martin Desruisseaux
Sent: Sunday, December 06, 2015 2:36 PM
To: dev@sis.apache.org
Subject: Re: INFRA issue created - please avoid commits for now
Update on INFRA-10826 front:
Someone on infrastructure@apache.org looked at INFRA-10826 (or to
similar issues - from the discussion that I saw on the mailing list, at
least 3 other projects are facing similar problems). They are still
looking into how to erase such files, but it's trickier than initially
thought. They tried a filter that claimed to have removed the files, but
they still show up on GitHub.
I closed INFRA-10826 as "will not fix". However in my understanding,
investigation on infrastructure side continue anyway for other projects.
For example they are looking for removing JAR files from Lucene history.
But I do not know if and when infra would have a solution.
So short terms alternatives for us are:
* Ignore the 3 Mb binary file and resume activity. We should be
careful to not commit other big files. I'm not completely sure if
what infra is looking for would allow us to clean history even
months after the fact. I will try to read again infra emails more
carefully and report back on this question.
* Ask infra to switch the SIS project from SVN to Git and do a "push
--force" ourself before to resume activity.
What would peoples prefer?
Martin
Re: INFRA issue created - please avoid commits for now
Posted by Martin Desruisseaux <ma...@geomatys.com>.
Update on INFRA-10826 front:
Someone on infrastructure@apache.org looked at INFRA-10826 (or to
similar issues - from the discussion that I saw on the mailing list, at
least 3 other projects are facing similar problems). They are still
looking into how to erase such files, but it's trickier than initially
thought. They tried a filter that claimed to have removed the files, but
they still show up on GitHub.
I closed INFRA-10826 as "will not fix". However in my understanding,
investigation on infrastructure side continue anyway for other projects.
For example they are looking for removing JAR files from Lucene history.
But I do not know if and when infra would have a solution.
So short terms alternatives for us are:
* Ignore the 3 Mb binary file and resume activity. We should be
careful to not commit other big files. I'm not completely sure if
what infra is looking for would allow us to clean history even
months after the fact. I will try to read again infra emails more
carefully and report back on this question.
* Ask infra to switch the SIS project from SVN to Git and do a "push
--force" ourself before to resume activity.
What would peoples prefer?
Martin
Re: INFRA issue created - please avoid commits for now
Posted by Martin Desruisseaux <ma...@geomatys.com>.
Hello Marc
Someone on infrastructure@apache.org told me that he will look at the
issue. I didn't hear back yet. I will send an email now for asking.
Martin
Le 06/12/15 11:39, Marc Le Bihan a écrit :
> Hello,
>
> I would like to commit now the abitility to do direct access in a
> Shapefile, using the .SHX file content that often comes with the .SHP
> file.
>
> The
> https://svn.apache.org/repos/asf/sis/branches/JDK8/
> repository is still "locked". 15 days has been spent since the
> creation of the INFRA-10826 and the infra team is not doing anything.
> https://issues.apache.org/jira/browse/INFRA-10826
>
> Can we resume the use of
> https://svn.apache.org/repos/asf/sis/branches/JDK8/ repository now ?
> Or at least have a date ? If you tell me : come back in one month to
> do your commit, I won't check everyday.
>
> Regards,
>
> Marc.
Re: INFRA issue created - please avoid commits for now
Posted by Marc Le Bihan <ml...@gmail.com>.
Hello,
I would like to commit now the abitility to do direct access in a
Shapefile, using the .SHX file content that often comes with the .SHP file.
The
https://svn.apache.org/repos/asf/sis/branches/JDK8/
repository is still "locked". 15 days has been spent since the creation of
the INFRA-10826 and the infra team is not doing anything.
https://issues.apache.org/jira/browse/INFRA-10826
Can we resume the use of https://svn.apache.org/repos/asf/sis/branches/JDK8/
repository now ?
Or at least have a date ? If you tell me : come back in one month to do your
commit, I won't check everyday.
Regards,
Marc.
-----Message d'origine-----
From: Martin Desruisseaux
Sent: Friday, November 27, 2015 11:12 AM
To: dev@sis.apache.org
Subject: Re: INFRA issue created - please avoid commits for now
Thanks. Actually I was thinking about proposing to migrate SIS to Git
since a little while. But my intend was to wait for the debate on
board@apache.org to settle down in the hope to avoid putting additional
pressure on them. In the meantime, I commit my work on
https://github.com/Geomatys/sis/tree/JDK8 (I will delete that branch
when we will be back on Apache's SVN or Git).
Martin
Le 27/11/15 10:52, Marc LE BIHAN a écrit :
> I can wait for the INFRA to be completed. No real emergency.
>
> For Git, I believe other developpers and you may like it, and I would
> enjoy
> it too.
> If one day we fully migrate to Git, it will be nice, but at the time you
> want to complete the migration. No hurry for me.
>
> Marc.
Re: INFRA issue created - please avoid commits for now
Posted by Martin Desruisseaux <ma...@geomatys.com>.
Thanks. Actually I was thinking about proposing to migrate SIS to Git
since a little while. But my intend was to wait for the debate on
board@apache.org to settle down in the hope to avoid putting additional
pressure on them. In the meantime, I commit my work on
https://github.com/Geomatys/sis/tree/JDK8 (I will delete that branch
when we will be back on Apache's SVN or Git).
Martin
Le 27/11/15 10:52, Marc LE BIHAN a écrit :
> I can wait for the INFRA to be completed. No real emergency.
>
> For Git, I believe other developpers and you may like it, and I would enjoy
> it too.
> If one day we fully migrate to Git, it will be nice, but at the time you
> want to complete the migration. No hurry for me.
>
> Marc.
Re: INFRA issue created - please avoid commits for now
Posted by Marc LE BIHAN <ml...@gmail.com>.
I can wait for the INFRA to be completed. No real emergency.
For Git, I believe other developpers and you may like it, and I would enjoy
it too.
If one day we fully migrate to Git, it will be nice, but at the time you
want to complete the migration. No hurry for me.
Marc.
2015-11-27 10:49 GMT+01:00 Martin Desruisseaux <
martin.desruisseaux@geomatys.com>:
> Hello Marc
>
> I do not know how long it will take before INFRA take the task. I
> suspect that the INFRA team is waiting for decisions from the Apache
> board about foundation's policy regarding history rewriting in Git (they
> are extensively debating this topic since a few weeks on
> board@apache.org). I also think that it wasn't clear that this issue was
> blocking commits on SIS (probably I should not have flagged this issue
> as "minor"). I will add a comment clarifying that point in the hope that
> it reach the infra team.
>
> In the meantime, we could create a temporary SVN branch for continuing
> the work. If the branch is not mirrored on Git, I think that we will not
> have any problem when the branch will be merged to JDK8.
>
> Another possible solution (but it may take more time than the SVN
> branch) would be to ask the infra team to fully migrate SIS to Git, if
> we have a consensus on this list for that request. In my understanding
> of the policy that seems to be emerging, we would be allowed to "push
> --force" on branches (but not on master).
>
> What would be your preference?
>
> Martin
>
>
> Le 27/11/15 07:37, Marc Le Bihan a écrit :
> > Hello !
> >
> > How long shall be commits avoided in JDK8 branch ?
> > I have run a VisualVM session (a profiler) on the DBase III code to
> > examine why it was taking 310 seconds (5 minutes) to load and read the
> > whole DBase part of the shapefile of french cities outlines (36,500+
> > polygons to read).
> > Mostly it was some log.debug that weren't well surrounded by
> > isLoggable(Level) functions, and few others optimizations where useful.
> >
> > I succeded in making this time fall to 1.3 seconds which is better,
> > and I would like to do a commit.
> >
> > Regards,
> >
> > Marc.
>
>
Re: INFRA issue created - please avoid commits for now
Posted by Martin Desruisseaux <ma...@geomatys.com>.
Hello Marc
I do not know how long it will take before INFRA take the task. I
suspect that the INFRA team is waiting for decisions from the Apache
board about foundation's policy regarding history rewriting in Git (they
are extensively debating this topic since a few weeks on
board@apache.org). I also think that it wasn't clear that this issue was
blocking commits on SIS (probably I should not have flagged this issue
as "minor"). I will add a comment clarifying that point in the hope that
it reach the infra team.
In the meantime, we could create a temporary SVN branch for continuing
the work. If the branch is not mirrored on Git, I think that we will not
have any problem when the branch will be merged to JDK8.
Another possible solution (but it may take more time than the SVN
branch) would be to ask the infra team to fully migrate SIS to Git, if
we have a consensus on this list for that request. In my understanding
of the policy that seems to be emerging, we would be allowed to "push
--force" on branches (but not on master).
What would be your preference?
Martin
Le 27/11/15 07:37, Marc Le Bihan a écrit :
> Hello !
>
> How long shall be commits avoided in JDK8 branch ?
> I have run a VisualVM session (a profiler) on the DBase III code to
> examine why it was taking 310 seconds (5 minutes) to load and read the
> whole DBase part of the shapefile of french cities outlines (36,500+
> polygons to read).
> Mostly it was some log.debug that weren't well surrounded by
> isLoggable(Level) functions, and few others optimizations where useful.
>
> I succeded in making this time fall to 1.3 seconds which is better,
> and I would like to do a commit.
>
> Regards,
>
> Marc.
Re: INFRA issue created - please avoid commits for now
Posted by Marc Le Bihan <ml...@gmail.com>.
Hello !
How long shall be commits avoided in JDK8 branch ?
I have run a VisualVM session (a profiler) on the DBase III code to
examine why it was taking 310 seconds (5 minutes) to load and read the whole
DBase part of the shapefile of french cities outlines (36,500+ polygons to
read).
Mostly it was some log.debug that weren't well surrounded by
isLoggable(Level) functions, and few others optimizations where useful.
I succeded in making this time fall to 1.3 seconds which is better, and
I would like to do a commit.
Regards,
Marc.
-----Message d'origine-----
From: Martin Desruisseaux
Sent: Monday, November 23, 2015 7:16 PM
To: dev@sis.apache.org
Subject: INFRA issue created - please avoid commits for now
Hello all
I created the ticket for the infra team:
https://issues.apache.org/jira/browse/INFRA-10826
We should not commit anything on the JDK8 branch until this issue is
resolved (either fixed or closed as "will not fix").
Thanks,
Martin