Uploaded image for project: 'Lucene - Core'
  1. Lucene - Core
  2. LUCENE-7543

Make changes-to-html target an offline operation

    Details

    • Lucene Fields:
      New

      Description

      Currently changes-to-html pulls release dates from JIRA, and so fails when JIRA is inaccessible (e.g. from behind a firewall).

      SOLR-9711 advocates adding a build sysprop to ignore JIRA connection failures, but I'd rather make the operation always offline.

      In an offline discussion, Hoss Man advocated moving Lucene's and Solr's doap.rdf files, which contain all of the release dates that the changes-to-html now pulls from JIRA, from the CMS Subversion repository (downloadable from the website at http://lucene.apache.org/core/doap.rdf and http://lucene.apache.org/solr/doap.rdf) to the Lucene/Solr git repository. If we did that, then the process could be entirely offline if release dates were taken from the local doap.rdf files instead of downloaded from JIRA.

      1. LUCENE-7543.patch
        40 kB
        Steve Rowe
      2. LUCENE-7543.patch
        43 kB
        Mano Kovacs
      3. LUCENE-7543.patch
        32 kB
        Mano Kovacs
      4. LUCENE-7543-drop-XML-Simple.patch
        6 kB
        Steve Rowe

        Issue Links

          Activity

          Hide
          arafalov Alexandre Rafalovitch added a comment -

          Just to clarify.
          Currently the (perl) script pulls the information from JIRA, right? So, it is maintained as part of the issue tagging/release process.

          So, what uses doap.rdf and how is it kept up to date? And if it is moved to GitHub, do we abandon the original location/processes?

          Show
          arafalov Alexandre Rafalovitch added a comment - Just to clarify. Currently the (perl) script pulls the information from JIRA, right? So, it is maintained as part of the issue tagging/release process. So, what uses doap.rdf and how is it kept up to date? And if it is moved to GitHub, do we abandon the original location/processes?
          Hide
          manokovacs Mano Kovacs added a comment -

          Steve Rowe, is there anything I could help with this task? If you share the details of the planned implementation, I could create a patch.

          Show
          manokovacs Mano Kovacs added a comment - Steve Rowe , is there anything I could help with this task? If you share the details of the planned implementation, I could create a patch.
          Hide
          steve_rowe Steve Rowe added a comment -

          So, what uses doap.rdf and how is it kept up to date?

          I'm not sure what uses it, but keeping it up-to-date is part of the ReleaseToDo.

          And if it is moved to GitHub, do we abandon the original location/processes?

          It won't be moved to GitHub of course, but rather to the Apache Git repo.

          These files are currently hosted in the Lucene/Solr CMS-based website repository. An extra release step will be required if we move it to the Git repo, so that the files will continue to be present on the website, similarly to how javadocs are now copied to the website. (I don't think keeping two copies of these files, one in Git and one in the CMS repo, would be a good alternative.)

          Show
          steve_rowe Steve Rowe added a comment - So, what uses doap.rdf and how is it kept up to date? I'm not sure what uses it, but keeping it up-to-date is part of the ReleaseToDo. And if it is moved to GitHub, do we abandon the original location/processes? It won't be moved to GitHub of course, but rather to the Apache Git repo. These files are currently hosted in the Lucene/Solr CMS-based website repository. An extra release step will be required if we move it to the Git repo, so that the files will continue to be present on the website, similarly to how javadocs are now copied to the website. (I don't think keeping two copies of these files, one in Git and one in the CMS repo, would be a good alternative.)
          Hide
          steve_rowe Steve Rowe added a comment -

          Steve Rowe, is there anything I could help with this task? If you share the details of the planned implementation, I could create a patch.

          Yes, that would be great, thanks!. Here's what I was going to do (but haven't really started #3 yet):

          1. Download the doap.rdf files
          2. Put them in place in a cloned Lucene/Solr Git repo (probably at lucene/ and solr/).
          3. Edit these two files to contain the same dates as JIRA has - you can look at how current changes-to-html pulls release info from JIRA and do the same thing to get the raw data. If there are conflicts, I think JIRA is probably more authoritative.
          4. Figure out how to parse the doap.rdf files, rather than the JIRA version output. (I'm being vague because I haven't looked at details of what's involved here.)
          5. Use doap.rdf release dates rather than those from JIRA.
          6. Stop downloading version data from JIRA.
          Show
          steve_rowe Steve Rowe added a comment - Steve Rowe , is there anything I could help with this task? If you share the details of the planned implementation, I could create a patch. Yes, that would be great, thanks!. Here's what I was going to do (but haven't really started #3 yet): Download the doap.rdf files Put them in place in a cloned Lucene/Solr Git repo (probably at lucene/ and solr/ ). Edit these two files to contain the same dates as JIRA has - you can look at how current changes-to-html pulls release info from JIRA and do the same thing to get the raw data. If there are conflicts, I think JIRA is probably more authoritative. Figure out how to parse the doap.rdf files, rather than the JIRA version output. (I'm being vague because I haven't looked at details of what's involved here.) Use doap.rdf release dates rather than those from JIRA. Stop downloading version data from JIRA.
          Hide
          hossman Hoss Man added a comment -

          Thanks for filing this jira steve, I'd forgotten about this conversation...

          So, what uses doap.rdf and how is it kept up to date? And if it is moved to GitHub, do we abandon the original location/processes?

          The doap.rdf files are published publicly on the lucene website for consumption by any system (internal or external) that wants to know about the history of solr/lucene releases – DOAP is an RDF standard for this purpose, much like FOAF.

          Notably the doap.rdf files power projects.apache.org...

          In theory the DOAP files could be auto generated by some system like Jira, but it's a good idea to edit them manually for the express purpose of being able to correct mistakes (ie: they are living documents)

          An extra release step will be required if we move it to the Git repo, so that the files will continue to be present on the website, similarly to how javadocs are now copied to the website.

          that would not be neccessary...

          from an external perspective, the doap files just have to be available at some public / well-known URL. traditionally that has been...

          ...but there is no reason the well known & public URLs can't be things like "https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;f=solr/doap.rdf;a=blob_plain;hb=HEAD" that are served directly form source control (the projects.apache.org instructions actually suggest that approach) and we could add some .htaccess rules to the website to make the existing URLs redirect to new URLs served directly from GIT.

          From an internal perspective we just have to update this list to point wherever we want...
          https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/projects.xml

          2. Put them in place in a cloned Lucene/Solr Git repo (probably at lucene/ and solr/).

          I would suggest they might make more sense in dev-tools? just a gut feeling.

          Show
          hossman Hoss Man added a comment - Thanks for filing this jira steve, I'd forgotten about this conversation... So, what uses doap.rdf and how is it kept up to date? And if it is moved to GitHub, do we abandon the original location/processes? The doap.rdf files are published publicly on the lucene website for consumption by any system (internal or external) that wants to know about the history of solr/lucene releases – DOAP is an RDF standard for this purpose, much like FOAF. Notably the doap.rdf files power projects.apache.org... https://projects.apache.org/doap.html https://projects.apache.org/committee.html?lucene https://projects.apache.org/project.html?lucene-core https://projects.apache.org/project.html?lucene-solr In theory the DOAP files could be auto generated by some system like Jira, but it's a good idea to edit them manually for the express purpose of being able to correct mistakes (ie: they are living documents) An extra release step will be required if we move it to the Git repo, so that the files will continue to be present on the website, similarly to how javadocs are now copied to the website. that would not be neccessary... from an external perspective, the doap files just have to be available at some public / well-known URL. traditionally that has been... http://lucene.apache.org/core/doap.rdf http://lucene.apache.org/solr/doap.rdf ...but there is no reason the well known & public URLs can't be things like "https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;f=solr/doap.rdf;a=blob_plain;hb=HEAD" that are served directly form source control (the projects.apache.org instructions actually suggest that approach) and we could add some .htaccess rules to the website to make the existing URLs redirect to new URLs served directly from GIT. From an internal perspective we just have to update this list to point wherever we want... https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/projects.xml 2. Put them in place in a cloned Lucene/Solr Git repo (probably at lucene/ and solr/). I would suggest they might make more sense in dev-tools? just a gut feeling.
          Hide
          steve_rowe Steve Rowe added a comment -

          Thaks hoss, +1 to all your suggestions - I'd forgotten about the ability to put the doap.rdf files wherever we wanted.

          2. Put them in place in a cloned Lucene/Solr Git repo (probably at lucene/ and solr/).

          I would suggest they might make more sense in dev-tools? just a gut feeling.

          Sure, maybe dev-tools/doap/lucene/doap.rdf and dev-tools/doap/solr/doap.rdf - alternatively I guess we could rename them to lucene-doap.rdf and solr-doap.rdf and put them directly in dev-tools/, but I prefer the former.

          Show
          steve_rowe Steve Rowe added a comment - Thaks hoss, +1 to all your suggestions - I'd forgotten about the ability to put the doap.rdf files wherever we wanted. 2. Put them in place in a cloned Lucene/Solr Git repo (probably at lucene/ and solr/). I would suggest they might make more sense in dev-tools? just a gut feeling. Sure, maybe dev-tools/doap/lucene/doap.rdf and dev-tools/doap/solr/doap.rdf - alternatively I guess we could rename them to lucene-doap.rdf and solr-doap.rdf and put them directly in dev-tools/ , but I prefer the former.
          Hide
          hossman Hoss Man added a comment -

          or just dev-tools/doap/lucene.rdf and dev-tools/doap/solr.rdf (with a README.txt in the same dir explaining to future devs why that dir is there) ... or whatever names we like ... there's no rule that the filenames / URLs has to have "doap" in them ... the bike sheds can be any color we want.

          Show
          hossman Hoss Man added a comment - or just dev-tools/doap/lucene.rdf and dev-tools/doap/solr.rdf (with a README.txt in the same dir explaining to future devs why that dir is there) ... or whatever names we like ... there's no rule that the filenames / URLs has to have "doap" in them ... the bike sheds can be any color we want.
          Hide
          steve_rowe Steve Rowe added a comment -

          or just dev-tools/doap/lucene.rdf and dev-tools/doap/solr.rdf (with a README.txt in the same dir explaining to future devs why that dir is there)

          +1

          Show
          steve_rowe Steve Rowe added a comment - or just dev-tools/doap/lucene.rdf and dev-tools/doap/solr.rdf (with a README.txt in the same dir explaining to future devs why that dir is there) +1
          Hide
          manokovacs Mano Kovacs added a comment -

          Steve Rowe, Hoss Man, thanks for the detailed outline for the implementation! I started the change, mostly done with the perl-script as well, but I noticed lucene.rdf has release versions and dates since 3.1 (only lucene, solr is fine). I am going to copy the missing from jira if that is fine with you.

          Show
          manokovacs Mano Kovacs added a comment - Steve Rowe , Hoss Man , thanks for the detailed outline for the implementation! I started the change, mostly done with the perl-script as well, but I noticed lucene.rdf has release versions and dates since 3.1 (only lucene, solr is fine). I am going to copy the missing from jira if that is fine with you.
          Hide
          steve_rowe Steve Rowe added a comment -

          I noticed lucene.rdf has release versions and dates since 3.1 (only lucene, solr is fine). I am going to copy the missing from jira if that is fine with you.

          +1, yeah, I noticed the same; that's in part what I meant when I said "Edit these two files to contain the same dates as JIRA has".

          Show
          steve_rowe Steve Rowe added a comment - I noticed lucene.rdf has release versions and dates since 3.1 (only lucene, solr is fine). I am going to copy the missing from jira if that is fine with you. +1, yeah, I noticed the same; that's in part what I meant when I said "Edit these two files to contain the same dates as JIRA has".
          Hide
          manokovacs Mano Kovacs added a comment -

          Adding first patch with solr.rdf and lucene.rdf, changed changes2html.pl and updated ant scripts. The rdf files are as-is, since missing dates were already hardcoded into changes2html.pl. I could move the hardcoded dates and add to lucene.rdf instead, if requested.

          Show
          manokovacs Mano Kovacs added a comment - Adding first patch with solr.rdf and lucene.rdf, changed changes2html.pl and updated ant scripts. The rdf files are as-is, since missing dates were already hardcoded into changes2html.pl. I could move the hardcoded dates and add to lucene.rdf instead, if requested.
          Hide
          steve_rowe Steve Rowe added a comment -

          I could move the hardcoded dates and add to lucene.rdf instead, if requested.

          Please do.

          Show
          steve_rowe Steve Rowe added a comment - I could move the hardcoded dates and add to lucene.rdf instead, if requested. Please do.
          Hide
          manokovacs Mano Kovacs added a comment -

          Ok, I added the versions from the jira json. However, the "-final", "RCx" and "1.01b" releases are not in any source. Is it ok to add them into the RDF as-is?

          Show
          manokovacs Mano Kovacs added a comment - Ok, I added the versions from the jira json. However, the "-final", "RCx" and "1.01b" releases are not in any source. Is it ok to add them into the RDF as-is?
          Hide
          steve_rowe Steve Rowe added a comment -

          With your first patch I ran ant changes-to-html in lucene/ and I see many releases' dates missing. I double checked that this is a new problem by looking at http://lucene.apache.org/core/6_3_0/changes/Changes.html, which doesn't have this problem. A nit: the 6.3.0 release date looks weird because the day-of-month is single digit (unlike all other dates, where it's zero-padded).

          Ok, I added the versions from the jira json. However, the "-final", "RCx" and "1.01b" releases are not in any source. Is it ok to add them into the RDF as-is?

          BTW, the "RCx" releases were treated as if they were real releases at the time, more like -alpha, -beta, etc. than "release candidate" really. The only thing I think worth considering here is whether the "final" modifier should be stripped in the doap.rdf files (even though it will remain in CHANGES.txt/Changes.html). I could go either way. I notice that JIRA lists "1.9 final" as just "1.9" - this is consistent with both the "-alpha/-beta" and "-RCx" naming schemes. The distributions at http://archive.apache.org/dist/lucene/java/archive/ include the "-final" and "-rcX" suffixes in their names, though, so I'd prefer to continue naming these releases in the doap.rdf files the same way as they are named in CHANGES.txt (i.e., include " final" in their names). This has the nice side-effect that no extra mapping step will be required in changes2html.pl.

          Show
          steve_rowe Steve Rowe added a comment - With your first patch I ran ant changes-to-html in lucene/ and I see many releases' dates missing. I double checked that this is a new problem by looking at http://lucene.apache.org/core/6_3_0/changes/Changes.html , which doesn't have this problem. A nit: the 6.3.0 release date looks weird because the day-of-month is single digit (unlike all other dates, where it's zero-padded). Ok, I added the versions from the jira json. However, the "-final", "RCx" and "1.01b" releases are not in any source. Is it ok to add them into the RDF as-is? BTW, the "RCx" releases were treated as if they were real releases at the time, more like -alpha, -beta, etc. than "release candidate" really. The only thing I think worth considering here is whether the "final" modifier should be stripped in the doap.rdf files (even though it will remain in CHANGES.txt/Changes.html). I could go either way. I notice that JIRA lists "1.9 final" as just "1.9" - this is consistent with both the "-alpha/-beta" and "-RCx" naming schemes. The distributions at http://archive.apache.org/dist/lucene/java/archive/ include the "-final" and "-rcX" suffixes in their names, though, so I'd prefer to continue naming these releases in the doap.rdf files the same way as they are named in CHANGES.txt (i.e., include " final" in their names). This has the nice side-effect that no extra mapping step will be required in changes2html.pl .
          Hide
          manokovacs Mano Kovacs added a comment -

          Adding all the versions of lucene into the lucene.rdf. There were many inconsistencies, non of the sources contained all the versions and some versions in the primary sources (jira+doap) were renamed to match the CHANGES.txt (final and RCx additions).

          You can verify the patch ant changes-to-html in solr and lucene folders, output will be in $PROJECT/build/docs/changes/Changes.html.

          Show
          manokovacs Mano Kovacs added a comment - Adding all the versions of lucene into the lucene.rdf. There were many inconsistencies, non of the sources contained all the versions and some versions in the primary sources (jira+doap) were renamed to match the CHANGES.txt (final and RCx additions). You can verify the patch ant changes-to-html in solr and lucene folders, output will be in $PROJECT/build/docs/changes/Changes.html .
          Hide
          steve_rowe Steve Rowe added a comment -

          Thanks Mano.

          I ran changes-to-html for both Lucene and Solr, and all Lucene versions now have dates - cool! Solr, however, is still missing dates for several versions.

          Many of the new Lucene doap.rdf versions are missing branches. For pre-Apache releases this makes sense I think, but thereafter we should theoretically be able to identify the source branches. Also, the source repo is out of date (yes, not directly applicable to this issue), and older branches aren't available via Git (I think some are tags there). I'll investigate.

          Show
          steve_rowe Steve Rowe added a comment - Thanks Mano. I ran changes-to-html for both Lucene and Solr, and all Lucene versions now have dates - cool! Solr, however, is still missing dates for several versions. Many of the new Lucene doap.rdf versions are missing branches. For pre-Apache releases this makes sense I think, but thereafter we should theoretically be able to identify the source branches. Also, the source repo is out of date (yes, not directly applicable to this issue), and older branches aren't available via Git (I think some are tags there). I'll investigate.
          Hide
          steve_rowe Steve Rowe added a comment -

          Patch that cleans up the DOAP files in several ways (removed unreleased versions; added missing versions; put versions in proper order; removed all <branch> mentions from versions, since they are not included in the DOAP schema (https://github.com/edumbill/doap/blob/master/schema/doap.rdf); replaced SVN repo link with Git repo link; added missing XML tags between releases), and improves changes2html.pl (removed file reading routine, since XML::Simple has native file-reading capabilities; improved trailing .0 matching in versions; normalized dates to always be formatted with 2-digit months and days-of-month).

          One DOAP file improvement we might consider in the future: the DOAP format supports <file-release> tag(s) within <release>-s, pointing to downloadable release distribution(s). E.g. Apache Maven uses this feature in its DOAP file: https://git-wip-us.apache.org/repos/asf?p=maven.git;a=blob_plain;f=doap_Maven.rdf;hb=HEAD. However, projects.apache.org doesn't display this information right now (e.g. https://projects.apache.org/project.html?maven).

          I think it's ready. I'll commit shortly.

          Show
          steve_rowe Steve Rowe added a comment - Patch that cleans up the DOAP files in several ways (removed unreleased versions; added missing versions; put versions in proper order; removed all <branch> mentions from versions, since they are not included in the DOAP schema ( https://github.com/edumbill/doap/blob/master/schema/doap.rdf ); replaced SVN repo link with Git repo link; added missing XML tags between releases), and improves changes2html.pl (removed file reading routine, since XML::Simple has native file-reading capabilities; improved trailing .0 matching in versions; normalized dates to always be formatted with 2-digit months and days-of-month). One DOAP file improvement we might consider in the future: the DOAP format supports <file-release> tag(s) within <release> -s, pointing to downloadable release distribution(s). E.g. Apache Maven uses this feature in its DOAP file: https://git-wip-us.apache.org/repos/asf?p=maven.git;a=blob_plain;f=doap_Maven.rdf;hb=HEAD . However, projects.apache.org doesn't display this information right now (e.g. https://projects.apache.org/project.html?maven ). I think it's ready. I'll commit shortly.
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit dd072aa309ed99cfb2fe19ee3b0d5b0d143d8e8e in lucene-solr's branch refs/heads/branch_5_5 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=dd072aa ]

          LUCENE-7543: Make changes-to-html target an offline operation, by moving the Lucene and Solr DOAP RDF files into the Git source repository under dev-tools/doap/ and then pulling release dates from those files, rather than from JIRA.

          Show
          jira-bot ASF subversion and git services added a comment - Commit dd072aa309ed99cfb2fe19ee3b0d5b0d143d8e8e in lucene-solr's branch refs/heads/branch_5_5 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=dd072aa ] LUCENE-7543 : Make changes-to-html target an offline operation, by moving the Lucene and Solr DOAP RDF files into the Git source repository under dev-tools/doap/ and then pulling release dates from those files, rather than from JIRA.
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 4b1be24b2ad20000d03fc85ccd3349a7ea4bbff8 in lucene-solr's branch refs/heads/branch_5_5 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=4b1be24 ]

          LUCENE-7543: added changes entry

          Show
          jira-bot ASF subversion and git services added a comment - Commit 4b1be24b2ad20000d03fc85ccd3349a7ea4bbff8 in lucene-solr's branch refs/heads/branch_5_5 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=4b1be24 ] LUCENE-7543 : added changes entry
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 3972507799b1fc2e543bacfa73ac7b1596a3b281 in lucene-solr's branch refs/heads/branch_5x from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=3972507 ]

          LUCENE-7543: Make changes-to-html target an offline operation, by moving the Lucene and Solr DOAP RDF files into the Git source repository under dev-tools/doap/ and then pulling release dates from those files, rather than from JIRA.

          Show
          jira-bot ASF subversion and git services added a comment - Commit 3972507799b1fc2e543bacfa73ac7b1596a3b281 in lucene-solr's branch refs/heads/branch_5x from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=3972507 ] LUCENE-7543 : Make changes-to-html target an offline operation, by moving the Lucene and Solr DOAP RDF files into the Git source repository under dev-tools/doap/ and then pulling release dates from those files, rather than from JIRA.
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit f150963b4e9791e7e38cba3ed93a19a794aa4f6a in lucene-solr's branch refs/heads/branch_5x from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=f150963 ]

          LUCENE-7543: added changes entry

          Show
          jira-bot ASF subversion and git services added a comment - Commit f150963b4e9791e7e38cba3ed93a19a794aa4f6a in lucene-solr's branch refs/heads/branch_5x from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=f150963 ] LUCENE-7543 : added changes entry
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 10e67b5097445ffad2e071fb1ee9d7a46de1a263 in lucene-solr's branch refs/heads/branch_6_0 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=10e67b5 ]

          LUCENE-7543: Make changes-to-html target an offline operation, by moving the Lucene and Solr DOAP RDF files into the Git source repository under dev-tools/doap/ and then pulling release dates from those files, rather than from JIRA.

          Show
          jira-bot ASF subversion and git services added a comment - Commit 10e67b5097445ffad2e071fb1ee9d7a46de1a263 in lucene-solr's branch refs/heads/branch_6_0 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=10e67b5 ] LUCENE-7543 : Make changes-to-html target an offline operation, by moving the Lucene and Solr DOAP RDF files into the Git source repository under dev-tools/doap/ and then pulling release dates from those files, rather than from JIRA.
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 429deea9b350f1c6ae941920b8d4e6ed6a108d2a in lucene-solr's branch refs/heads/branch_6_0 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=429deea ]

          LUCENE-7543: added changes entry

          Show
          jira-bot ASF subversion and git services added a comment - Commit 429deea9b350f1c6ae941920b8d4e6ed6a108d2a in lucene-solr's branch refs/heads/branch_6_0 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=429deea ] LUCENE-7543 : added changes entry
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 69cf982688c3a86273d0f2bb1519721be309281f in lucene-solr's branch refs/heads/branch_6_1 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=69cf982 ]

          LUCENE-7543: Make changes-to-html target an offline operation, by moving the Lucene and Solr DOAP RDF files into the Git source repository under dev-tools/doap/ and then pulling release dates from those files, rather than from JIRA.

          Show
          jira-bot ASF subversion and git services added a comment - Commit 69cf982688c3a86273d0f2bb1519721be309281f in lucene-solr's branch refs/heads/branch_6_1 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=69cf982 ] LUCENE-7543 : Make changes-to-html target an offline operation, by moving the Lucene and Solr DOAP RDF files into the Git source repository under dev-tools/doap/ and then pulling release dates from those files, rather than from JIRA.
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 763dd1a10fa8ccf9a912b9da33aeed900b3f70fc in lucene-solr's branch refs/heads/branch_6_1 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=763dd1a ]

          LUCENE-7543: added changes entry

          Show
          jira-bot ASF subversion and git services added a comment - Commit 763dd1a10fa8ccf9a912b9da33aeed900b3f70fc in lucene-solr's branch refs/heads/branch_6_1 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=763dd1a ] LUCENE-7543 : added changes entry
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 49cf6c04a47b8ef9feb97ce9131f78cad689277e in lucene-solr's branch refs/heads/branch_6_2 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=49cf6c0 ]

          LUCENE-7543: Make changes-to-html target an offline operation, by moving the Lucene and Solr DOAP RDF files into the Git source repository under dev-tools/doap/ and then pulling release dates from those files, rather than from JIRA.

          Show
          jira-bot ASF subversion and git services added a comment - Commit 49cf6c04a47b8ef9feb97ce9131f78cad689277e in lucene-solr's branch refs/heads/branch_6_2 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=49cf6c0 ] LUCENE-7543 : Make changes-to-html target an offline operation, by moving the Lucene and Solr DOAP RDF files into the Git source repository under dev-tools/doap/ and then pulling release dates from those files, rather than from JIRA.
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 1a488f37190a720fb1513469271818060949f754 in lucene-solr's branch refs/heads/branch_6_2 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=1a488f3 ]

          LUCENE-7543: added changes entry

          Show
          jira-bot ASF subversion and git services added a comment - Commit 1a488f37190a720fb1513469271818060949f754 in lucene-solr's branch refs/heads/branch_6_2 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=1a488f3 ] LUCENE-7543 : added changes entry
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 3c885149db7a71572ffd5ff296d08dd38180f593 in lucene-solr's branch refs/heads/branch_6_3 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=3c88514 ]

          LUCENE-7543: Make changes-to-html target an offline operation, by moving the Lucene and Solr DOAP RDF files into the Git source repository under dev-tools/doap/ and then pulling release dates from those files, rather than from JIRA.

          Show
          jira-bot ASF subversion and git services added a comment - Commit 3c885149db7a71572ffd5ff296d08dd38180f593 in lucene-solr's branch refs/heads/branch_6_3 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=3c88514 ] LUCENE-7543 : Make changes-to-html target an offline operation, by moving the Lucene and Solr DOAP RDF files into the Git source repository under dev-tools/doap/ and then pulling release dates from those files, rather than from JIRA.
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 25d2d8d27315fdb5a9b4accbe36d7b12bd2a9243 in lucene-solr's branch refs/heads/branch_6x from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=25d2d8d ]

          LUCENE-7543: Make changes-to-html target an offline operation, by moving the Lucene and Solr DOAP RDF files into the Git source repository under dev-tools/doap/ and then pulling release dates from those files, rather than from JIRA.

          Show
          jira-bot ASF subversion and git services added a comment - Commit 25d2d8d27315fdb5a9b4accbe36d7b12bd2a9243 in lucene-solr's branch refs/heads/branch_6x from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=25d2d8d ] LUCENE-7543 : Make changes-to-html target an offline operation, by moving the Lucene and Solr DOAP RDF files into the Git source repository under dev-tools/doap/ and then pulling release dates from those files, rather than from JIRA.
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 33ff6cde9be9b9ab9c2e4c8f9dc5221bc998b673 in lucene-solr's branch refs/heads/master from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=33ff6cd ]

          LUCENE-7543: Make changes-to-html target an offline operation, by moving the Lucene and Solr DOAP RDF files into the Git source repository under dev-tools/doap/ and then pulling release dates from those files, rather than from JIRA.

          Show
          jira-bot ASF subversion and git services added a comment - Commit 33ff6cde9be9b9ab9c2e4c8f9dc5221bc998b673 in lucene-solr's branch refs/heads/master from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=33ff6cd ] LUCENE-7543 : Make changes-to-html target an offline operation, by moving the Lucene and Solr DOAP RDF files into the Git source repository under dev-tools/doap/ and then pulling release dates from those files, rather than from JIRA.
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 76bad38018e3d17e0e004bcac81c81662ee05632 in lucene-solr's branch refs/heads/branch_5_5 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=76bad38 ]

          LUCENE-7543: Added note to dev-tools/doap/README.txt about maintaining the website .htaccess file. Cleaned up DOAP files: added full Aapache license reference; added info about canonical URLs; dropped useles stylesheet processing instruction.

          Show
          jira-bot ASF subversion and git services added a comment - Commit 76bad38018e3d17e0e004bcac81c81662ee05632 in lucene-solr's branch refs/heads/branch_5_5 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=76bad38 ] LUCENE-7543 : Added note to dev-tools/doap/README.txt about maintaining the website .htaccess file. Cleaned up DOAP files: added full Aapache license reference; added info about canonical URLs; dropped useles stylesheet processing instruction.
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit d41bb6f46a5869d7a18e13258aa26bd2d5713ea0 in lucene-solr's branch refs/heads/branch_5x from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=d41bb6f ]

          LUCENE-7543: Added note to dev-tools/doap/README.txt about maintaining the website .htaccess file. Cleaned up DOAP files: added full Aapache license reference; added info about canonical URLs; dropped useles stylesheet processing instruction.

          Show
          jira-bot ASF subversion and git services added a comment - Commit d41bb6f46a5869d7a18e13258aa26bd2d5713ea0 in lucene-solr's branch refs/heads/branch_5x from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=d41bb6f ] LUCENE-7543 : Added note to dev-tools/doap/README.txt about maintaining the website .htaccess file. Cleaned up DOAP files: added full Aapache license reference; added info about canonical URLs; dropped useles stylesheet processing instruction.
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 97ccb67b1dbb72b4d169071cd6cc30999a367804 in lucene-solr's branch refs/heads/branch_6_0 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=97ccb67 ]

          LUCENE-7543: Added note to dev-tools/doap/README.txt about maintaining the website .htaccess file. Cleaned up DOAP files: added full Aapache license reference; added info about canonical URLs; dropped useles stylesheet processing instruction.

          Show
          jira-bot ASF subversion and git services added a comment - Commit 97ccb67b1dbb72b4d169071cd6cc30999a367804 in lucene-solr's branch refs/heads/branch_6_0 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=97ccb67 ] LUCENE-7543 : Added note to dev-tools/doap/README.txt about maintaining the website .htaccess file. Cleaned up DOAP files: added full Aapache license reference; added info about canonical URLs; dropped useles stylesheet processing instruction.
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit ef989afb649a5ff2794673a17b205af361fa83af in lucene-solr's branch refs/heads/branch_6_1 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=ef989af ]

          LUCENE-7543: Added note to dev-tools/doap/README.txt about maintaining the website .htaccess file. Cleaned up DOAP files: added full Aapache license reference; added info about canonical URLs; dropped useles stylesheet processing instruction.

          Show
          jira-bot ASF subversion and git services added a comment - Commit ef989afb649a5ff2794673a17b205af361fa83af in lucene-solr's branch refs/heads/branch_6_1 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=ef989af ] LUCENE-7543 : Added note to dev-tools/doap/README.txt about maintaining the website .htaccess file. Cleaned up DOAP files: added full Aapache license reference; added info about canonical URLs; dropped useles stylesheet processing instruction.
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 0a6d2508045d2e11b2bfb3f33a177562d2c8a5d8 in lucene-solr's branch refs/heads/branch_6_2 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=0a6d250 ]

          LUCENE-7543: Added note to dev-tools/doap/README.txt about maintaining the website .htaccess file. Cleaned up DOAP files: added full Aapache license reference; added info about canonical URLs; dropped useles stylesheet processing instruction.

          Show
          jira-bot ASF subversion and git services added a comment - Commit 0a6d2508045d2e11b2bfb3f33a177562d2c8a5d8 in lucene-solr's branch refs/heads/branch_6_2 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=0a6d250 ] LUCENE-7543 : Added note to dev-tools/doap/README.txt about maintaining the website .htaccess file. Cleaned up DOAP files: added full Aapache license reference; added info about canonical URLs; dropped useles stylesheet processing instruction.
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 45f34c99dad9bc62ea4a1ab5b1ca8515801e9e48 in lucene-solr's branch refs/heads/branch_6_3 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=45f34c9 ]

          LUCENE-7543: Added note to dev-tools/doap/README.txt about maintaining the website .htaccess file. Cleaned up DOAP files: added full Aapache license reference; added info about canonical URLs; dropped useles stylesheet processing instruction.

          Show
          jira-bot ASF subversion and git services added a comment - Commit 45f34c99dad9bc62ea4a1ab5b1ca8515801e9e48 in lucene-solr's branch refs/heads/branch_6_3 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=45f34c9 ] LUCENE-7543 : Added note to dev-tools/doap/README.txt about maintaining the website .htaccess file. Cleaned up DOAP files: added full Aapache license reference; added info about canonical URLs; dropped useles stylesheet processing instruction.
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit c069dbc147deff79abd1cdd2da329ab426fcd3f8 in lucene-solr's branch refs/heads/branch_6x from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=c069dbc ]

          LUCENE-7543: Added note to dev-tools/doap/README.txt about maintaining the website .htaccess file. Cleaned up DOAP files: added full Aapache license reference; added info about canonical URLs; dropped useles stylesheet processing instruction.

          Show
          jira-bot ASF subversion and git services added a comment - Commit c069dbc147deff79abd1cdd2da329ab426fcd3f8 in lucene-solr's branch refs/heads/branch_6x from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=c069dbc ] LUCENE-7543 : Added note to dev-tools/doap/README.txt about maintaining the website .htaccess file. Cleaned up DOAP files: added full Aapache license reference; added info about canonical URLs; dropped useles stylesheet processing instruction.
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 51db00a313d93e5b24468b5fb70165304cb572eb in lucene-solr's branch refs/heads/master from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=51db00a ]

          LUCENE-7543: Added note to dev-tools/doap/README.txt about maintaining the website .htaccess file. Cleaned up DOAP files: added full Aapache license reference; added info about canonical URLs; dropped useles stylesheet processing instruction.

          Show
          jira-bot ASF subversion and git services added a comment - Commit 51db00a313d93e5b24468b5fb70165304cb572eb in lucene-solr's branch refs/heads/master from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=51db00a ] LUCENE-7543 : Added note to dev-tools/doap/README.txt about maintaining the website .htaccess file. Cleaned up DOAP files: added full Aapache license reference; added info about canonical URLs; dropped useles stylesheet processing instruction.
          Hide
          steve_rowe Steve Rowe added a comment - - edited

          I deleted content/core/doap.rdf and content/solr/doap.rdf from the website CMS Subversion repository, and I edited the website .htaccess file to redirect them to their new homes in the Lucene/Solr Git repository.

          edit fixed Lucene doap file location

          Show
          steve_rowe Steve Rowe added a comment - - edited I deleted content/core/doap.rdf and content/solr/doap.rdf from the website CMS Subversion repository, and I edited the website .htaccess file to redirect them to their new homes in the Lucene/Solr Git repository. edit fixed Lucene doap file location
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 6c539d9b71759c277f3af8fb1c1bb35219b3d828 in lucene-solr's branch refs/heads/branch_5_5 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=6c539d9 ]

          LUCENE-7543: fixed canonical URL in comment

          Show
          jira-bot ASF subversion and git services added a comment - Commit 6c539d9b71759c277f3af8fb1c1bb35219b3d828 in lucene-solr's branch refs/heads/branch_5_5 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=6c539d9 ] LUCENE-7543 : fixed canonical URL in comment
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 65f451b9309ed4994bdf4ced1f7b2a269a621a43 in lucene-solr's branch refs/heads/branch_5x from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=65f451b ]

          LUCENE-7543: fixed canonical URL in comment

          Show
          jira-bot ASF subversion and git services added a comment - Commit 65f451b9309ed4994bdf4ced1f7b2a269a621a43 in lucene-solr's branch refs/heads/branch_5x from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=65f451b ] LUCENE-7543 : fixed canonical URL in comment
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit d7adb97446a53b2a25af3037b81421a1f0347e8b in lucene-solr's branch refs/heads/branch_6_0 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=d7adb97 ]

          LUCENE-7543: fixed canonical URL in comment

          Show
          jira-bot ASF subversion and git services added a comment - Commit d7adb97446a53b2a25af3037b81421a1f0347e8b in lucene-solr's branch refs/heads/branch_6_0 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=d7adb97 ] LUCENE-7543 : fixed canonical URL in comment
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit cf51e5cf74d03d9ed0fd7aa00df7c198067b7288 in lucene-solr's branch refs/heads/branch_6_1 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=cf51e5c ]

          LUCENE-7543: fixed canonical URL in comment

          Show
          jira-bot ASF subversion and git services added a comment - Commit cf51e5cf74d03d9ed0fd7aa00df7c198067b7288 in lucene-solr's branch refs/heads/branch_6_1 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=cf51e5c ] LUCENE-7543 : fixed canonical URL in comment
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 819bea1fdf74aa91f1ef43c7a2ba47fe2f0992c7 in lucene-solr's branch refs/heads/branch_6_2 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=819bea1 ]

          LUCENE-7543: fixed canonical URL in comment

          Show
          jira-bot ASF subversion and git services added a comment - Commit 819bea1fdf74aa91f1ef43c7a2ba47fe2f0992c7 in lucene-solr's branch refs/heads/branch_6_2 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=819bea1 ] LUCENE-7543 : fixed canonical URL in comment
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 8fba114d69535959591091e84a32092a857767e5 in lucene-solr's branch refs/heads/branch_6_3 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=8fba114 ]

          LUCENE-7543: fixed canonical URL in comment

          Show
          jira-bot ASF subversion and git services added a comment - Commit 8fba114d69535959591091e84a32092a857767e5 in lucene-solr's branch refs/heads/branch_6_3 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=8fba114 ] LUCENE-7543 : fixed canonical URL in comment
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit f0f30eec303394105fc256d71bef5567b08bc586 in lucene-solr's branch refs/heads/branch_6x from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=f0f30ee ]

          LUCENE-7543: fixed canonical URL in comment

          Show
          jira-bot ASF subversion and git services added a comment - Commit f0f30eec303394105fc256d71bef5567b08bc586 in lucene-solr's branch refs/heads/branch_6x from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=f0f30ee ] LUCENE-7543 : fixed canonical URL in comment
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit b768a83a1e884fbf65c7044738ea88dac4c38e84 in lucene-solr's branch refs/heads/master from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=b768a83 ]

          LUCENE-7543: fixed canonical URL in comment

          Show
          jira-bot ASF subversion and git services added a comment - Commit b768a83a1e884fbf65c7044738ea88dac4c38e84 in lucene-solr's branch refs/heads/master from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=b768a83 ] LUCENE-7543 : fixed canonical URL in comment
          Hide
          steve_rowe Steve Rowe added a comment -

          Committed.

          Thanks Mano Kovacs!

          Show
          steve_rowe Steve Rowe added a comment - Committed. Thanks Mano Kovacs !
          Hide
          steve_rowe Steve Rowe added a comment -

          Reopening to address Jenkins failures due to missing Perl module XML::Simple.

          Show
          steve_rowe Steve Rowe added a comment - Reopening to address Jenkins failures due to missing Perl module XML::Simple.
          Hide
          steve_rowe Steve Rowe added a comment -

          Patch to parse DOAP RDF files using Ant's <xmlproperty> task, output comma-separated values for the release names and dates to a temporary file, then have changes2html.pl read release dates from the temporary file. This way the Perl XML::Simple module, which may not be available on some users machines (e.g. Jenkins, running Ubuntu) is not required.

          Committing shortly.

          Show
          steve_rowe Steve Rowe added a comment - Patch to parse DOAP RDF files using Ant's <xmlproperty> task, output comma-separated values for the release names and dates to a temporary file, then have changes2html.pl read release dates from the temporary file. This way the Perl XML::Simple module, which may not be available on some users machines (e.g. Jenkins, running Ubuntu) is not required. Committing shortly.
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 71f556621e49f28b04bbd3d749ef422821eb36c7 in lucene-solr's branch refs/heads/branch_5_5 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=71f5566 ]

          LUCENE-7543: Parse DOAP RDF files with Ant <xmlproperty> rather than Perl XML::Simple

          Show
          jira-bot ASF subversion and git services added a comment - Commit 71f556621e49f28b04bbd3d749ef422821eb36c7 in lucene-solr's branch refs/heads/branch_5_5 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=71f5566 ] LUCENE-7543 : Parse DOAP RDF files with Ant <xmlproperty> rather than Perl XML::Simple
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit ff2f1693653f1212cf92d48af684e17d9d0db998 in lucene-solr's branch refs/heads/branch_5x from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=ff2f169 ]

          LUCENE-7543: Parse DOAP RDF files with Ant <xmlproperty> rather than Perl XML::Simple

          Show
          jira-bot ASF subversion and git services added a comment - Commit ff2f1693653f1212cf92d48af684e17d9d0db998 in lucene-solr's branch refs/heads/branch_5x from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=ff2f169 ] LUCENE-7543 : Parse DOAP RDF files with Ant <xmlproperty> rather than Perl XML::Simple
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 4cf901aa9fe1667e90b3aa597d2e0abaf1c9ea22 in lucene-solr's branch refs/heads/branch_6_0 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=4cf901a ]

          LUCENE-7543: Parse DOAP RDF files with Ant <xmlproperty> rather than Perl XML::Simple

          Show
          jira-bot ASF subversion and git services added a comment - Commit 4cf901aa9fe1667e90b3aa597d2e0abaf1c9ea22 in lucene-solr's branch refs/heads/branch_6_0 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=4cf901a ] LUCENE-7543 : Parse DOAP RDF files with Ant <xmlproperty> rather than Perl XML::Simple
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit d8d8c77dc0d7714778a35b57a8d64274c5753596 in lucene-solr's branch refs/heads/branch_6_1 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=d8d8c77 ]

          LUCENE-7543: Parse DOAP RDF files with Ant <xmlproperty> rather than Perl XML::Simple

          Show
          jira-bot ASF subversion and git services added a comment - Commit d8d8c77dc0d7714778a35b57a8d64274c5753596 in lucene-solr's branch refs/heads/branch_6_1 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=d8d8c77 ] LUCENE-7543 : Parse DOAP RDF files with Ant <xmlproperty> rather than Perl XML::Simple
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 2cf3998ff6da7bb8c7beb39d7e25978fdb2eb9a0 in lucene-solr's branch refs/heads/branch_6_2 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=2cf3998 ]

          LUCENE-7543: Parse DOAP RDF files with Ant <xmlproperty> rather than Perl XML::Simple

          Show
          jira-bot ASF subversion and git services added a comment - Commit 2cf3998ff6da7bb8c7beb39d7e25978fdb2eb9a0 in lucene-solr's branch refs/heads/branch_6_2 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=2cf3998 ] LUCENE-7543 : Parse DOAP RDF files with Ant <xmlproperty> rather than Perl XML::Simple
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit e803d20758f772c01b2c4e1dc8fa3fc2a73c0e88 in lucene-solr's branch refs/heads/branch_6_3 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=e803d20 ]

          LUCENE-7543: Parse DOAP RDF files with Ant <xmlproperty> rather than Perl XML::Simple

          Show
          jira-bot ASF subversion and git services added a comment - Commit e803d20758f772c01b2c4e1dc8fa3fc2a73c0e88 in lucene-solr's branch refs/heads/branch_6_3 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=e803d20 ] LUCENE-7543 : Parse DOAP RDF files with Ant <xmlproperty> rather than Perl XML::Simple
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit c85a0d8aa348969f712f7e29e70a7d89d7664e31 in lucene-solr's branch refs/heads/branch_6x from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=c85a0d8 ]

          LUCENE-7543: Parse DOAP RDF files with Ant <xmlproperty> rather than Perl XML::Simple

          Show
          jira-bot ASF subversion and git services added a comment - Commit c85a0d8aa348969f712f7e29e70a7d89d7664e31 in lucene-solr's branch refs/heads/branch_6x from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=c85a0d8 ] LUCENE-7543 : Parse DOAP RDF files with Ant <xmlproperty> rather than Perl XML::Simple
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit c5aa9b9adaa8c94f9b8c0c897b0f3cd84ddbe8b4 in lucene-solr's branch refs/heads/master from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=c5aa9b9 ]

          LUCENE-7543: Parse DOAP RDF files with Ant <xmlproperty> rather than Perl XML::Simple

          Show
          jira-bot ASF subversion and git services added a comment - Commit c5aa9b9adaa8c94f9b8c0c897b0f3cd84ddbe8b4 in lucene-solr's branch refs/heads/master from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=c5aa9b9 ] LUCENE-7543 : Parse DOAP RDF files with Ant <xmlproperty> rather than Perl XML::Simple
          Hide
          steve_rowe Steve Rowe added a comment -

          I'll leave the issue open until some Jenkins builds have succeeded.

          Show
          steve_rowe Steve Rowe added a comment - I'll leave the issue open until some Jenkins builds have succeeded.
          Hide
          arafalov Alexandre Rafalovitch added a comment -

          I am comparing solr.doap and the CHANGES.txt file in the distribution. A couple of points:

          • It calls release 1.2 in CHANGES as 1.2.0 in doap
          • CHANGES does not have 1.4.1, doap does
          • Neither seem to have 3.0, did it not happen?
          • doap uses 3.1, CHANGES uses 3.1.0 (for all 3.x), same with 4.x vs. 4.x.0
          • doap for solr seems to include 4 lucene entries (3.6.1, 3.6.2, 4.0-ALPHA, 4.0-BETA). These probably should be SOLR entries instead, as those are missing. But I don't know if dates match
          • CHANGES does not have 4.9.1

          Also, there is a README file in the dev-tools directory which lists what subdirectories contain. It was not updated to mention doap (or git from previous addition I guess).

          Show
          arafalov Alexandre Rafalovitch added a comment - I am comparing solr.doap and the CHANGES.txt file in the distribution. A couple of points: It calls release 1.2 in CHANGES as 1.2.0 in doap CHANGES does not have 1.4.1, doap does Neither seem to have 3.0, did it not happen? doap uses 3.1, CHANGES uses 3.1.0 (for all 3.x), same with 4.x vs. 4.x.0 doap for solr seems to include 4 lucene entries (3.6.1, 3.6.2, 4.0-ALPHA, 4.0-BETA). These probably should be SOLR entries instead, as those are missing. But I don't know if dates match CHANGES does not have 4.9.1 Also, there is a README file in the dev-tools directory which lists what subdirectories contain. It was not updated to mention doap (or git from previous addition I guess).
          Hide
          arafalov Alexandre Rafalovitch added a comment -

          For lucene.doap vs lucene's CHANGES.txt

          • doap has lucene-1.2.final, CHANGES has lucene 1.2 RC6 (both have RC5, though with different naming conventions)
          • doap has lucene-2.x, CHANGES has lucene 2.x.0 (same for later versions)
          • In CHANGES, 2.9.x and 3.0.(x-1) are collocated. Not sure if that will be an issue
          Show
          arafalov Alexandre Rafalovitch added a comment - For lucene.doap vs lucene's CHANGES.txt doap has lucene-1.2.final, CHANGES has lucene 1.2 RC6 (both have RC5, though with different naming conventions) doap has lucene-2.x, CHANGES has lucene 2.x.0 (same for later versions) In CHANGES, 2.9.x and 3.0.(x-1) are collocated. Not sure if that will be an issue
          Hide
          steve_rowe Steve Rowe added a comment - - edited

          edit: improved formatting

          Thanks for the review Alexandre Rafalovitch.

          I am comparing solr.doap and the CHANGES.txt file in the distribution. A couple of points:

          • It calls release 1.2 in CHANGES as 1.2.0 in doap
            [...]
          • doap uses 3.1, CHANGES uses 3.1.0 (for all 3.x), same with 4.x vs. 4.x.0

          I consider X.Y and X.Y.0 to be interchangeable aliases. These forms should be (and currently are) understood as equivalent for the purposes of linking information in the DOAP and CHANGES files. I don't think there's a problem here.

          • CHANGES does not have 1.4.1, doap does
            [...]
          • CHANGES does not have 4.9.1

          The entries for these releases apparently were never pulled from the release branch into the unstable & stable branches' CHANGES. I'll fix.

          • Neither seem to have 3.0, did it not happen?

          There never was a Solr 3.0 release.

          • doap for solr seems to include 4 lucene entries (3.6.1, 3.6.2, 4.0-ALPHA, 4.0-BETA). These probably should be SOLR entries instead, as those are missing. But I don't know if dates match

          Solr and Lucene releases from v3.1 have been synchronized in both number and date. This is a copy/paste-o of mine - I saw they were missing and pulled them from Lucene's DOAP files without changing the <name>. I'll fix.

          Also, there is a README file in the dev-tools directory which lists what subdirectories contain. It was not updated to mention doap (or git from previous addition I guess).

          I didn't see that file. I'll fix.

          For lucene.doap vs lucene's CHANGES.txt

          • doap has lucene-1.2.final, CHANGES has lucene 1.2 RC6 (both have RC5, though with different naming conventions)

          This is an intentional deviation. The CHANGES entry for 1.2 RC6 should have been changed to be 1.2 final after RC6 was blessed as the final 1.2 version, but it never was.

          • doap has lucene-2.x, CHANGES has lucene 2.x.0 (same for later versions)

          See my comments above about the same phenomenon in Solr's files. (To repeat, I don't think this is a problem.)

          • In CHANGES, 2.9.x and 3.0.(x-1) are collocated. Not sure if that will be an issue

          If you find any problems related to this, let me know.

          Show
          steve_rowe Steve Rowe added a comment - - edited edit : improved formatting Thanks for the review Alexandre Rafalovitch . I am comparing solr.doap and the CHANGES.txt file in the distribution. A couple of points: It calls release 1.2 in CHANGES as 1.2.0 in doap [...] doap uses 3.1, CHANGES uses 3.1.0 (for all 3.x), same with 4.x vs. 4.x.0 I consider X.Y and X.Y.0 to be interchangeable aliases. These forms should be (and currently are) understood as equivalent for the purposes of linking information in the DOAP and CHANGES files. I don't think there's a problem here. CHANGES does not have 1.4.1, doap does [...] CHANGES does not have 4.9.1 The entries for these releases apparently were never pulled from the release branch into the unstable & stable branches' CHANGES. I'll fix. Neither seem to have 3.0, did it not happen? There never was a Solr 3.0 release. doap for solr seems to include 4 lucene entries (3.6.1, 3.6.2, 4.0-ALPHA, 4.0-BETA). These probably should be SOLR entries instead, as those are missing. But I don't know if dates match Solr and Lucene releases from v3.1 have been synchronized in both number and date. This is a copy/paste-o of mine - I saw they were missing and pulled them from Lucene's DOAP files without changing the <name> . I'll fix. Also, there is a README file in the dev-tools directory which lists what subdirectories contain. It was not updated to mention doap (or git from previous addition I guess). I didn't see that file. I'll fix. For lucene.doap vs lucene's CHANGES.txt doap has lucene-1.2.final, CHANGES has lucene 1.2 RC6 (both have RC5, though with different naming conventions) This is an intentional deviation. The CHANGES entry for 1.2 RC6 should have been changed to be 1.2 final after RC6 was blessed as the final 1.2 version, but it never was. doap has lucene-2.x, CHANGES has lucene 2.x.0 (same for later versions) See my comments above about the same phenomenon in Solr's files. (To repeat, I don't think this is a problem.) In CHANGES, 2.9.x and 3.0.(x-1) are collocated. Not sure if that will be an issue If you find any problems related to this, let me know.
          Hide
          manokovacs Mano Kovacs added a comment -

          Sorry, Steve Rowe, I had a daughter delivered yesterday and it took my whole day. Thank you for taking the patch on, I see that there are lots of improvement since last Friday. Can I be any help with this?

          Show
          manokovacs Mano Kovacs added a comment - Sorry, Steve Rowe , I had a daughter delivered yesterday and it took my whole day. Thank you for taking the patch on, I see that there are lots of improvement since last Friday. Can I be any help with this?
          Hide
          steve_rowe Steve Rowe added a comment -

          Sorry, Steve Rowe, I had a daughter delivered yesterday and it took my whole day. Thank you for taking the patch on, I see that there are lots of improvement since last Friday. Can I be any help with this?

          No problem, thanks for all the work you did on it. I should be able to finish the rest of the work myself. Congratulations on your new family addition!

          Mano Kovacs, one request though: please stop using the "reply" link under specific JIRA comments. I noticed your comment because of the email sent to the dev list, but when I went to find it here I had to search for a while. Please just make a new comment, and if you feel you need to include context, quote previous comment(s). That way, future readers will be able to see comments properly time sequenced. And synchronized interlocutors won't have to dig to find your comments; I've seen more than one occasion where people assumed that the latest comments were at the bottom, and so they missed replies that were placed elsewhere on the page. I really really wish we could turn this feature off.

          Show
          steve_rowe Steve Rowe added a comment - Sorry, Steve Rowe , I had a daughter delivered yesterday and it took my whole day. Thank you for taking the patch on, I see that there are lots of improvement since last Friday. Can I be any help with this? No problem, thanks for all the work you did on it. I should be able to finish the rest of the work myself. Congratulations on your new family addition! Mano Kovacs , one request though: please stop using the "reply" link under specific JIRA comments. I noticed your comment because of the email sent to the dev list, but when I went to find it here I had to search for a while. Please just make a new comment, and if you feel you need to include context, quote previous comment(s). That way, future readers will be able to see comments properly time sequenced. And synchronized interlocutors won't have to dig to find your comments; I've seen more than one occasion where people assumed that the latest comments were at the bottom, and so they missed replies that were placed elsewhere on the page. I really really wish we could turn this feature off.
          Hide
          manokovacs Mano Kovacs added a comment -

          please stop using the "reply" link under specific JIRA comments

          OK, got it, makes sense!

          Thank you for helping these issues getting resolved!

          Show
          manokovacs Mano Kovacs added a comment - please stop using the "reply" link under specific JIRA comments OK, got it, makes sense! Thank you for helping these issues getting resolved!
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 73fb3f03d8cd554d0aa03e3c3cc2d24574edaaee in lucene-solr's branch refs/heads/branch_5_5 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=73fb3f0 ]

          LUCENE-7543: Update dev-tools/README.txt to include new dev-tools/ directories including doap/; add missing 1.4.1 and 4.9.1 release notes to Solr's CHANGES.txt; fix names of 3.6.1, 3.6.2, 4.0-ALPHA and 4.0-BETA releases in Solr's DOAP file to refer to solr instead of lucene.

          Show
          jira-bot ASF subversion and git services added a comment - Commit 73fb3f03d8cd554d0aa03e3c3cc2d24574edaaee in lucene-solr's branch refs/heads/branch_5_5 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=73fb3f0 ] LUCENE-7543 : Update dev-tools/README.txt to include new dev-tools/ directories including doap/; add missing 1.4.1 and 4.9.1 release notes to Solr's CHANGES.txt; fix names of 3.6.1, 3.6.2, 4.0-ALPHA and 4.0-BETA releases in Solr's DOAP file to refer to solr instead of lucene.
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit ee2198b7547a8e9476dc9fda4e3199fd0359ca89 in lucene-solr's branch refs/heads/branch_5x from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=ee2198b ]

          LUCENE-7543: Update dev-tools/README.txt to include new dev-tools/ directories including doap/; add missing 1.4.1 and 4.9.1 release notes to Solr's CHANGES.txt; fix names of 3.6.1, 3.6.2, 4.0-ALPHA and 4.0-BETA releases in Solr's DOAP file to refer to solr instead of lucene.

          Show
          jira-bot ASF subversion and git services added a comment - Commit ee2198b7547a8e9476dc9fda4e3199fd0359ca89 in lucene-solr's branch refs/heads/branch_5x from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=ee2198b ] LUCENE-7543 : Update dev-tools/README.txt to include new dev-tools/ directories including doap/; add missing 1.4.1 and 4.9.1 release notes to Solr's CHANGES.txt; fix names of 3.6.1, 3.6.2, 4.0-ALPHA and 4.0-BETA releases in Solr's DOAP file to refer to solr instead of lucene.
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 2b3977c5573d829827cbf9162f337e3d7fe8bb88 in lucene-solr's branch refs/heads/branch_6_0 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=2b3977c ]

          LUCENE-7543: Update dev-tools/README.txt to include new dev-tools/ directories including doap/; add missing 1.4.1 and 4.9.1 release notes to Solr's CHANGES.txt; fix names of 3.6.1, 3.6.2, 4.0-ALPHA and 4.0-BETA releases in Solr's DOAP file to refer to solr instead of lucene.

          Show
          jira-bot ASF subversion and git services added a comment - Commit 2b3977c5573d829827cbf9162f337e3d7fe8bb88 in lucene-solr's branch refs/heads/branch_6_0 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=2b3977c ] LUCENE-7543 : Update dev-tools/README.txt to include new dev-tools/ directories including doap/; add missing 1.4.1 and 4.9.1 release notes to Solr's CHANGES.txt; fix names of 3.6.1, 3.6.2, 4.0-ALPHA and 4.0-BETA releases in Solr's DOAP file to refer to solr instead of lucene.
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 0f42a3993e6d430421cc0594412c7993f2b6dd30 in lucene-solr's branch refs/heads/branch_6_1 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=0f42a39 ]

          LUCENE-7543: Update dev-tools/README.txt to include new dev-tools/ directories including doap/; add missing 1.4.1 and 4.9.1 release notes to Solr's CHANGES.txt; fix names of 3.6.1, 3.6.2, 4.0-ALPHA and 4.0-BETA releases in Solr's DOAP file to refer to solr instead of lucene.

          Show
          jira-bot ASF subversion and git services added a comment - Commit 0f42a3993e6d430421cc0594412c7993f2b6dd30 in lucene-solr's branch refs/heads/branch_6_1 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=0f42a39 ] LUCENE-7543 : Update dev-tools/README.txt to include new dev-tools/ directories including doap/; add missing 1.4.1 and 4.9.1 release notes to Solr's CHANGES.txt; fix names of 3.6.1, 3.6.2, 4.0-ALPHA and 4.0-BETA releases in Solr's DOAP file to refer to solr instead of lucene.
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit c3dad251f49ca10378ad70759bfb65224cf27fec in lucene-solr's branch refs/heads/branch_6_2 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=c3dad25 ]

          LUCENE-7543: Update dev-tools/README.txt to include new dev-tools/ directories including doap/; add missing 1.4.1 and 4.9.1 release notes to Solr's CHANGES.txt; fix names of 3.6.1, 3.6.2, 4.0-ALPHA and 4.0-BETA releases in Solr's DOAP file to refer to solr instead of lucene.

          Show
          jira-bot ASF subversion and git services added a comment - Commit c3dad251f49ca10378ad70759bfb65224cf27fec in lucene-solr's branch refs/heads/branch_6_2 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=c3dad25 ] LUCENE-7543 : Update dev-tools/README.txt to include new dev-tools/ directories including doap/; add missing 1.4.1 and 4.9.1 release notes to Solr's CHANGES.txt; fix names of 3.6.1, 3.6.2, 4.0-ALPHA and 4.0-BETA releases in Solr's DOAP file to refer to solr instead of lucene.
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit d39550245fdf647caf5322b1b8e16a11d14660da in lucene-solr's branch refs/heads/branch_6_3 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=d395502 ]

          LUCENE-7543: Update dev-tools/README.txt to include new dev-tools/ directories including doap/; add missing 1.4.1 and 4.9.1 release notes to Solr's CHANGES.txt; fix names of 3.6.1, 3.6.2, 4.0-ALPHA and 4.0-BETA releases in Solr's DOAP file to refer to solr instead of lucene.

          Show
          jira-bot ASF subversion and git services added a comment - Commit d39550245fdf647caf5322b1b8e16a11d14660da in lucene-solr's branch refs/heads/branch_6_3 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=d395502 ] LUCENE-7543 : Update dev-tools/README.txt to include new dev-tools/ directories including doap/; add missing 1.4.1 and 4.9.1 release notes to Solr's CHANGES.txt; fix names of 3.6.1, 3.6.2, 4.0-ALPHA and 4.0-BETA releases in Solr's DOAP file to refer to solr instead of lucene.
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 615570c347a772fe23588fdbd11e0be935e97106 in lucene-solr's branch refs/heads/branch_6x from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=615570c ]

          LUCENE-7543: Update dev-tools/README.txt to include new dev-tools/ directories including doap/; add missing 1.4.1 and 4.9.1 release notes to Solr's CHANGES.txt; fix names of 3.6.1, 3.6.2, 4.0-ALPHA and 4.0-BETA releases in Solr's DOAP file to refer to solr instead of lucene.

          Show
          jira-bot ASF subversion and git services added a comment - Commit 615570c347a772fe23588fdbd11e0be935e97106 in lucene-solr's branch refs/heads/branch_6x from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=615570c ] LUCENE-7543 : Update dev-tools/README.txt to include new dev-tools/ directories including doap/; add missing 1.4.1 and 4.9.1 release notes to Solr's CHANGES.txt; fix names of 3.6.1, 3.6.2, 4.0-ALPHA and 4.0-BETA releases in Solr's DOAP file to refer to solr instead of lucene.
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 6a83f0fa3ae880be497d48af702f293f38203b2d in lucene-solr's branch refs/heads/master from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=6a83f0f ]

          LUCENE-7543: Update dev-tools/README.txt to include new dev-tools/ directories including doap/; add missing 1.4.1 and 4.9.1 release notes to Solr's CHANGES.txt; fix names of 3.6.1, 3.6.2, 4.0-ALPHA and 4.0-BETA releases in Solr's DOAP file to refer to solr instead of lucene.

          Show
          jira-bot ASF subversion and git services added a comment - Commit 6a83f0fa3ae880be497d48af702f293f38203b2d in lucene-solr's branch refs/heads/master from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=6a83f0f ] LUCENE-7543 : Update dev-tools/README.txt to include new dev-tools/ directories including doap/; add missing 1.4.1 and 4.9.1 release notes to Solr's CHANGES.txt; fix names of 3.6.1, 3.6.2, 4.0-ALPHA and 4.0-BETA releases in Solr's DOAP file to refer to solr instead of lucene.
          Hide
          arafalov Alexandre Rafalovitch added a comment -

          I consider X.Y and X.Y.0 to be interchangeable aliases. These forms should be (and currently are) understood as equivalent for the purposes of linking information in the DOAP and CHANGES files. I don't think there's a problem here.

          It is not a small issue, but it would be an issue for everybody actually trying to parse the doap file. Could we at least make it consistent internally (at the moment, it is solr-4.3 but solr-4.9.0). I still think x.y.z is better, otherwise, we should also have 5, not 5.0 for consistency.

          I know it is a nitpicking, but I write the parsing tools and these things are disproportionally annoying and confusing. I am happy to do the change myself to normalize to x.y.z, if you don't mind.

          Show
          arafalov Alexandre Rafalovitch added a comment - I consider X.Y and X.Y.0 to be interchangeable aliases. These forms should be (and currently are) understood as equivalent for the purposes of linking information in the DOAP and CHANGES files. I don't think there's a problem here. It is not a small issue, but it would be an issue for everybody actually trying to parse the doap file. Could we at least make it consistent internally (at the moment, it is solr-4.3 but solr-4.9.0). I still think x.y.z is better, otherwise, we should also have 5, not 5.0 for consistency. I know it is a nitpicking, but I write the parsing tools and these things are disproportionally annoying and confusing. I am happy to do the change myself to normalize to x.y.z, if you don't mind.
          Hide
          steve_rowe Steve Rowe added a comment -

          It is not a small issue, but it would be an issue for everybody actually trying to parse the doap file. Could we at least make it consistent internally (at the moment, it is solr-4.3 but solr-4.9.0). I still think x.y.z is better, otherwise, we should also have 5, not 5.0 for consistency.
          I know it is a nitpicking, but I write the parsing tools and these things are disproportionally annoying and confusing. I am happy to do the change myself to normalize to x.y.z, if you don't mind.

          The problem is that people think of them as interchangeable, regardless of programmatic "inconsistency", and though you may normalize them up through today, a future release manager will generate more "inconsistencies". Better to teach the programs to understand the humans than vice versa. Do you really want to spend time arguing with people in the future about how they have to have the right number of trailing zeros in all the places they record release numbers? I know I don't.

          Show
          steve_rowe Steve Rowe added a comment - It is not a small issue, but it would be an issue for everybody actually trying to parse the doap file. Could we at least make it consistent internally (at the moment, it is solr-4.3 but solr-4.9.0). I still think x.y.z is better, otherwise, we should also have 5, not 5.0 for consistency. I know it is a nitpicking, but I write the parsing tools and these things are disproportionally annoying and confusing. I am happy to do the change myself to normalize to x.y.z, if you don't mind. The problem is that people think of them as interchangeable, regardless of programmatic "inconsistency", and though you may normalize them up through today, a future release manager will generate more "inconsistencies". Better to teach the programs to understand the humans than vice versa. Do you really want to spend time arguing with people in the future about how they have to have the right number of trailing zeros in all the places they record release numbers? I know I don't.
          Hide
          arafalov Alexandre Rafalovitch added a comment -

          Do you really want to spend time arguing with people in the future about how they have to have the right number of trailing zeros in all the places they record release numbers?

          I don't (though it seems I am doing it right now), but I think having a consistent start and perhaps a note in the comment about using full x.y.z format for tools' sake will go a long way there. And if our own internal tool relies on x.y.z (that's the goal, right?) and breaks on build for the other format, then people will adjust their commits.

          But, like I said, I am happy to do the cleanup and - if I am proven wrong later - I will not complain.

          Show
          arafalov Alexandre Rafalovitch added a comment - Do you really want to spend time arguing with people in the future about how they have to have the right number of trailing zeros in all the places they record release numbers? I don't (though it seems I am doing it right now), but I think having a consistent start and perhaps a note in the comment about using full x.y.z format for tools' sake will go a long way there. And if our own internal tool relies on x.y.z (that's the goal, right?) and breaks on build for the other format, then people will adjust their commits. But, like I said, I am happy to do the cleanup and - if I am proven wrong later - I will not complain.
          Hide
          steve_rowe Steve Rowe added a comment -

          But, like I said, I am happy to do the cleanup and - if I am proven wrong later - I will not complain.

          In my opinion, version parsing/comparison code that consumes human input and doesn't do this work is broken. I think what you want to do is a step backward. If you put this in place, you will be policing how release numbers are represented in a fraction of places where they're recorded. The website (for example) has no such validation.

          Show
          steve_rowe Steve Rowe added a comment - But, like I said, I am happy to do the cleanup and - if I am proven wrong later - I will not complain. In my opinion, version parsing/comparison code that consumes human input and doesn't do this work is broken. I think what you want to do is a step backward. If you put this in place, you will be policing how release numbers are represented in a fraction of places where they're recorded. The website (for example) has no such validation.
          Hide
          arafalov Alexandre Rafalovitch added a comment -

          Ok. I am reading this as -1 and will let you get on with it. If there are issues later, we can revisit this with more specific concerns.

          Show
          arafalov Alexandre Rafalovitch added a comment - Ok. I am reading this as -1 and will let you get on with it. If there are issues later, we can revisit this with more specific concerns.
          Hide
          steve_rowe Steve Rowe added a comment -

          Ok. I am reading this as -1 and will let you get on with it. If there are issues later, we can revisit this with more specific concerns.

          I tried to write -0 but I couldn't bring myself to do it, since I really think it's the wrong thing to do, and I had hoped to convince you of that.

          Show
          steve_rowe Steve Rowe added a comment - Ok. I am reading this as -1 and will let you get on with it. If there are issues later, we can revisit this with more specific concerns. I tried to write -0 but I couldn't bring myself to do it, since I really think it's the wrong thing to do, and I had hoped to convince you of that.
          Hide
          arafalov Alexandre Rafalovitch added a comment -

          I tried to write -0 but I couldn't bring myself to do it, since I really think it's the wrong thing to do, and I had hoped to convince you of that.

          Sorry, I am absolutely not convinced. My understanding is that doap file is for tools. So, deliberately allowing non-significant variability to force each tool that wants to parse that file do more work makes zero sense to me. And may cause for less of such tools being created.

          Other places that are not tools oriented are and will continue to be inconsistent. That to me is an argument but of a little weight in this situation. I would have thought that it would be easier to just start consistent and then worry about what may be.

          But perhaps I am missing the bigger picture you are seeing. So, let's not bike-shed and just go ahead with what you have already.

          Show
          arafalov Alexandre Rafalovitch added a comment - I tried to write -0 but I couldn't bring myself to do it, since I really think it's the wrong thing to do, and I had hoped to convince you of that. Sorry, I am absolutely not convinced. My understanding is that doap file is for tools. So, deliberately allowing non-significant variability to force each tool that wants to parse that file do more work makes zero sense to me. And may cause for less of such tools being created. Other places that are not tools oriented are and will continue to be inconsistent. That to me is an argument but of a little weight in this situation. I would have thought that it would be easier to just start consistent and then worry about what may be. But perhaps I am missing the bigger picture you are seeing. So, let's not bike-shed and just go ahead with what you have already.
          Hide
          steve_rowe Steve Rowe added a comment -

          My understanding is that doap file is for tools.

          I agree, it's not for human consumption. But at this point it's created by people, not tools.

          I would +0 what you propose if you wrote a script to update the doap files. This script would accept release numbers in formats X(-suffix), X.Y(-suffix) and X.Y.Z(-suffix) and normalized them to the X.Y.Z(-suffix) format. (Your other suggestions about failing the build and a comment in the doap files about release number format would still be necessary to handle the case where people don't use the script.)

          Show
          steve_rowe Steve Rowe added a comment - My understanding is that doap file is for tools. I agree, it's not for human consumption. But at this point it's created by people, not tools. I would +0 what you propose if you wrote a script to update the doap files. This script would accept release numbers in formats X(-suffix) , X.Y(-suffix) and X.Y.Z(-suffix) and normalized them to the X.Y.Z(-suffix) format. (Your other suggestions about failing the build and a comment in the doap files about release number format would still be necessary to handle the case where people don't use the script.)
          Hide
          arafalov Alexandre Rafalovitch added a comment -

          Sorry. You can stay at -1 I do not see this as a rational trade-off of effort.

          I assume, the doap file will be updated by a release-manager already following a bunch of checklist items. Updated approximately once every 6 week!!! Having one more that says "and remember to use x.y.z" version would have been sufficient. The build failure during generation of the changes.html would ensure the step is not skipped accidentally.

          I appreciate your attempts to find a common ground. I just think we spent too much time disagreeing. Let's just go ahead and keep this for historical reference for when we actually have tools consuming this format and we can see what makes sense.

          Show
          arafalov Alexandre Rafalovitch added a comment - Sorry. You can stay at -1 I do not see this as a rational trade-off of effort. I assume, the doap file will be updated by a release-manager already following a bunch of checklist items. Updated approximately once every 6 week!!! Having one more that says "and remember to use x.y.z" version would have been sufficient. The build failure during generation of the changes.html would ensure the step is not skipped accidentally. I appreciate your attempts to find a common ground. I just think we spent too much time disagreeing. Let's just go ahead and keep this for historical reference for when we actually have tools consuming this format and we can see what makes sense.
          Hide
          steve_rowe Steve Rowe added a comment -

          I guess the essense of our disagreement is whether additional burden on the release manager is acceptable. You may not know this, but that job was once complicated enough that people wouldn't volunteer to do it. Some progress has been made in automating it, but there's lots left to do. Without tooling support, "one more little thing" will get a -1 from me, regardless of its infrequency. (BTW minor releases, where the issue happens, have occurred once every 10 weeks on average since 4.0.)

          Show
          steve_rowe Steve Rowe added a comment - I guess the essense of our disagreement is whether additional burden on the release manager is acceptable. You may not know this, but that job was once complicated enough that people wouldn't volunteer to do it. Some progress has been made in automating it, but there's lots left to do. Without tooling support, "one more little thing" will get a -1 from me, regardless of its infrequency. (BTW minor releases, where the issue happens, have occurred once every 10 weeks on average since 4.0.)
          Hide
          steve_rowe Steve Rowe added a comment - - edited

          From Alexandre Rafalovitch on the dev list:

          I just noticed that in the HTML version of the shipped release notes,
          the "LUCENE_CHANGES.txt" is no longer hyperlinked to the online
          version of the Lucene changes document.

          In the 6.3 release and before, it was hyperlinked.

          The issue: Changes committed on this issue downcased the product name “SOLR”->”solr” passed by solr/build.xml into changes2html.pl, which causes the conditional code to do the LUCENE_CHANGES.txt hyperlinking to never get invoked because the product name is misspelled… Not sure why the product name got downcased?

          Show
          steve_rowe Steve Rowe added a comment - - edited From Alexandre Rafalovitch on the dev list: I just noticed that in the HTML version of the shipped release notes, the "LUCENE_CHANGES.txt" is no longer hyperlinked to the online version of the Lucene changes document. In the 6.3 release and before, it was hyperlinked. The issue: Changes committed on this issue downcased the product name “SOLR”->”solr” passed by solr/build.xml into changes2html.pl , which causes the conditional code to do the LUCENE_CHANGES.txt hyperlinking to never get invoked because the product name is misspelled… Not sure why the product name got downcased?
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit ddb008d960a8f85999f085b0ed96d78c41252339 in lucene-solr's branch refs/heads/branch_5_5 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=ddb008d ]

          LUCENE-7543: Treat product name passed into changes2html.pl case-insensitively, and validate that the product name is either 'lucene' or 'solr'

          Show
          jira-bot ASF subversion and git services added a comment - Commit ddb008d960a8f85999f085b0ed96d78c41252339 in lucene-solr's branch refs/heads/branch_5_5 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=ddb008d ] LUCENE-7543 : Treat product name passed into changes2html.pl case-insensitively, and validate that the product name is either 'lucene' or 'solr'
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 5c5c8b5c5daf85c76173fa7ebeedeb6994c1b67e in lucene-solr's branch refs/heads/branch_5x from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=5c5c8b5 ]

          LUCENE-7543: Treat product name passed into changes2html.pl case-insensitively, and validate that the product name is either 'lucene' or 'solr'

          Show
          jira-bot ASF subversion and git services added a comment - Commit 5c5c8b5c5daf85c76173fa7ebeedeb6994c1b67e in lucene-solr's branch refs/heads/branch_5x from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=5c5c8b5 ] LUCENE-7543 : Treat product name passed into changes2html.pl case-insensitively, and validate that the product name is either 'lucene' or 'solr'
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 8ed9528b8e3288f02882eef570b20cf420d01b3c in lucene-solr's branch refs/heads/branch_6_0 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=8ed9528 ]

          LUCENE-7543: Treat product name passed into changes2html.pl case-insensitively, and validate that the product name is either 'lucene' or 'solr'

          Show
          jira-bot ASF subversion and git services added a comment - Commit 8ed9528b8e3288f02882eef570b20cf420d01b3c in lucene-solr's branch refs/heads/branch_6_0 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=8ed9528 ] LUCENE-7543 : Treat product name passed into changes2html.pl case-insensitively, and validate that the product name is either 'lucene' or 'solr'
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 30466d57788a44b7aa88f6bebd10ade2f3cd58e8 in lucene-solr's branch refs/heads/branch_6_1 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=30466d5 ]

          LUCENE-7543: Treat product name passed into changes2html.pl case-insensitively, and validate that the product name is either 'lucene' or 'solr'

          Show
          jira-bot ASF subversion and git services added a comment - Commit 30466d57788a44b7aa88f6bebd10ade2f3cd58e8 in lucene-solr's branch refs/heads/branch_6_1 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=30466d5 ] LUCENE-7543 : Treat product name passed into changes2html.pl case-insensitively, and validate that the product name is either 'lucene' or 'solr'
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit d908647eeb57cbbf7b2f36e17eead7edbc062a09 in lucene-solr's branch refs/heads/branch_6_2 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=d908647 ]

          LUCENE-7543: Treat product name passed into changes2html.pl case-insensitively, and validate that the product name is either 'lucene' or 'solr'

          Show
          jira-bot ASF subversion and git services added a comment - Commit d908647eeb57cbbf7b2f36e17eead7edbc062a09 in lucene-solr's branch refs/heads/branch_6_2 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=d908647 ] LUCENE-7543 : Treat product name passed into changes2html.pl case-insensitively, and validate that the product name is either 'lucene' or 'solr'
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 6fa26fe8553b7b65dee96da741f2c1adf4cb6216 in lucene-solr's branch refs/heads/branch_6_3 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=6fa26fe ]

          LUCENE-7543: Treat product name passed into changes2html.pl case-insensitively, and validate that the product name is either 'lucene' or 'solr'

          Show
          jira-bot ASF subversion and git services added a comment - Commit 6fa26fe8553b7b65dee96da741f2c1adf4cb6216 in lucene-solr's branch refs/heads/branch_6_3 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=6fa26fe ] LUCENE-7543 : Treat product name passed into changes2html.pl case-insensitively, and validate that the product name is either 'lucene' or 'solr'
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 14812fa1bcbb7fcf1d1e289f0633fa8ffc9f7dc6 in lucene-solr's branch refs/heads/branch_6_4 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=14812fa ]

          LUCENE-7543: Treat product name passed into changes2html.pl case-insensitively, and validate that the product name is either 'lucene' or 'solr'

          Show
          jira-bot ASF subversion and git services added a comment - Commit 14812fa1bcbb7fcf1d1e289f0633fa8ffc9f7dc6 in lucene-solr's branch refs/heads/branch_6_4 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=14812fa ] LUCENE-7543 : Treat product name passed into changes2html.pl case-insensitively, and validate that the product name is either 'lucene' or 'solr'
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 34af139b4d9a10999b76e78a14d27e39f7d68405 in lucene-solr's branch refs/heads/branch_6x from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=34af139 ]

          LUCENE-7543: Treat product name passed into changes2html.pl case-insensitively, and validate that the product name is either 'lucene' or 'solr'

          Show
          jira-bot ASF subversion and git services added a comment - Commit 34af139b4d9a10999b76e78a14d27e39f7d68405 in lucene-solr's branch refs/heads/branch_6x from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=34af139 ] LUCENE-7543 : Treat product name passed into changes2html.pl case-insensitively, and validate that the product name is either 'lucene' or 'solr'
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 1b80691f28b045c7a8d9552f3c63f7bafdf52d48 in lucene-solr's branch refs/heads/master from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=1b80691 ]

          LUCENE-7543: Treat product name passed into changes2html.pl case-insensitively, and validate that the product name is either 'lucene' or 'solr'

          Show
          jira-bot ASF subversion and git services added a comment - Commit 1b80691f28b045c7a8d9552f3c63f7bafdf52d48 in lucene-solr's branch refs/heads/master from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=1b80691 ] LUCENE-7543 : Treat product name passed into changes2html.pl case-insensitively, and validate that the product name is either 'lucene' or 'solr'
          Hide
          steve_rowe Steve Rowe added a comment -

          I committed a fix (upcase product name in changes2html.pl, and then make sure it's either "LUCENE" or "SOLR").

          Not sure why the product name got downcased?

          This is to be able to match the DOAP file names, which include lowercase product names.

          I'm resolving this issue now.

          Show
          steve_rowe Steve Rowe added a comment - I committed a fix (upcase product name in changes2html.pl , and then make sure it's either "LUCENE" or "SOLR"). Not sure why the product name got downcased? This is to be able to match the DOAP file names, which include lowercase product names. I'm resolving this issue now.
          Hide
          jira-bot ASF subversion and git services added a comment -

          Commit 1b80691f28b045c7a8d9552f3c63f7bafdf52d48 in lucene-solr's branch refs/heads/apiv2 from Steve Rowe
          [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=1b80691 ]

          LUCENE-7543: Treat product name passed into changes2html.pl case-insensitively, and validate that the product name is either 'lucene' or 'solr'

          Show
          jira-bot ASF subversion and git services added a comment - Commit 1b80691f28b045c7a8d9552f3c63f7bafdf52d48 in lucene-solr's branch refs/heads/apiv2 from Steve Rowe [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=1b80691 ] LUCENE-7543 : Treat product name passed into changes2html.pl case-insensitively, and validate that the product name is either 'lucene' or 'solr'
          Hide
          manokovacs Mano Kovacs added a comment -

          Steve Rowe, as you also wrote, I made it lowercase to match the doap files. I was trying to verify if it was used anywhere else, but I missed the links. Sorry for the trouble and thank you for the fix.

          Show
          manokovacs Mano Kovacs added a comment - Steve Rowe , as you also wrote, I made it lowercase to match the doap files. I was trying to verify if it was used anywhere else, but I missed the links. Sorry for the trouble and thank you for the fix.
          Hide
          steve_rowe Steve Rowe added a comment -

          No problem Mano, thanks again for doing the bulk of the work on this issue.

          Show
          steve_rowe Steve Rowe added a comment - No problem Mano, thanks again for doing the bulk of the work on this issue.

            People

            • Assignee:
              steve_rowe Steve Rowe
              Reporter:
              steve_rowe Steve Rowe
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development