Saw that the automatically generated entries in this file still says Marek is making them.
No point in changing them there at the moment since there is no official new maintainer yet.
could be replaced by something generic, like "pike developers" or "noone".
although i believe the name there should point to the person that is responsible for that particular changelog entry, not the maintainer of the package. so ideally, export.pike should pick up the right value from the environment, or i guess it could just point to you as the release manager.
greetings, martin.
As I wrote earlier, there is not much point generating two changelog entries per snapshot unless every snapshot is uploaded to Debian. It just adds noise.
But since people might want to download snapshots and build bleeding edge Debian packages themselves, it may be a good idea if the top entry version matches the current version. In that case you can simply change the version and timestamp without adding a new entry. The maintainer field can be set to something like "Pike snapshot autobuilder" and the Debian part of the version should begin with a '0', so that an official Debian package supersedes it, e.g. 7.6.246-0.1 or 7.6.246-0pike1.
As I wrote earlier, there is not much point generating two changelog entries per snapshot unless every snapshot is uploaded to Debian. It just adds noise.
But since people might want to download snapshots and build bleeding edge Debian packages themselves, it may be a good idea if the top entry version matches the current version. In that case you can simply change the version and timestamp without adding a new entry. The maintainer field can be set to something like "Pike snapshot autobuilder" and the Debian part of the version should begin with a '0', so that an official Debian package supersedes it, e.g. 7.6.246-0.1 or 7.6.246-0pike1.
As I wrote earlier, there is not much point generating two changelog entries per snapshot unless every snapshot is uploaded to Debian. It just adds noise.
But since people might want to download snapshots and build bleeding edge Debian packages themselves, it may be a good idea if the top entry version matches the current version. In that case you can simply change the version and timestamp without adding a new entry. The maintainer field can be set to something like "Pike snapshot autobuilder" and the Debian part of the version should begin with a '0', so that an official Debian package supersedes it, e.g. 7.6.246-0.1 or 7.6.246-0pike1.
As I wrote earlier, there is not much point generating two changelog entries per snapshot unless every snapshot is uploaded to Debian. It just adds noise.
But since people might want to download snapshots and build bleeding edge Debian packages themselves, it may be a good idea if the top entry version matches the current version. In that case you can simply change the version and timestamp without adding a new entry. The maintainer field can be set to something like "Pike snapshot autobuilder" and the Debian part of the version should begin with a '0', so that an official Debian package supersedes it, e.g. 7.6.246-0.1 or 7.6.246-0pike1.
As I wrote earlier, there is not much point generating two changelog entries per snapshot unless every snapshot is uploaded to Debian. It just adds noise.
But since people might want to download snapshots and build bleeding edge Debian packages themselves, it may be a good idea if the top entry version matches the current version. In that case you can simply change the version and timestamp without adding a new entry. The maintainer field can be set to something like "Pike snapshot autobuilder" and the Debian part of the version should begin with a '0', so that an official Debian package supersedes it, e.g. 7.6.246-0.1 or 7.6.246-0pike1.
pike-devel@lists.lysator.liu.se
-
Magnus Holmgren, FR Ryd (Nu med m�l och syfte) ＠ Pike (-) developers forum -
Martin Bähr -
Martin Stjernholm, Roxen IS ＠ Pike developers forum
-
Peter Bortas ＠ Pike developers forum