Task:Providing changes since last version of a package - Revision history

imported_>amigadave: /* XML file */ use

2011-02-24T14:19:11Z

XML file: use <source>

← Older revision		Revision as of 14:19, 24 February 2011
Line 17:		Line 17:

	An example:		An example:
			<source lang="xml">
	<maemo-release-changelog>		<maemo-release-changelog>
	<revision release-date="2008-07-07 23:05:00" revision="<package revision>">		<revision release-date="2008-07-07 23:05:00" revision="<package revision>">
Line 29:		Line 30:
	</release>		</release>
	</maemo-release-changelog>		</maemo-release-changelog>
			</source>
	When the XML file isn't found, fallback to ChangeLog and changelog. [Proposed by [[User:framstag\|framstag]]]		When the XML file isn't found, fallback to ChangeLog and changelog. [Proposed by [[User:framstag\|framstag]]]

imported_>generalantilles: Categorization

2008-10-30T18:08:31Z

Categorization

← Older revision		Revision as of 18:08, 30 October 2008
Line 44:		Line 44:

	(Commenting on my own proposal): I both suggestions as valid and good ideas. However they solve different problems. My proposal collects more data than acutally required to display the latest change (it has history) and is thus more complex, while the other solutions is far simpler and exactly fits the initial requirement. So the questions is: How much changelog do we need? For what purpose? If we do not find more purpose then initially requested I would suggest to start with the header aproach - just because it is simpler.--[[User:framstag\|framstag]] 19:27, 14 July 2008 (UTC)		(Commenting on my own proposal): I both suggestions as valid and good ideas. However they solve different problems. My proposal collects more data than acutally required to display the latest change (it has history) and is thus more complex, while the other solutions is far simpler and exactly fits the initial requirement. So the questions is: How much changelog do we need? For what purpose? If we do not find more purpose then initially requested I would suggest to start with the header aproach - just because it is simpler.--[[User:framstag\|framstag]] 19:27, 14 July 2008 (UTC)


			[[Category:Community]]

imported_>generalantilles: Providing changes since last version of a package moved to Task:Providing changes since last version of a package: Moving to proper namespace

2008-08-28T02:54:03Z

Providing changes since last version of a package moved to Task:Providing changes since last version of a package: Moving to proper namespace

← Older revision	Revision as of 02:54, 28 August 2008
(No difference)

imported_>framstag: /* Comparison */

2008-07-14T19:27:27Z

Comparison

← Older revision		Revision as of 19:27, 14 July 2008
Line 43:		Line 43:
	=== Comparison ===		=== Comparison ===

	(Commenting on my own proposal): I both suggestions as valid and good ideas. However they solve different problems. My proposal collects more data than acutally required to display the latest change (it has history) and is thus more complex, while the other solutions is far simpler and exactly fits the initial requirement. So the questions is: How much changelog do we need? For what purpose? If we do not find more purpose then initially requested I would suggest to start with the header aproach - just because it is simpler.--[[~~Special~~:~~Contributions/92.227.89.184~~\|~~92.227.89.184~~]] 19:26, 14 July 2008 (UTC)		(Commenting on my own proposal): I both suggestions as valid and good ideas. However they solve different problems. My proposal collects more data than acutally required to display the latest change (it has history) and is thus more complex, while the other solutions is far simpler and exactly fits the initial requirement. So the questions is: How much changelog do we need? For what purpose? If we do not find more purpose then initially requested I would suggest to start with the header aproach - just because it is simpler.--[[User:framstag\|framstag]] 19:27, 14 July 2008 (UTC)

92.227.89.184: /* Comparison */

2008-07-14T19:26:21Z

Comparison

← Older revision		Revision as of 19:26, 14 July 2008
Line 43:		Line 43:
	=== Comparison ===		=== Comparison ===

	(Commenting on my own proposal): I both suggestions as valid and good ideas. However they solve different problems. My proposal collects more data than acutally required to display the latest change (it has history) and is thus more complex, while the other solutions is far simpler and exactly fits the initial requirement. So the questions is: How much changelog do we need? For what purpose? If we do not find more purpose then initially requested I would suggest to start with the header aproach - just because it is simpler.		(Commenting on my own proposal): I both suggestions as valid and good ideas. However they solve different problems. My proposal collects more data than acutally required to display the latest change (it has history) and is thus more complex, while the other solutions is far simpler and exactly fits the initial requirement. So the questions is: How much changelog do we need? For what purpose? If we do not find more purpose then initially requested I would suggest to start with the header aproach - just because it is simpler.--[[Special:Contributions/92.227.89.184\|92.227.89.184]] 19:26, 14 July 2008 (UTC)

92.227.89.184: /* Proposed solutions */

2008-07-14T19:25:25Z

Proposed solutions

← Older revision		Revision as of 19:25, 14 July 2008
Line 40:		Line 40:

	Certainly for downloads.maemo.org; for more detail the debian/changelog is available and /should/ be the definitive location so we don't diverge too much from other Debian-based systems. --[[User:jaffa]]		Certainly for downloads.maemo.org; for more detail the debian/changelog is available and /should/ be the definitive location so we don't diverge too much from other Debian-based systems. --[[User:jaffa]]

			=== Comparison ===

			(Commenting on my own proposal): I both suggestions as valid and good ideas. However they solve different problems. My proposal collects more data than acutally required to display the latest change (it has history) and is thus more complex, while the other solutions is far simpler and exactly fits the initial requirement. So the questions is: How much changelog do we need? For what purpose? If we do not find more purpose then initially requested I would suggest to start with the header aproach - just because it is simpler.

92.227.89.184: /* XML file */

2008-07-14T19:21:06Z

XML file

← Older revision		Revision as of 19:21, 14 July 2008
Line 30:		Line 30:
	</maemo-release-changelog>		</maemo-release-changelog>

	When the XML file isn't found, fallback to ChangeLog and changelog. [Proposed by ~~Tim Teulings~~]		When the XML file isn't found, fallback to ChangeLog and changelog. [Proposed by [[User:framstag\|framstag]]]

	I vote for this solution.		I vote for this solution.

imported_>anidel: /* XML file */

2008-07-10T15:33:58Z

XML file

← Older revision		Revision as of 15:33, 10 July 2008
Line 31:		Line 31:

	When the XML file isn't found, fallback to ChangeLog and changelog. [Proposed by Tim Teulings]		When the XML file isn't found, fallback to ChangeLog and changelog. [Proposed by Tim Teulings]

			I vote for this solution.
			Actually a small tool could be created to convert the XML to TXT (thus becoming a regular ChangeLog file)--[[User:anidel\|anidel]] 15:33, 10 July 2008 (UTC)

	=== Additional header in debian/control ===		=== Additional header in debian/control ===

imported_>jaffa: /* Background */ Fix typo

2008-07-10T15:31:11Z

Background: Fix typo

← Older revision		Revision as of 15:31, 10 July 2008
Line 1:		Line 1:
	== Background ==		== Background ==

	For the Application ~~manager~~ and downloads.maemo.org it would be nice to have automatically updated information about changes since last version of a package. It would be good to have the change information available inside a package.		For the Application Manager and downloads.maemo.org it would be nice to have automatically updated information about changes since last version of a package. It would be good to have the change information available inside a package.

	== Problems ==		== Problems ==

imported_>xfade: New page: == Background == For the Application manager and downloads.maemo.org it would be nice to have automatically updated information about changes since last version of a package. It would be ...

2008-07-10T14:39:59Z

New page: == Background == For the Application manager and downloads.maemo.org it would be nice to have automatically updated information about changes since last version of a package. It would be ...

New page

== Background ==

For the Application manager and downloads.maemo.org it would be nice to have automatically updated information about changes since last version of a package. It would be good to have the change information available inside a package.

== Problems ==

=== debian package changelog ===
The debian package changelog describes changed to the package made by the package maintainer. If maintainer and developer are different a changelog entry for a major relase could just contain "New upstream version".

=== ChangeLog ===
Another option would be to use the ChangeLog of the original source package - this would contain upstream documentation to changes in the original software. You would expect to find new features there. However upstream information might contain information of varying detail. Another problem is that the ChangeLog is "owned" by upstream, the maintainer can/should not change it.

== Proposed solutions ==

=== XML file ===
Add a Maemo specific XML file for each package.

An example:
<maemo-release-changelog>
<revision release-date="2008-07-07 23:05:00" revision="<package revision>">
<description>
Packages new upstream version.
</description>
</revision>
<release release-date="2008-07-01 11:55:00" version="<source package version>">
<description>
Now plays funny sound on start.
</description>
</release>
</maemo-release-changelog>

When the XML file isn't found, fallback to ChangeLog and changelog. [Proposed by Tim Teulings]

=== Additional header in debian/control ===

I wonder whether another header would be sufficient in debian/control? We've already got XB-Maemo-Icon, adding XBS-Version-Changes or something could be sufficient.

Certainly for downloads.maemo.org; for more detail the debian/changelog is available and /should/ be the definitive location so we don't diverge too much from other Debian-based systems. --[[User:jaffa]]