Texen
  1. Texen
  2. TEXEN-8

Broken links on Texen site for 1.0 and devel versions

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Activity

      Hide
      Will Glass-Husain added a comment -

      Ok, ok. You're right. I edited the page by hand to have the right. Since it's a tagged release, it's unlikely we'll rebuild that portion of the site. If we do this fix will be overwritten. Hopefully we'll have an updated release of Texen by then and this issue will be moot.

      Commenting more for the Velocity dev community below...

      This may be academic, but still pondering what the right process is to track changes to the docs. An unchanging "tag" for the release means that the docs can never be rebuilt on the site. Maybe we should be deploying from a branch (e.g. the VELOCITY_1.5 branch) so that doc fixes are source controlled?

      Henning's suggested an alternative approach in the past, which is to pull the docs out of the release cycle entirely. I'm beginning to see the point, though I worry about losing synchronicity with feature changes.

      WILL

      Show
      Will Glass-Husain added a comment - Ok, ok. You're right. I edited the page by hand to have the right. Since it's a tagged release, it's unlikely we'll rebuild that portion of the site. If we do this fix will be overwritten. Hopefully we'll have an updated release of Texen by then and this issue will be moot. Commenting more for the Velocity dev community below... This may be academic, but still pondering what the right process is to track changes to the docs. An unchanging "tag" for the release means that the docs can never be rebuilt on the site. Maybe we should be deploying from a branch (e.g. the VELOCITY_1.5 branch) so that doc fixes are source controlled? Henning's suggested an alternative approach in the past, which is to pull the docs out of the release cycle entirely. I'm beginning to see the point, though I worry about losing synchronicity with feature changes. WILL
      Hide
      Sebb added a comment -

      I can understand that you may not want to rebuild the site for 1.0, but surely the page can be editted so it works?

      Show
      Sebb added a comment - I can understand that you may not want to rebuild the site for 1.0, but surely the page can be editted so it works?
      Hide
      Will Glass-Husain added a comment -

      The problem was a mismatch between the maven build (for the website) and the ant build (when downloading the distribution).

      Fixed the "trunk" and "1.0" branch. The website will update in the next 12 hours on the "devel" link. The "1.0" link won't update till we do a new release.

      Now the links work both when downloading the distribution and on the web site (at least for the "devel" tree).

      Show
      Will Glass-Husain added a comment - The problem was a mismatch between the maven build (for the website) and the ant build (when downloading the distribution). Fixed the "trunk" and "1.0" branch. The website will update in the next 12 hours on the "devel" link. The "1.0" link won't update till we do a new release. Now the links work both when downloading the distribution and on the web site (at least for the "devel" tree).

        People

        • Assignee:
          Unassigned
          Reporter:
          Sebb
        • Votes:
          0 Vote for this issue
          Watchers:
          0 Start watching this issue

          Dates

          • Created:
            Updated:
            Resolved:

            Development