Version 15.54 and Version 16.00

  • Jeffrey T Best

    Jeffrey T Best - 2003-03-22

    Once we have pulled all of the v15.53 source files into the CVS and applied and tested a few small bug-fixes that have accumulated since then, I think we should release the result as v15.54.

    At the same time, I thin kwe need a list of features and the responsible developers, for what is going to go into v16.00.

    Any thoughts?

    • Jonathan L Cunningham

      We seem to have moved on a bit in the last
      10 months - you are currently proposing a
      platform specific suffix letter to the version
      number (w, etc.) on the (non-SF) mailing

      But I agree a 15.54 version would be a good
      psychological boost.

    • Jeffrey T Best

      Jeffrey T Best - 2004-01-20

      Actually, it was Aaron who was proposing a platform suffix and I was merely trying to politely equivocate.

      I think that we will have an internal version number, e.g. 15.53.04, indicating the changes to the base level and we'll try to keep the base level matching the other code-bases. When Aaron moves to 16.00, we will absorb those changes and do the same.

      If we succeed in merging the different versions, then a full export from the CVS will be the current base version, and each platform-specific subset will be its own internal version, possibly tagged with an alpha suffix.


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks