From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- .../20110609/bb4de47b/attachment-0001.html | 41 ++++++++++++++++++++++ .../attachments/20110609/bb4de47b/attachment.html | 41 ++++++++++++++++++++++ 2 files changed, 82 insertions(+) create mode 100644 zarb-ml/mageia-dev/attachments/20110609/bb4de47b/attachment-0001.html create mode 100644 zarb-ml/mageia-dev/attachments/20110609/bb4de47b/attachment.html (limited to 'zarb-ml/mageia-dev/attachments/20110609/bb4de47b') diff --git a/zarb-ml/mageia-dev/attachments/20110609/bb4de47b/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20110609/bb4de47b/attachment-0001.html new file mode 100644 index 000000000..7a857a9f2 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110609/bb4de47b/attachment-0001.html @@ -0,0 +1,41 @@ + + +

Le jeudi 9 juin 2011 07:00:24, Anssi Hannula a écrit :

+

> On 09.06.2011 02:25, Michael Scherer wrote:

+

> > I guess we can start with a list of exception :

+

> >

+

> > - stuff that should be updated to latest version, because the security

+

> > support for older releases ( firefox, chrome ) is too hard

+

> > -> we update to latest version if there is no regression and a strong

+

> > reason to upgrade ( severe bugfixes, security issue, breakages ).

+

> > Exception of this category should be very expectional

+

> >

+

> > - stuff where there is strict bugfixes only release

+

> > ( postgresql ), or update to a stable version ( which should be a bugfix

+

> > only release when compared to beta/rc :) )

+

> > -> we upgrade to stable ( for rc/beta )

+

> > -> we do version update if it is bug fixes and if the packager is ok

+

> > with it ( and if the rules of the bugfix branches are clearly documented

+

> > )

+

> >

+

> > - everything else

+

> > -> only minimal patches

+

> >

+

> > The question of game is still open, ie, should it go in 1st category, or

+

> > should we have different rules to see what should be there or not ?

+

> >

+

> > I guess this would only be for networked game ?

+

>

+

> Yes. Note that this applies to some other software that communicates

+

> with outside systems as well, e.g. subdownloader. Maybe also Vuze if the

+

> content delivery system requires a version update.

+

>

+

> Maybe the correct phrasing would be something like:

+

> - Packages where some functions no longer work due to remote server

+

> changes, requiring a newer version of the package.

+


+

Agreed.

+


+

Samuel

\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20110609/bb4de47b/attachment.html b/zarb-ml/mageia-dev/attachments/20110609/bb4de47b/attachment.html new file mode 100644 index 000000000..7a857a9f2 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110609/bb4de47b/attachment.html @@ -0,0 +1,41 @@ + + +

Le jeudi 9 juin 2011 07:00:24, Anssi Hannula a écrit :

+

> On 09.06.2011 02:25, Michael Scherer wrote:

+

> > I guess we can start with a list of exception :

+

> >

+

> > - stuff that should be updated to latest version, because the security

+

> > support for older releases ( firefox, chrome ) is too hard

+

> > -> we update to latest version if there is no regression and a strong

+

> > reason to upgrade ( severe bugfixes, security issue, breakages ).

+

> > Exception of this category should be very expectional

+

> >

+

> > - stuff where there is strict bugfixes only release

+

> > ( postgresql ), or update to a stable version ( which should be a bugfix

+

> > only release when compared to beta/rc :) )

+

> > -> we upgrade to stable ( for rc/beta )

+

> > -> we do version update if it is bug fixes and if the packager is ok

+

> > with it ( and if the rules of the bugfix branches are clearly documented

+

> > )

+

> >

+

> > - everything else

+

> > -> only minimal patches

+

> >

+

> > The question of game is still open, ie, should it go in 1st category, or

+

> > should we have different rules to see what should be there or not ?

+

> >

+

> > I guess this would only be for networked game ?

+

>

+

> Yes. Note that this applies to some other software that communicates

+

> with outside systems as well, e.g. subdownloader. Maybe also Vuze if the

+

> content delivery system requires a version update.

+

>

+

> Maybe the correct phrasing would be something like:

+

> - Packages where some functions no longer work due to remote server

+

> changes, requiring a newer version of the package.

+


+

Agreed.

+


+

Samuel

\ No newline at end of file -- cgit v1.2.1