You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@xmlgraphics.apache.org by Glenn Adams <gl...@skynav.com> on 2023/02/17 05:01:11 UTC
[GitMigration] Rename Git Mirrors for XML Graphics Project
Dear All,
I just filed INFRA-24218 [1] to begin the process of migrating the
xmlgraphics SVN repositories to GitBox/GitHub.
I will coordinate with the project the starting date/time of the migration
after which further commits to the SVN repositories should not be performed.
Regards,
Glenn
[1] https://issues.apache.org/jira/browse/INFRA-24218
Re: [GitMigration] Rename Git Mirrors for XML Graphics Project
Posted by Glenn Adams <gl...@skynav.com>.
On Wed, Mar 8, 2023 at 4:07 AM Simon Steiner <si...@gmail.com>
wrote:
> We are using checkstyle and findbugs currently which allow offline use and
> use in commercial development without extra licensing.
>
Checkstyle is good for enforcing style rules, but our dependencies are
seriously out of date, currently referring to Maven Checkstyle Plugin 2.14
or 2.15, which use Checkstyle 5.8 and 6.1.1, respectively, and where both
are now ~8 years old (early 2015). The current version of the plugin is
3.2.1 which uses Checkstyle 9.3 by default (and can be configured to use
more recent versions of Checkstyle, for which the most recent version is
10.8.0).
Findbugs is an abandoned project, last released in 2015. Spotbugs is its
successor, so we should reconfigure to use the latter. Neither are focused
on vulnerability analysis or remediation.
This situation demonstrates the disadvantage of using a statically
configured analysis tool, when a cloud or server based tool is generally
always using the latest version.
> Do we want to switch to cloud based tools that currently allow our repo to
> be scanned.
>
For a major new feature I may not want to send to the cloud for scanning
> until I have permission to open source this change.
>
CodeQL is open sourced at [1], while SonarQube Community Edition is open
sourced at [2].
[1] https://github.com/github/codeql
[2] https://github.com/SonarSource/sonarqube
Here [3] is an article on the use of SonarQube in an Apache project (Apache
Struts). Also, according to [4], 418 Apache projects are configured to use
SonarCloud. See [5] for more on SonarLint, SonarQube, and SonarCloud.
[3] https://softwaremill.com/how-to-use-sonar-in-your-project/
[4] https://sonarcloud.io/organizations/apache/projects
[5] https://www.sonarsource.com/open-source-editions/
RE: [GitMigration] Rename Git Mirrors for XML Graphics Project
Posted by Simon Steiner <si...@gmail.com>.
Hi,
We are using checkstyle and findbugs currently which allow offline use and use in commercial development without extra licensing.
Do we want to switch to cloud based tools that currently allow our repo to be scanned.
For a major new feature I may not want to send to the cloud for scanning until I have permission to open source this change.
Thanks
From: Simon Steiner <si...@gmail.com>
Sent: 08 March 2023 10:00
To: 'Glenn Adams' <gl...@skynav.com>; general@xmlgraphics.apache.org
Subject: RE: [GitMigration] Rename Git Mirrors for XML Graphics Project
Hi,
I was thinking your changes would make the PR only merge once certain tools go green such as cve scanning.
Thanks
From: Glenn Adams <glenn@skynav.com <ma...@skynav.com> >
Sent: 08 March 2023 09:40
To: general@xmlgraphics.apache.org <ma...@xmlgraphics.apache.org>
Cc: Simon Steiner <simonsteiner1984@gmail.com <ma...@gmail.com> >
Subject: Re: [GitMigration] Rename Git Mirrors for XML Graphics Project
Here is a link to a PDF containing my full response regarding PR usage.
https://drive.google.com/file/d/12sHfOyXyU1fJzxvd5dBQRqAD6d9l4CBI/view?usp=sharing
Most of the security and code quality tools are server based these days, and licensed. CodeQL is owned by GitHub who make its use available for free to public repositories in GH; others, like SonarQube (owned by JetBrains) also make it available via GH Actions for no fee for public repositories. I am planning to configure our repos to also use SonarQube in addition to CodeQL via GH Actions. I can't speak to their availability to the community for local installations.
I don't think we will have any trouble with PRs being blocked by 3rd party analysis tools, unless we choose to do so. So at this point, I'm not worried about PRs being blocked without any recourse on our part.
On Wed, Mar 8, 2023 at 2:58 AM Simon Steiner <simonsteiner1984@gmail.com <ma...@gmail.com> > wrote:
Hi,
The images in your email are not displaying for me.
Can we run these security/quality checking tool locally?
I am not sure we should block all PRs based on new CVEs being released which may require lots of work to upgrade dependancies.
Thanks
-----Original Message-----
From: Simon Steiner <simonsteiner1984@gmail.com <ma...@gmail.com> >
Sent: 07 March 2023 20:50
To: general@xmlgraphics.apache.org <ma...@xmlgraphics.apache.org>
Subject: RE: [GitMigration] Rename Git Mirrors for XML Graphics Project
Hi,
We are seeing so many emails after using the PR system today that its hard to review changes.
Thanks
-----Original Message-----
From: Simon Steiner <simonsteiner1984@gmail.com <ma...@gmail.com> >
Sent: 07 March 2023 20:49
To: general@xmlgraphics.apache.org <ma...@xmlgraphics.apache.org>
Subject: RE: [GitMigration] Rename Git Mirrors for XML Graphics Project
Hi,
I think the overhead it adds, issues arounds CI failing for reasons outside of your control.
Can you rerun github pr ci if it fails.
If your changing something that wont affect CI such as a small typo, documentation?
For large changes it is good to open a code review.
Thanks
-----Original Message-----
From: Glenn Adams <glenn@skynav.com <ma...@skynav.com> >
Sent: 07 March 2023 20:33
To: general@xmlgraphics.apache.org <ma...@xmlgraphics.apache.org>
Subject: Re: [GitMigration] Rename Git Mirrors for XML Graphics Project
I haven't done that yet, though I would like to do so. There are a variety of reasons for requiring PRs, including
- ensure that GitHub actions, such as build, test, analyze, are
completed (in PR branch) successfully before merging into main
- ensure that PR conversation (including discussion resolution) and
changes are recorded and retained for future reference
- enable (optional) review processing, should it be desired
Given that it takes only a few mouse clicks in GH to create a PR from a commit on a private branch, is there any reason we shouldn't use PRs for all prospective merges? We should take advantage of the tools gained from migrating to Git, yes?
On Tue, Mar 7, 2023 at 12:47 PM Simon Steiner <simonsteiner1984@gmail.com <ma...@gmail.com> >
wrote:
> Glenn are you making PRs required for the git repos, should this go
> thru a vote before being implemented?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org <ma...@xmlgraphics.apache.org>
For additional commands, e-mail: general-help@xmlgraphics.apache.org <ma...@xmlgraphics.apache.org>
RE: [GitMigration] Rename Git Mirrors for XML Graphics Project
Posted by Simon Steiner <si...@gmail.com>.
Hi,
I was thinking your changes would make the PR only merge once certain tools go green such as cve scanning.
Thanks
From: Glenn Adams <gl...@skynav.com>
Sent: 08 March 2023 09:40
To: general@xmlgraphics.apache.org
Cc: Simon Steiner <si...@gmail.com>
Subject: Re: [GitMigration] Rename Git Mirrors for XML Graphics Project
Here is a link to a PDF containing my full response regarding PR usage.
https://drive.google.com/file/d/12sHfOyXyU1fJzxvd5dBQRqAD6d9l4CBI/view?usp=sharing
Most of the security and code quality tools are server based these days, and licensed. CodeQL is owned by GitHub who make its use available for free to public repositories in GH; others, like SonarQube (owned by JetBrains) also make it available via GH Actions for no fee for public repositories. I am planning to configure our repos to also use SonarQube in addition to CodeQL via GH Actions. I can't speak to their availability to the community for local installations.
I don't think we will have any trouble with PRs being blocked by 3rd party analysis tools, unless we choose to do so. So at this point, I'm not worried about PRs being blocked without any recourse on our part.
On Wed, Mar 8, 2023 at 2:58 AM Simon Steiner <simonsteiner1984@gmail.com <ma...@gmail.com> > wrote:
Hi,
The images in your email are not displaying for me.
Can we run these security/quality checking tool locally?
I am not sure we should block all PRs based on new CVEs being released which may require lots of work to upgrade dependancies.
Thanks
-----Original Message-----
From: Simon Steiner <simonsteiner1984@gmail.com <ma...@gmail.com> >
Sent: 07 March 2023 20:50
To: general@xmlgraphics.apache.org
Subject: RE: [GitMigration] Rename Git Mirrors for XML Graphics Project
Hi,
We are seeing so many emails after using the PR system today that its hard to review changes.
Thanks
-----Original Message-----
From: Simon Steiner <simonsteiner1984@gmail.com <ma...@gmail.com> >
Sent: 07 March 2023 20:49
To: general@xmlgraphics.apache.org <ma...@xmlgraphics.apache.org>
Subject: RE: [GitMigration] Rename Git Mirrors for XML Graphics Project
Hi,
I think the overhead it adds, issues arounds CI failing for reasons outside of your control.
Can you rerun github pr ci if it fails.
If your changing something that wont affect CI such as a small typo, documentation?
For large changes it is good to open a code review.
Thanks
-----Original Message-----
From: Glenn Adams <glenn@skynav.com <ma...@skynav.com> >
Sent: 07 March 2023 20:33
To: general@xmlgraphics.apache.org <ma...@xmlgraphics.apache.org>
Subject: Re: [GitMigration] Rename Git Mirrors for XML Graphics Project
I haven't done that yet, though I would like to do so. There are a variety of reasons for requiring PRs, including
- ensure that GitHub actions, such as build, test, analyze, are
completed (in PR branch) successfully before merging into main
- ensure that PR conversation (including discussion resolution) and
changes are recorded and retained for future reference
- enable (optional) review processing, should it be desired
Given that it takes only a few mouse clicks in GH to create a PR from a commit on a private branch, is there any reason we shouldn't use PRs for all prospective merges? We should take advantage of the tools gained from migrating to Git, yes?
On Tue, Mar 7, 2023 at 12:47 PM Simon Steiner <simonsteiner1984@gmail.com <ma...@gmail.com> >
wrote:
> Glenn are you making PRs required for the git repos, should this go
> thru a vote before being implemented?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org <ma...@xmlgraphics.apache.org>
For additional commands, e-mail: general-help@xmlgraphics.apache.org <ma...@xmlgraphics.apache.org>
Re: [GitMigration] Rename Git Mirrors for XML Graphics Project
Posted by Glenn Adams <gl...@skynav.com>.
Here is a link to a PDF containing my full response regarding PR usage.
https://drive.google.com/file/d/12sHfOyXyU1fJzxvd5dBQRqAD6d9l4CBI/view?usp=sharing
Most of the security and code quality tools are server based these days,
and licensed. CodeQL is owned by GitHub who make its use available for free
to public repositories in GH; others, like SonarQube (owned by JetBrains)
also make it available via GH Actions for no fee for public repositories. I
am planning to configure our repos to also use SonarQube in addition to
CodeQL via GH Actions. I can't speak to their availability to the community
for local installations.
I don't think we will have any trouble with PRs being blocked by 3rd party
analysis tools, unless we choose to do so. So at this point, I'm not
worried about PRs being blocked without any recourse on our part.
On Wed, Mar 8, 2023 at 2:58 AM Simon Steiner <si...@gmail.com>
wrote:
> Hi,
>
> The images in your email are not displaying for me.
> Can we run these security/quality checking tool locally?
> I am not sure we should block all PRs based on new CVEs being released
> which may require lots of work to upgrade dependancies.
>
> Thanks
>
> -----Original Message-----
> From: Simon Steiner <si...@gmail.com>
> Sent: 07 March 2023 20:50
> To: general@xmlgraphics.apache.org
> Subject: RE: [GitMigration] Rename Git Mirrors for XML Graphics Project
>
> Hi,
>
> We are seeing so many emails after using the PR system today that its hard
> to review changes.
>
> Thanks
>
> -----Original Message-----
> From: Simon Steiner <si...@gmail.com>
> Sent: 07 March 2023 20:49
> To: general@xmlgraphics.apache.org
> Subject: RE: [GitMigration] Rename Git Mirrors for XML Graphics Project
>
> Hi,
>
> I think the overhead it adds, issues arounds CI failing for reasons
> outside of your control.
> Can you rerun github pr ci if it fails.
> If your changing something that wont affect CI such as a small typo,
> documentation?
>
> For large changes it is good to open a code review.
>
> Thanks
>
> -----Original Message-----
> From: Glenn Adams <gl...@skynav.com>
> Sent: 07 March 2023 20:33
> To: general@xmlgraphics.apache.org
> Subject: Re: [GitMigration] Rename Git Mirrors for XML Graphics Project
>
> I haven't done that yet, though I would like to do so. There are a variety
> of reasons for requiring PRs, including
>
> - ensure that GitHub actions, such as build, test, analyze, are
> completed (in PR branch) successfully before merging into main
> - ensure that PR conversation (including discussion resolution) and
> changes are recorded and retained for future reference
> - enable (optional) review processing, should it be desired
>
> Given that it takes only a few mouse clicks in GH to create a PR from a
> commit on a private branch, is there any reason we shouldn't use PRs for
> all prospective merges? We should take advantage of the tools gained from
> migrating to Git, yes?
>
> On Tue, Mar 7, 2023 at 12:47 PM Simon Steiner <si...@gmail.com>
> wrote:
>
> > Glenn are you making PRs required for the git repos, should this go
> > thru a vote before being implemented?
> >
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: general-help@xmlgraphics.apache.org
>
>
RE: [GitMigration] Rename Git Mirrors for XML Graphics Project
Posted by Simon Steiner <si...@gmail.com>.
Hi,
The images in your email are not displaying for me.
Can we run these security/quality checking tool locally?
I am not sure we should block all PRs based on new CVEs being released which may require lots of work to upgrade dependancies.
Thanks
-----Original Message-----
From: Simon Steiner <si...@gmail.com>
Sent: 07 March 2023 20:50
To: general@xmlgraphics.apache.org
Subject: RE: [GitMigration] Rename Git Mirrors for XML Graphics Project
Hi,
We are seeing so many emails after using the PR system today that its hard to review changes.
Thanks
-----Original Message-----
From: Simon Steiner <si...@gmail.com>
Sent: 07 March 2023 20:49
To: general@xmlgraphics.apache.org
Subject: RE: [GitMigration] Rename Git Mirrors for XML Graphics Project
Hi,
I think the overhead it adds, issues arounds CI failing for reasons outside of your control.
Can you rerun github pr ci if it fails.
If your changing something that wont affect CI such as a small typo, documentation?
For large changes it is good to open a code review.
Thanks
-----Original Message-----
From: Glenn Adams <gl...@skynav.com>
Sent: 07 March 2023 20:33
To: general@xmlgraphics.apache.org
Subject: Re: [GitMigration] Rename Git Mirrors for XML Graphics Project
I haven't done that yet, though I would like to do so. There are a variety of reasons for requiring PRs, including
- ensure that GitHub actions, such as build, test, analyze, are
completed (in PR branch) successfully before merging into main
- ensure that PR conversation (including discussion resolution) and
changes are recorded and retained for future reference
- enable (optional) review processing, should it be desired
Given that it takes only a few mouse clicks in GH to create a PR from a commit on a private branch, is there any reason we shouldn't use PRs for all prospective merges? We should take advantage of the tools gained from migrating to Git, yes?
On Tue, Mar 7, 2023 at 12:47 PM Simon Steiner <si...@gmail.com>
wrote:
> Glenn are you making PRs required for the git repos, should this go
> thru a vote before being implemented?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org
RE: [GitMigration] Rename Git Mirrors for XML Graphics Project
Posted by Simon Steiner <si...@gmail.com>.
Hi,
We are seeing so many emails after using the PR system today that its hard to review changes.
Thanks
-----Original Message-----
From: Simon Steiner <si...@gmail.com>
Sent: 07 March 2023 20:49
To: general@xmlgraphics.apache.org
Subject: RE: [GitMigration] Rename Git Mirrors for XML Graphics Project
Hi,
I think the overhead it adds, issues arounds CI failing for reasons outside of your control.
Can you rerun github pr ci if it fails.
If your changing something that wont affect CI such as a small typo, documentation?
For large changes it is good to open a code review.
Thanks
-----Original Message-----
From: Glenn Adams <gl...@skynav.com>
Sent: 07 March 2023 20:33
To: general@xmlgraphics.apache.org
Subject: Re: [GitMigration] Rename Git Mirrors for XML Graphics Project
I haven't done that yet, though I would like to do so. There are a variety of reasons for requiring PRs, including
- ensure that GitHub actions, such as build, test, analyze, are
completed (in PR branch) successfully before merging into main
- ensure that PR conversation (including discussion resolution) and
changes are recorded and retained for future reference
- enable (optional) review processing, should it be desired
Given that it takes only a few mouse clicks in GH to create a PR from a commit on a private branch, is there any reason we shouldn't use PRs for all prospective merges? We should take advantage of the tools gained from migrating to Git, yes?
On Tue, Mar 7, 2023 at 12:47 PM Simon Steiner <si...@gmail.com>
wrote:
> Glenn are you making PRs required for the git repos, should this go
> thru a vote before being implemented?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org
RE: [GitMigration] Rename Git Mirrors for XML Graphics Project
Posted by Simon Steiner <si...@gmail.com>.
Hi,
I think the overhead it adds, issues arounds CI failing for reasons outside of your control.
Can you rerun github pr ci if it fails.
If your changing something that wont affect CI such as a small typo, documentation?
For large changes it is good to open a code review.
Thanks
-----Original Message-----
From: Glenn Adams <gl...@skynav.com>
Sent: 07 March 2023 20:33
To: general@xmlgraphics.apache.org
Subject: Re: [GitMigration] Rename Git Mirrors for XML Graphics Project
I haven't done that yet, though I would like to do so. There are a variety of reasons for requiring PRs, including
- ensure that GitHub actions, such as build, test, analyze, are
completed (in PR branch) successfully before merging into main
- ensure that PR conversation (including discussion resolution) and
changes are recorded and retained for future reference
- enable (optional) review processing, should it be desired
Given that it takes only a few mouse clicks in GH to create a PR from a commit on a private branch, is there any reason we shouldn't use PRs for all prospective merges? We should take advantage of the tools gained from migrating to Git, yes?
On Tue, Mar 7, 2023 at 12:47 PM Simon Steiner <si...@gmail.com>
wrote:
> Glenn are you making PRs required for the git repos, should this go
> thru a vote before being implemented?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org
Re: [GitMigration] Rename Git Mirrors for XML Graphics Project
Posted by Glenn Adams <gl...@skynav.com>.
I haven't done that yet, though I would like to do so. There are a variety
of reasons for requiring PRs, including
- ensure that GitHub actions, such as build, test, analyze, are
completed (in PR branch) successfully before merging into main
- ensure that PR conversation (including discussion resolution) and
changes are recorded and retained for future reference
- enable (optional) review processing, should it be desired
Given that it takes only a few mouse clicks in GH to create a PR from a
commit on a private branch, is there any reason we shouldn't use PRs for
all prospective merges? We should take advantage of the tools gained from
migrating to Git, yes?
On Tue, Mar 7, 2023 at 12:47 PM Simon Steiner <si...@gmail.com>
wrote:
> Glenn are you making PRs required for the git repos, should this go thru a
> vote before being implemented?
>
RE: [GitMigration] Rename Git Mirrors for XML Graphics Project
Posted by Simon Steiner <si...@gmail.com>.
Hi,
Seems your config isn’t doing that.
Thanks
-----Original Message-----
From: Simon Steiner <si...@gmail.com>
Sent: 07 March 2023 18:47
To: general@xmlgraphics.apache.org
Subject: RE: [GitMigration] Rename Git Mirrors for XML Graphics Project
Hi,
Glenn are you making PRs required for the git repos, should this go thru a vote before being implemented?
Thanks
-----Original Message-----
From: The Web Maestro <th...@gmail.com>
Sent: 07 March 2023 16:40
To: general@xmlgraphics.apache.org
Subject: Re: [GitMigration] Rename Git Mirrors for XML Graphics Project
+1
On Tue, Mar 7, 2023 at 5:35 AM Simon Steiner <si...@gmail.com>
wrote:
> Hi,
>
> Should we remove commits to personal branches away from the mailing
> list or we get too many emails.
>
> Thanks
>
> -----Original Message-----
> From: Glenn Adams <gl...@skynav.com>
> Sent: 23 February 2023 14:55
> To: XML Graphics Project <ge...@xmlgraphics.apache.org>
> Subject: Re: [GitMigration] Rename Git Mirrors for XML Graphics
> Project
>
> I failed to mention that if you already have a local copy of any of
> these repos, then you should perform the following steps to update the
> local default branch (from trunk to main):
>
> git branch -m trunk main
> git fetch origin
> git branch -u origin/main main
> git remote set-head origin -a
>
>
> On Wed, Feb 22, 2023 at 10:58 PM Glenn Adams <gl...@skynav.com> wrote:
>
> > The following XML Graphics Project repositories are now dual-hosted
> > as writeable GitBox/GitHub repositories, and the previous SVN
> > repositories have been switched to read-only mode.
> >
> > - xmlgraphics-batik <https://github.com/apache/xmlgraphics-batik>
> > - xmlgraphics-commons <https://github.com/apache/xmlgraphics-commons>
> > - xmlgraphics-fop <https://github.com/apache/xmlgraphics-fop>
> > - xmlgraphics-fop-pdf-images
> > <https://github.com/apache/xmlgraphics-fop-pdf-images>
> >
> > I expect some additional tweaks will be needed to put everything in
> > order, such as the CI (currently Jenkins) configurations, site
> > documentation linkage (via git submodules), etc. I will advise
> > further on these matters.
> >
> > Regards,
> > Glenn
> >
> > On Thu, Feb 16, 2023 at 11:01 PM Glenn Adams <gl...@skynav.com> wrote:
> >
> >> Dear All,
> >>
> >> I just filed INFRA-24218 [1] to begin the process of migrating the
> >> xmlgraphics SVN repositories to GitBox/GitHub.
> >>
> >> I will coordinate with the project the starting date/time of the
> >> migration after which further commits to the SVN repositories
> >> should not be performed.
> >>
> >> Regards,
> >> Glenn
> >>
> >> [1] https://issues.apache.org/jira/browse/INFRA-24218
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: general-help@xmlgraphics.apache.org
>
>
--
Kind regards,
Clay Leeds
--
<th...@gmail.com> - <http://ourlil.com/> My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org
RE: [GitMigration] Rename Git Mirrors for XML Graphics Project
Posted by Simon Steiner <si...@gmail.com>.
Hi,
Glenn are you making PRs required for the git repos, should this go thru a vote before being implemented?
Thanks
-----Original Message-----
From: The Web Maestro <th...@gmail.com>
Sent: 07 March 2023 16:40
To: general@xmlgraphics.apache.org
Subject: Re: [GitMigration] Rename Git Mirrors for XML Graphics Project
+1
On Tue, Mar 7, 2023 at 5:35 AM Simon Steiner <si...@gmail.com>
wrote:
> Hi,
>
> Should we remove commits to personal branches away from the mailing
> list or we get too many emails.
>
> Thanks
>
> -----Original Message-----
> From: Glenn Adams <gl...@skynav.com>
> Sent: 23 February 2023 14:55
> To: XML Graphics Project <ge...@xmlgraphics.apache.org>
> Subject: Re: [GitMigration] Rename Git Mirrors for XML Graphics
> Project
>
> I failed to mention that if you already have a local copy of any of
> these repos, then you should perform the following steps to update the
> local default branch (from trunk to main):
>
> git branch -m trunk main
> git fetch origin
> git branch -u origin/main main
> git remote set-head origin -a
>
>
> On Wed, Feb 22, 2023 at 10:58 PM Glenn Adams <gl...@skynav.com> wrote:
>
> > The following XML Graphics Project repositories are now dual-hosted
> > as writeable GitBox/GitHub repositories, and the previous SVN
> > repositories have been switched to read-only mode.
> >
> > - xmlgraphics-batik <https://github.com/apache/xmlgraphics-batik>
> > - xmlgraphics-commons <https://github.com/apache/xmlgraphics-commons>
> > - xmlgraphics-fop <https://github.com/apache/xmlgraphics-fop>
> > - xmlgraphics-fop-pdf-images
> > <https://github.com/apache/xmlgraphics-fop-pdf-images>
> >
> > I expect some additional tweaks will be needed to put everything in
> > order, such as the CI (currently Jenkins) configurations, site
> > documentation linkage (via git submodules), etc. I will advise
> > further on these matters.
> >
> > Regards,
> > Glenn
> >
> > On Thu, Feb 16, 2023 at 11:01 PM Glenn Adams <gl...@skynav.com> wrote:
> >
> >> Dear All,
> >>
> >> I just filed INFRA-24218 [1] to begin the process of migrating the
> >> xmlgraphics SVN repositories to GitBox/GitHub.
> >>
> >> I will coordinate with the project the starting date/time of the
> >> migration after which further commits to the SVN repositories
> >> should not be performed.
> >>
> >> Regards,
> >> Glenn
> >>
> >> [1] https://issues.apache.org/jira/browse/INFRA-24218
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: general-help@xmlgraphics.apache.org
>
>
--
Kind regards,
Clay Leeds
--
<th...@gmail.com> - <http://ourlil.com/> My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org
Re: [GitMigration] Rename Git Mirrors for XML Graphics Project
Posted by The Web Maestro <th...@gmail.com>.
+1
On Tue, Mar 7, 2023 at 5:35 AM Simon Steiner <si...@gmail.com>
wrote:
> Hi,
>
> Should we remove commits to personal branches away from the mailing list
> or we get too many emails.
>
> Thanks
>
> -----Original Message-----
> From: Glenn Adams <gl...@skynav.com>
> Sent: 23 February 2023 14:55
> To: XML Graphics Project <ge...@xmlgraphics.apache.org>
> Subject: Re: [GitMigration] Rename Git Mirrors for XML Graphics Project
>
> I failed to mention that if you already have a local copy of any of these
> repos, then you should perform the following steps to update the local
> default branch (from trunk to main):
>
> git branch -m trunk main
> git fetch origin
> git branch -u origin/main main
> git remote set-head origin -a
>
>
> On Wed, Feb 22, 2023 at 10:58 PM Glenn Adams <gl...@skynav.com> wrote:
>
> > The following XML Graphics Project repositories are now dual-hosted as
> > writeable GitBox/GitHub repositories, and the previous SVN
> > repositories have been switched to read-only mode.
> >
> > - xmlgraphics-batik <https://github.com/apache/xmlgraphics-batik>
> > - xmlgraphics-commons <https://github.com/apache/xmlgraphics-commons>
> > - xmlgraphics-fop <https://github.com/apache/xmlgraphics-fop>
> > - xmlgraphics-fop-pdf-images
> > <https://github.com/apache/xmlgraphics-fop-pdf-images>
> >
> > I expect some additional tweaks will be needed to put everything in
> > order, such as the CI (currently Jenkins) configurations, site
> > documentation linkage (via git submodules), etc. I will advise further
> > on these matters.
> >
> > Regards,
> > Glenn
> >
> > On Thu, Feb 16, 2023 at 11:01 PM Glenn Adams <gl...@skynav.com> wrote:
> >
> >> Dear All,
> >>
> >> I just filed INFRA-24218 [1] to begin the process of migrating the
> >> xmlgraphics SVN repositories to GitBox/GitHub.
> >>
> >> I will coordinate with the project the starting date/time of the
> >> migration after which further commits to the SVN repositories should
> >> not be performed.
> >>
> >> Regards,
> >> Glenn
> >>
> >> [1] https://issues.apache.org/jira/browse/INFRA-24218
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: general-help@xmlgraphics.apache.org
>
>
--
Kind regards,
Clay Leeds
--
<th...@gmail.com> - <http://ourlil.com/>
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet
Re: [GitMigration] Rename Git Mirrors for XML Graphics Project
Posted by Chris Bowditch <bo...@hotmail.com>.
+1
On 07/03/2023 13:35, Simon Steiner wrote:
> Hi,
>
> Should we remove commits to personal branches away from the mailing list or we get too many emails.
>
> Thanks
>
> -----Original Message-----
> From: Glenn Adams <gl...@skynav.com>
> Sent: 23 February 2023 14:55
> To: XML Graphics Project <ge...@xmlgraphics.apache.org>
> Subject: Re: [GitMigration] Rename Git Mirrors for XML Graphics Project
>
> I failed to mention that if you already have a local copy of any of these repos, then you should perform the following steps to update the local default branch (from trunk to main):
>
> git branch -m trunk main
> git fetch origin
> git branch -u origin/main main
> git remote set-head origin -a
>
>
> On Wed, Feb 22, 2023 at 10:58 PM Glenn Adams <gl...@skynav.com> wrote:
>
>> The following XML Graphics Project repositories are now dual-hosted as
>> writeable GitBox/GitHub repositories, and the previous SVN
>> repositories have been switched to read-only mode.
>>
>> - xmlgraphics-batik <https://github.com/apache/xmlgraphics-batik>
>> - xmlgraphics-commons <https://github.com/apache/xmlgraphics-commons>
>> - xmlgraphics-fop <https://github.com/apache/xmlgraphics-fop>
>> - xmlgraphics-fop-pdf-images
>> <https://github.com/apache/xmlgraphics-fop-pdf-images>
>>
>> I expect some additional tweaks will be needed to put everything in
>> order, such as the CI (currently Jenkins) configurations, site
>> documentation linkage (via git submodules), etc. I will advise further
>> on these matters.
>>
>> Regards,
>> Glenn
>>
>> On Thu, Feb 16, 2023 at 11:01 PM Glenn Adams <gl...@skynav.com> wrote:
>>
>>> Dear All,
>>>
>>> I just filed INFRA-24218 [1] to begin the process of migrating the
>>> xmlgraphics SVN repositories to GitBox/GitHub.
>>>
>>> I will coordinate with the project the starting date/time of the
>>> migration after which further commits to the SVN repositories should
>>> not be performed.
>>>
>>> Regards,
>>> Glenn
>>>
>>> [1] https://issues.apache.org/jira/browse/INFRA-24218
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: general-help@xmlgraphics.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org
Re: [GitMigration] Rename Git Mirrors for XML Graphics Project
Posted by Glenn Adams <gl...@skynav.com>.
I haven't found a way to remove/suppress notifications for pushes to a
non-main branch. Moreover, some members of the commits ML may actually want
to see them all.
If you use GMail and want to search for these notifications, you can use
the following:
list:commits.xmlgraphics.apache.org gitbox.apache.org {"pushed a commit"
"pushed a change"} -{"to branch main" "to branch master"}
or, for a corresponding filter (but note truncation of {"pushed a commit"
"pushed a change"} in the following screenshot):
[image: Screen Shot 2023-03-07 at 21.11.49.png]
[image: Screen Shot 2023-03-07 at 21.12.22.png]
On Tue, Mar 7, 2023 at 7:35 AM Simon Steiner <si...@gmail.com>
wrote:
> Should we remove commits to personal branches away from the mailing list
> or we get too many emails.
>
RE: [GitMigration] Rename Git Mirrors for XML Graphics Project
Posted by Simon Steiner <si...@gmail.com>.
Hi,
Should we remove commits to personal branches away from the mailing list or we get too many emails.
Thanks
-----Original Message-----
From: Glenn Adams <gl...@skynav.com>
Sent: 23 February 2023 14:55
To: XML Graphics Project <ge...@xmlgraphics.apache.org>
Subject: Re: [GitMigration] Rename Git Mirrors for XML Graphics Project
I failed to mention that if you already have a local copy of any of these repos, then you should perform the following steps to update the local default branch (from trunk to main):
git branch -m trunk main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a
On Wed, Feb 22, 2023 at 10:58 PM Glenn Adams <gl...@skynav.com> wrote:
> The following XML Graphics Project repositories are now dual-hosted as
> writeable GitBox/GitHub repositories, and the previous SVN
> repositories have been switched to read-only mode.
>
> - xmlgraphics-batik <https://github.com/apache/xmlgraphics-batik>
> - xmlgraphics-commons <https://github.com/apache/xmlgraphics-commons>
> - xmlgraphics-fop <https://github.com/apache/xmlgraphics-fop>
> - xmlgraphics-fop-pdf-images
> <https://github.com/apache/xmlgraphics-fop-pdf-images>
>
> I expect some additional tweaks will be needed to put everything in
> order, such as the CI (currently Jenkins) configurations, site
> documentation linkage (via git submodules), etc. I will advise further
> on these matters.
>
> Regards,
> Glenn
>
> On Thu, Feb 16, 2023 at 11:01 PM Glenn Adams <gl...@skynav.com> wrote:
>
>> Dear All,
>>
>> I just filed INFRA-24218 [1] to begin the process of migrating the
>> xmlgraphics SVN repositories to GitBox/GitHub.
>>
>> I will coordinate with the project the starting date/time of the
>> migration after which further commits to the SVN repositories should
>> not be performed.
>>
>> Regards,
>> Glenn
>>
>> [1] https://issues.apache.org/jira/browse/INFRA-24218
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org
Re: [GitMigration] Rename Git Mirrors for XML Graphics Project
Posted by The Web Maestro <th...@gmail.com>.
Thank you Glenn!
On Thu, Feb 23, 2023 at 6:54 AM Glenn Adams <gl...@skynav.com> wrote:
> I failed to mention that if you already have a local copy of any of these
> repos, then you should perform the following steps
> to update the local default branch (from trunk to main):
>
> git branch -m trunk main
> git fetch origin
> git branch -u origin/main main
> git remote set-head origin -a
>
>
> On Wed, Feb 22, 2023 at 10:58 PM Glenn Adams <gl...@skynav.com> wrote:
>
> > The following XML Graphics Project repositories are now dual-hosted as
> > writeable GitBox/GitHub repositories,
> > and the previous SVN repositories have been switched to read-only mode.
> >
> > - xmlgraphics-batik <https://github.com/apache/xmlgraphics-batik>
> > - xmlgraphics-commons <https://github.com/apache/xmlgraphics-commons>
> > - xmlgraphics-fop <https://github.com/apache/xmlgraphics-fop>
> > - xmlgraphics-fop-pdf-images
> > <https://github.com/apache/xmlgraphics-fop-pdf-images>
> >
> > I expect some additional tweaks will be needed to put everything in
> order,
> > such as the CI (currently Jenkins)
> > configurations, site documentation linkage (via git submodules), etc. I
> > will advise further on these matters.
> >
> > Regards,
> > Glenn
> >
> > On Thu, Feb 16, 2023 at 11:01 PM Glenn Adams <gl...@skynav.com> wrote:
> >
> >> Dear All,
> >>
> >> I just filed INFRA-24218 [1] to begin the process of migrating the
> >> xmlgraphics SVN repositories to GitBox/GitHub.
> >>
> >> I will coordinate with the project the starting date/time of the
> >> migration after which further commits to the SVN repositories should
> not be
> >> performed.
> >>
> >> Regards,
> >> Glenn
> >>
> >> [1] https://issues.apache.org/jira/browse/INFRA-24218
> >>
> >
>
--
Kind regards,
Clay Leeds
--
<th...@gmail.com> - <http://ourlil.com/>
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet
Re: [GitMigration] Rename Git Mirrors for XML Graphics Project
Posted by Glenn Adams <gl...@skynav.com>.
I failed to mention that if you already have a local copy of any of these
repos, then you should perform the following steps
to update the local default branch (from trunk to main):
git branch -m trunk main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a
On Wed, Feb 22, 2023 at 10:58 PM Glenn Adams <gl...@skynav.com> wrote:
> The following XML Graphics Project repositories are now dual-hosted as
> writeable GitBox/GitHub repositories,
> and the previous SVN repositories have been switched to read-only mode.
>
> - xmlgraphics-batik <https://github.com/apache/xmlgraphics-batik>
> - xmlgraphics-commons <https://github.com/apache/xmlgraphics-commons>
> - xmlgraphics-fop <https://github.com/apache/xmlgraphics-fop>
> - xmlgraphics-fop-pdf-images
> <https://github.com/apache/xmlgraphics-fop-pdf-images>
>
> I expect some additional tweaks will be needed to put everything in order,
> such as the CI (currently Jenkins)
> configurations, site documentation linkage (via git submodules), etc. I
> will advise further on these matters.
>
> Regards,
> Glenn
>
> On Thu, Feb 16, 2023 at 11:01 PM Glenn Adams <gl...@skynav.com> wrote:
>
>> Dear All,
>>
>> I just filed INFRA-24218 [1] to begin the process of migrating the
>> xmlgraphics SVN repositories to GitBox/GitHub.
>>
>> I will coordinate with the project the starting date/time of the
>> migration after which further commits to the SVN repositories should not be
>> performed.
>>
>> Regards,
>> Glenn
>>
>> [1] https://issues.apache.org/jira/browse/INFRA-24218
>>
>
Re: [GitMigration] Rename Git Mirrors for XML Graphics Project
Posted by Glenn Adams <gl...@skynav.com>.
The following XML Graphics Project repositories are now dual-hosted as
writeable GitBox/GitHub repositories,
and the previous SVN repositories have been switched to read-only mode.
- xmlgraphics-batik <https://github.com/apache/xmlgraphics-batik>
- xmlgraphics-commons <https://github.com/apache/xmlgraphics-commons>
- xmlgraphics-fop <https://github.com/apache/xmlgraphics-fop>
- xmlgraphics-fop-pdf-images
<https://github.com/apache/xmlgraphics-fop-pdf-images>
I expect some additional tweaks will be needed to put everything in order,
such as the CI (currently Jenkins)
configurations, site documentation linkage (via git submodules), etc. I
will advise further on these matters.
Regards,
Glenn
On Thu, Feb 16, 2023 at 11:01 PM Glenn Adams <gl...@skynav.com> wrote:
> Dear All,
>
> I just filed INFRA-24218 [1] to begin the process of migrating the
> xmlgraphics SVN repositories to GitBox/GitHub.
>
> I will coordinate with the project the starting date/time of the migration
> after which further commits to the SVN repositories should not be performed.
>
> Regards,
> Glenn
>
> [1] https://issues.apache.org/jira/browse/INFRA-24218
>