On Thu, Aug 04, 2011 at 10:10:01PM +0200, gregor herrmann wrote: > On Thu, 04 Aug 2011 13:52:13 +0200, Ansgar Burchardt wrote: > > > > I think it would ease the maintainance of the packages if everyone goes for > > > option 2 and use git-dch(1) before releasing. > > I don't think this is a good idea for pkg-perl as PET would be > > confused: it uses the version number to notice changes, and even with > > that changed it would not have anything useful to show (as the changelog > > would not have changed). > > Without a changelog, we also cannot use the "IGNORE-VERSION" feature > > of PET (once PET3 has it anyway). > > Ouch. - And librdf-vcard-perl is already an exmaple. > > And the package also doesn't build to well (with git-buildpackage) if > there is no changelog entry for the new version at all. > > I've played a bit with git-dch --snapshot which works around this > issue. But I guess we don't want to have it's idea of a changelog > pushed. (And it's a specific tool again.) > > I guess we want to have at least a short entry with the new version > and "New upstream release." and PET commands in the pushed repo ... ---end quoted text--- Can't PET list the upstream/<version> tags of the repository to detect that there is a new upstream being worked on ? -- أحمد المحمودي (Ahmed El-Mahmoudy) Digital design engineer GPG KeyID: 0xEDDDA1B7 GPG Fingerprint: 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7
Attachment:
signature.asc
Description: Digital signature