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 --- .../20110619/0de93587/attachment-0001.html | 26 ++++++++++++++++++++++ .../attachments/20110619/0de93587/attachment.html | 26 ++++++++++++++++++++++ 2 files changed, 52 insertions(+) create mode 100644 zarb-ml/mageia-dev/attachments/20110619/0de93587/attachment-0001.html create mode 100644 zarb-ml/mageia-dev/attachments/20110619/0de93587/attachment.html (limited to 'zarb-ml/mageia-dev/attachments/20110619/0de93587') diff --git a/zarb-ml/mageia-dev/attachments/20110619/0de93587/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20110619/0de93587/attachment-0001.html new file mode 100644 index 000000000..5a85ca909 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110619/0de93587/attachment-0001.html @@ -0,0 +1,26 @@ + + +

andre999 <andr55@laposte.net> schrieb am 19.06.2011

+

> Another thought about the amended freeze process.

+

> Have you noticed how packagers sometimes set off an exchange of 10

+

> or more emails in attempts to get a package into the release

+

> during the freeze ?

+

> The packager wants to submit, but they can't because cauldron is

+

> frozen. Maybe if only pre-release were frozen, but cauldron open,

+

> they would accept submitting to cauldron after only 1 or 2

+

> exchanges. They would have the at least partial satisfaction of

+

> being able to submit their package (instead of waiting, and doing

+

> something else, probably elsewhere), and others would have been

+

> releaved of the hassle of dealing with their repeated requests. I

+

> think that would be more motivating for the packager in question,

+

> as well as the others involved. And packagers would avoid wasting

+

> both time and energy.

+

I don't know. I think most freeze push requests were due to the fact, that packagers wanted to have their baby in the release.

+

Because every packager knows, he only has to wait some days to submit it to Cauldron again.

+

So I don't think any packager would be any the happier by this solution.

+


+

I have to agree with misc. It would only mean having more work.

+


+

Oliver

\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20110619/0de93587/attachment.html b/zarb-ml/mageia-dev/attachments/20110619/0de93587/attachment.html new file mode 100644 index 000000000..5a85ca909 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110619/0de93587/attachment.html @@ -0,0 +1,26 @@ + + +

andre999 <andr55@laposte.net> schrieb am 19.06.2011

+

> Another thought about the amended freeze process.

+

> Have you noticed how packagers sometimes set off an exchange of 10

+

> or more emails in attempts to get a package into the release

+

> during the freeze ?

+

> The packager wants to submit, but they can't because cauldron is

+

> frozen. Maybe if only pre-release were frozen, but cauldron open,

+

> they would accept submitting to cauldron after only 1 or 2

+

> exchanges. They would have the at least partial satisfaction of

+

> being able to submit their package (instead of waiting, and doing

+

> something else, probably elsewhere), and others would have been

+

> releaved of the hassle of dealing with their repeated requests. I

+

> think that would be more motivating for the packager in question,

+

> as well as the others involved. And packagers would avoid wasting

+

> both time and energy.

+

I don't know. I think most freeze push requests were due to the fact, that packagers wanted to have their baby in the release.

+

Because every packager knows, he only has to wait some days to submit it to Cauldron again.

+

So I don't think any packager would be any the happier by this solution.

+


+

I have to agree with misc. It would only mean having more work.

+


+

Oliver

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