Changes between Initial Version and Version 1 of Ticket #63141


Ignore:
Timestamp:
Jan 28, 2022, 5:25:38 AM (2 years ago)
Author:
JDLH (Jim DeLaHunt)
Comment:

Freeciv 2.6.6 was released by upstream on 2021-12-10. Release notes: https://freeciv.fandom.com/wiki/NEWS-2.6.6 . It contains upstream fixes to #62798 and #62793. I'm changing the title and description of this ticket from "2.6.5" to "2.6.6".

I intend to pick up this new version in the course of a major restructure to the port, as described in #62984 . Thus if someone wants to update the existing port with the version 2.6.6 code, go for it. But I expect to come along, eventually, with the new port file and 2.6.6.

Mind you, Freeciv version 3.0 is entering Release Candidate now, so maybe 2.6.6 will get overtaken by 3.0 if I don't hurry up! :-)

For the record, the description entered on 2021-06-26 was:

Freeciv 2.6.5 has just been released by upstream. Release notes: https://freeciv.fandom.com/wiki/NEWS-2.6.5 . Should contain upstream fixes to #62798 .

I intend to pick up this new version in the course of a major restructure to the port, as described in #62984 . Thus if someone wants to update the existing port with the version 2.6.5 code, go for it. But I expect to come along soon with the new port file and 2.6.5.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #63141

    • Property Owner set to JDLH
    • Property Status changed from new to assigned
    • Property Summary changed from freeciv @2.6.4_0: upgrade to 2.6.5 to freeciv @2.6.4_0: upgrade to 2.6.6
  • Ticket #63141 – Description

    initial v1  
    1 Freeciv 2.6.5 has just been released by upstream. Release notes: https://freeciv.fandom.com/wiki/NEWS-2.6.5 . Should contain upstream fixes to #62798 .
     1Freeciv 2.6.6 was released by upstream on 2021-12-10. Release notes: https://freeciv.fandom.com/wiki/NEWS-2.6.6 . Contain upstream fixes to #62798 and #62793.  I'm changing the title and description of this ticket from "2.6.5" to "2.6.6".
    22
    3 I intend to pick up this new version in the course of a major restructure to the port, as described in #62984 . Thus if someone wants to update the existing port with the version 2.6.5 code, go for it. But I expect to come along soon with the new port file and 2.6.5.
     3I intend to pick up this new version in the course of a major restructure to the port, as described in #62984 . Thus if someone wants to update the existing port with the version 2.6.6 code, go for it. But I expect to come along, eventually, with the new port file and 2.6.6.