[Freeciv-Dev] [patch #3462] Separate metaserver version tag for Windows installer builds

2012-07-31 Thread Jacob Nevins
Follow-up Comment #1, patch #3462 (project freeciv):

Do we want a win32-S2_4 tag for 2.4.0-betaX/rcX, rather than plain win32?

When 2.5.0-beta1 comes round, we presumably want all the 2.4.x Windows builds
to display the current stable Win32 release, not the betas. Is that what
win32 will mean -- _stable_ win32 release?

(Also, I notice that the There is no newer %s release of freeciv available
is i18n'd, but the tag stable of course is not. Not sure we can reasonably
fix that, so perhaps need translators to add scare quotes '%s'.)

___

Reply to this item at:

  http://gna.org/patch/?3462

___
  Message sent via/by Gna!
  http://gna.org/


___
Freeciv-dev mailing list
Freeciv-dev@gna.org
https://mail.gna.org/listinfo/freeciv-dev


[Freeciv-Dev] [patch #3462] Separate metaserver version tag for Windows installer builds

2012-07-31 Thread Marko Lindqvist
Follow-up Comment #2, patch #3462 (project freeciv):

I think single win32 should mean latest stable release(1). If we had 2.4
releases following 2.4 specific tag, they would never inform users about 2.5
series existence.

I have added branch specific S2_4 and S2_5 tags to metaserver side, but I
don't plan to using them in any builds we do - they are just an option for
those people who make their own builds and want to follow specific branch (so
that if 2.5.0 is released before 2.4.3, 2.4.2 user will get notification about
2.4.3)

(1) Tag win32 should inform users of stable releases about stable releases
only. But I still think we should use it for *2.4* betas. There's no earlier
users of the tag, so listing betas there would not inform any stable users,
only those of earlier 2.4 betas. So using it for betas would not only provide
beta testing for the feature, but also be service to users.


Have to think about the translation thing. I think it would be doable by
adding file containing string(s) that is used only as POTFILES.in source.
Presumably these strings need to qualified ones, so some code magic is needed
too. Ah, stuff for new ticket.

___

Reply to this item at:

  http://gna.org/patch/?3462

___
  Message sent via/by Gna!
  http://gna.org/


___
Freeciv-dev mailing list
Freeciv-dev@gna.org
https://mail.gna.org/listinfo/freeciv-dev


[Freeciv-Dev] [patch #3462] Separate metaserver version tag for Windows installer builds

2012-07-30 Thread Marko Lindqvist
URL:
  http://gna.org/patch/?3462

 Summary: Separate metaserver version tag for Windows
installer builds
 Project: Freeciv
Submitted by: cazfi
Submitted on: Mon 30 Jul 2012 03:08:50 PM EEST
Category: bootstrap
Priority: 5 - Normal
  Status: Ready For Test
 Privacy: Public
 Assigned to: None
Originator Email: 
 Open/Closed: Open
 Discussion Lock: Any
 Planned Release: 2.4.0, 2.5.0

___

Details:

Since Windows installer often gets built only after (source) release, latest
Win Installer version is not same as latest freeciv release. Attached patch
gives Win Installer builds version tag of its own on metaserver so user is not
told about new version until build exist.



___

File Attachments:


---
Date: Mon 30 Jul 2012 03:08:50 PM EEST  Name: Win32Followtag.patch  Size: 502B
  By: cazfi

http://gna.org/patch/download.php?file_id=16247

___

Reply to this item at:

  http://gna.org/patch/?3462

___
  Message sent via/by Gna!
  http://gna.org/


___
Freeciv-dev mailing list
Freeciv-dev@gna.org
https://mail.gna.org/listinfo/freeciv-dev