FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Development

 
 
LinkBack Thread Tools
 
Old 02-06-2011, 05:23 PM
Manoj Srivastava
 
Default Branching changelogs or not

On Sun, Feb 06 2011, Andreas Tille wrote:

>
> 2. Whether upstream changelogs should be copied fully or in
> parts copied into Debian changelog and I think the New
> maintainers guide[3] gives a clear answer to mention only
> the changes of this *new* release specifically if these are
> closing known bugs in Debian and not just random features
> of the new release and definitely not changes of old
> releases.

My take on this has been that we should do what is most
important for the users: The changelog can be presented to the users on
upgrade, and when users chose to see it, and in those cases the users
arepresented with an option to abort the upgrade. The other audience
for the changelog entry us people looking into it in /usr/doc, and
perhaps fr dignificant changes or feature addtions; and lastly, the
future maintainers.

I would suggest we copy over from the upstream changelog any
information that might be relevant to the users; and that does mean
major features and significant changes, specifically backwards
incompatible changes.

So I tend to favour a changelog by changelog decision, not a
hard ruling one way or the other.

>
> [1] http://lists.debian.org/debian-med/2011/02/msg00048.html
> [2] http://www.debian.org/doc/maint-guide/ch-update.en.html#s-newupstream
> [3] http://lists.debian.org/debian-release/2010/12/msg01054.html

manoj
almost through the long tunnel with the legal department
--
Comedy, like Medicine, was never meant to be practiced by the general
public.
Manoj Srivastava <srivasta@acm.org> <http://www.golden-gryphon.com/>
4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20 05B6 CF48 9438 C577 9A1C


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87aai9yqbs.fsf@anzu.internal.golden-gryphon.com">http://lists.debian.org/87aai9yqbs.fsf@anzu.internal.golden-gryphon.com
 
Old 02-12-2011, 07:40 PM
Goswin von Brederlow
 
Default Branching changelogs or not

Andreas Tille <andreas@an3as.eu> writes:

> [Reply-To set to debian-devel]
>
> Hi,
>
> on the Debian Med list a discussion about handling changelogs was started[1]
> which addressed the following questions:
>
> 1. What to do with pre-Debian-Release changelogs (if packaging
> needed some time and went through several intermediate steps
> before it was uploaded to ftp.d.o (with the special case of
> releases in other distros).
> There was the conclusion to basically keep this changelog
> entries.

My opinion here is that it depends. There are basically 2 cases:

1) local developement builds that don't leave the house

I often compile several versions of a package till I'm satisfied.
Sometimes I ask others to test them but in a verry controlled
enviroment. The package isn't spread. None the less it helps to bump the
version for every build to keep them straight when discussing errors.

But when releasing the final version for upload all those intermediate
versions are best collapsed into one changelog entry. No need to mention
all the in-house, so to speak, testing.

2) intermittant versions that the public might get hold of

If I upload a version to e.g. mentors it becomes public. If the sponsor
then finds some bug in the upload, usualy days later, I tend to bump the
version and keep the changelog entry. People might have grabed it from
mentors and installed it and still have it installed weeks or month
later. They might also report bugs on it. If the intermittant versions
are removed from the changelog the version tracking in the BTS can't
work.

On the other hand this means the sponsor has to include multiple
changelog entries in the changes file (important for closing bugs). So
it is a balaning act.

MfG
Goswin


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87r5bd6l6c.fsf@frosties.localnet">http://lists.debian.org/87r5bd6l6c.fsf@frosties.localnet
 

Thread Tools




All times are GMT. The time now is 12:44 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org