On Sat, Nov 06, 2010 at 08:18:41AM +1100, Ben Finney wrote: > Moving this non-Python part of the discussion to ‘debian-mentors’. > > Stefano Rivera <stefano@rivera.za.net> writes: > > > First, we don't tag releases until they are uploaded. You can leave the > > changelog entry as UNRELEASED, and the sponsor will fix that and tag on > > upload. > > Is this common practise among sponsors? No, it's merely the convention of the Python application/modules teams in the SVN repository. This workflow (UNRELEASED until ready, tagged after upload) helps keep the package entropy tracker sane while multiple contributors are committing changes. > I was under the impression that the maintainer should create the package > exactly as it should be uploaded into Debian, and the sponsor can expect > to make no modifications before re-building. So I always put the > intended target suite in the changelog entry. Wheras this is the convention of the mentors list, where it's accepted that a .dsc should be presented with zero or little modification required. -- Jonathan Wiltshire 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
Attachment:
signature.asc
Description: Digital signature