Loading ...
Sorry, an error occurred while loading the content.

Re: VIM v7 and v7.3.46: End of Life and End of Support Dates needed

Expand Messages
  • Ben Fritz
    ... Some open-source projects (like Python, for example) have a cutting-edge version but also release security updates, etc. for older versions. So you can
    Message 1 of 6 , Nov 29, 2012
    • 0 Attachment
      On Wednesday, November 28, 2012 10:11:52 PM UTC-6, Gary Johnson wrote:
      > On 2012-11-28, rams wrote:
      >
      > > Hello,
      >
      > >
      >
      > > I am looking for End of Life and End of Support dates for:
      >
      > > VIM 7
      >
      > > VIM 7.3.46
      >
      > >
      >
      > > Can you please share the info for this?
      >
      >
      >
      > I am not an official spokesman for Vim. The following is just my
      >
      > perspective.
      >
      >
      >
      > I don't know what those terms mean in the context of an open source
      >
      > project such as Vim. What do those terms mean to you?
      >

      Some open-source projects (like Python, for example) have a cutting-edge version but also release security updates, etc. for older versions. So you can still download Python 2.7 for example even though they're pushing Python 3.

      It would be like having a Vim 7.2 branch that we would back-port crash fixes and data loss issues and the like from the default branch (7.3). But Vim doesn't work this way, and as far as I know, it hasn't ever worked this way. With Vim it seems there is only ever one active line of development.

      --
      You received this message from the "vim_use" maillist.
      Do not top-post! Type your reply below the text you are replying to.
      For more information, visit http://www.vim.org/maillist.php
    • Tony Mechelynck
      ... From time to time, but not at this precise moment, development has happened on some future code branch of Vim, which was then labeled as either alpha
      Message 2 of 6 , Nov 29, 2012
      • 0 Attachment
        On 29/11/12 16:55, Ben Fritz wrote:
        > On Wednesday, November 28, 2012 10:11:52 PM UTC-6, Gary Johnson wrote:
        >> On 2012-11-28, rams wrote:
        >>
        >>> Hello,
        >>
        >>>
        >>
        >>> I am looking for End of Life and End of Support dates for:
        >>
        >>> VIM 7
        >>
        >>> VIM 7.3.46
        >>
        >>>
        >>
        >>> Can you please share the info for this?
        >>
        >>
        >>
        >> I am not an official spokesman for Vim. The following is just my
        >>
        >> perspective.
        >>
        >>
        >>
        >> I don't know what those terms mean in the context of an open source
        >>
        >> project such as Vim. What do those terms mean to you?
        >>
        >
        > Some open-source projects (like Python, for example) have a cutting-edge version but also release security updates, etc. for older versions. So you can still download Python 2.7 for example even though they're pushing Python 3.
        >
        > It would be like having a Vim 7.2 branch that we would back-port crash fixes and data loss issues and the like from the default branch (7.3). But Vim doesn't work this way, and as far as I know, it hasn't ever worked this way. With Vim it seems there is only ever one active line of development.
        >

        From time to time, but not at this precise moment, development has
        happened on some "future code branch" of Vim, which was then labeled as
        either "alpha" or "beta". Important security-and-stability bug fixes
        have been, at such times, backported from the "future" release to the
        "current stable" release. Nowadays, however, the only code branch
        visibly under development is the current stable branch, namely Vim
        7.3.x, and all previous branches are at EOL AFAICT. This means that, as
        Gary said, currently each new patchlevel obsoletes all previous ones:
        the current version is 7.3.744 released some three hours ago as I'm
        typing this message. Like Ben said, any bug found in some earlier
        release will still be investigated and, if some already published
        patchlevel did not fix it, a fix will be attempted, and, if found and
        accepted by Bram, published as a new patchlevel, etc.

        Someday an alpha or beta pre-release of 7.4 or 8.0 will probably appear,
        and then we will again be in the other, "transition" case described at
        the beginning of the previous paragraph, until a new "stable" 7.4 or 8.0
        release obsoletes the 7.3.x branch.

        Best regards,
        Tony.
        --
        The penalty for laughing in a courtroom is six months in jail; if it
        were not for this penalty, the jury would never hear the evidence.
        -- H. L. Mencken

        --
        You received this message from the "vim_use" maillist.
        Do not top-post! Type your reply below the text you are replying to.
        For more information, visit http://www.vim.org/maillist.php
      • Tony Mechelynck
        ... -- The meta-Turing test counts a thing as intelligent if it seeks to devise and apply Turing tests to objects of its own creation. -- Lew Mammel, Jr. --
        Message 3 of 6 , Nov 29, 2012
        • 0 Attachment
          On 29/11/12 23:14, Tony Mechelynck wrote:
          > On 29/11/12 16:55, Ben Fritz wrote:
          >> On Wednesday, November 28, 2012 10:11:52 PM UTC-6, Gary Johnson wrote:
          >>> On 2012-11-28, rams wrote:
          >>>
          >>>> Hello,
          >>>
          >>>>
          >>>
          >>>> I am looking for End of Life and End of Support dates for:
          >>>
          >>>> VIM 7
          >>>
          >>>> VIM 7.3.46
          >>>
          >>>>
          >>>
          >>>> Can you please share the info for this?
          >>>
          >>>
          >>>
          >>> I am not an official spokesman for Vim. The following is just my
          >>>
          >>> perspective.
          >>>
          >>>
          >>>
          >>> I don't know what those terms mean in the context of an open source
          >>>
          >>> project such as Vim. What do those terms mean to you?
          >>>
          >>
          >> Some open-source projects (like Python, for example) have a
          >> cutting-edge version but also release security updates, etc. for older
          >> versions. So you can still download Python 2.7 for example even though
          >> they're pushing Python 3.
          >>
          >> It would be like having a Vim 7.2 branch that we would back-port crash
          >> fixes and data loss issues and the like from the default branch (7.3).
          >> But Vim doesn't work this way, and as far as I know, it hasn't ever
          >> worked this way. With Vim it seems there is only ever one active line
          >> of development.
          >>
          >
          > From time to time, but not at this precise moment, development has
          > happened on some "future code branch" of Vim, which was then labeled as
          > either "alpha" or "beta". Important security-and-stability bug fixes
          > have been, at such times, backported from the "future" release to the
          > "current stable" release. Nowadays, however, the only code branch
          > visibly under development is the current stable branch, namely Vim
          > 7.3.x, and all previous branches are at EOL AFAICT. This means that, as
          > Gary said, currently each new patchlevel obsoletes all previous ones:
          > the current version is 7.3.744 released some three hours ago as I'm
          > typing this message. Like Ben said, any bug found in some earlier
          ----------------------------^^^ sorry, "like Gary said".
          > release will still be investigated and, if some already published
          > patchlevel did not fix it, a fix will be attempted, and, if found and
          > accepted by Bram, published as a new patchlevel, etc.
          >
          > Someday an alpha or beta pre-release of 7.4 or 8.0 will probably appear,
          > and then we will again be in the other, "transition" case described at
          > the beginning of the previous paragraph, until a new "stable" 7.4 or 8.0
          > release obsoletes the 7.3.x branch.
          >
          > Best regards,
          > Tony.
          --
          The meta-Turing test counts a thing as intelligent if it seeks to
          devise and apply Turing tests to objects of its own creation.
          -- Lew Mammel, Jr.

          --
          You received this message from the "vim_use" maillist.
          Do not top-post! Type your reply below the text you are replying to.
          For more information, visit http://www.vim.org/maillist.php
        Your message has been successfully submitted and would be delivered to recipients shortly.