Re: Mentioning proposed-updates on the main website
Josip Rodin wrote: On Mon, Nov 05, 2007 at 07:50:43AM +0100, Luk Claes wrote: I just committed that new page to CVS, please feel free to... embrace and extend :) [...] It only demonstrates why finally documenting this can be very helpfull :-) Thank you very much for starting the page! Um, you are aware that all I did was copypaste one standard header line and a bit of HTML-formatted content into a file with the extension .wml, and then cvs add cvs commit that? :) So where is the wrong content you copied from, what's the URL? I interpolated that from security/faq and releases/etch/errata Ok, though there are no errors in these, but I understand how the misinterpretation could happen :-) Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mentioning proposed-updates on the main website
Josip Rodin wrote: On Tue, Oct 23, 2007 at 09:57:13PM +0200, Josip Rodin wrote: On Tue, Oct 23, 2007 at 08:13:19PM +0200, Luk Claes wrote: As you may (or may not) know proposed-updates is used as a basis for the next point release. As such it would be good that people would use it more so we find most bugs *before* a point release. To make this happen I want to mention proposed-updates more visibly on the main website. Does anyone have good ideas how and where on the website I should mention proposed-updates (and oldstable-proposed-updates and maybe the process involved)? /releases/stable/errata actually includes some information about that, but I'm not sure where else. Maybe we need a new page called /releases/proposed-updates that explains the concept better, and then link that one from other places? I just committed that new page to CVS, please feel free to... embrace and extend :) And correct apparantly :-( Uploading will only work when targeting 'stable', 'stable-security' or 'proposed-updates' for proposed-updates and targeting 'oldstable', 'oldstable-security' or 'oldstable-proposed-updates'. Mentioning etch-proposed-updates, stable-proposed-updates or similar as a target won't work... After the upload the packages reach a NEW queue like system and when members of the Stable Release Team have accepted packages to migrate to proposed-updates these packages will very likely be included in the next point release... It only demonstrates why finally documenting this can be very helpfull :-) I'll also add a part about uploading best practices... Thank you very much for starting the page! Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mentioning proposed-updates on the main website
On Mon, Nov 05, 2007 at 07:50:43AM +0100, Luk Claes wrote: I just committed that new page to CVS, please feel free to... embrace and extend :) [...] It only demonstrates why finally documenting this can be very helpfull :-) Thank you very much for starting the page! Um, you are aware that all I did was copypaste one standard header line and a bit of HTML-formatted content into a file with the extension .wml, and then cvs add cvs commit that? :) So where is the wrong content you copied from, what's the URL? I interpolated that from security/faq and releases/etch/errata -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mentioning proposed-updates on the main website
On Tue, Oct 23, 2007 at 09:57:13PM +0200, Josip Rodin wrote: On Tue, Oct 23, 2007 at 08:13:19PM +0200, Luk Claes wrote: As you may (or may not) know proposed-updates is used as a basis for the next point release. As such it would be good that people would use it more so we find most bugs *before* a point release. To make this happen I want to mention proposed-updates more visibly on the main website. Does anyone have good ideas how and where on the website I should mention proposed-updates (and oldstable-proposed-updates and maybe the process involved)? /releases/stable/errata actually includes some information about that, but I'm not sure where else. Maybe we need a new page called /releases/proposed-updates that explains the concept better, and then link that one from other places? I just committed that new page to CVS, please feel free to... embrace and extend :) -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mentioning proposed-updates on the main website
Hi, From: Josip Rodin Subject: Re: Mentioning proposed-updates on the main website Date: Tue, 23 Oct 2007 21:57:13 +0200 On Tue, Oct 23, 2007 at 08:13:19PM +0200, Luk Claes wrote: As you may (or may not) know proposed-updates is used as a basis for the next point release. As such it would be good that people would use it more so we find most bugs *before* a point release. To make this happen I want to mention proposed-updates more visibly on the main website. Does anyone have good ideas how and where on the website I should mention proposed-updates (and oldstable-proposed-updates and maybe the process involved)? /releases/stable/errata actually includes some information about that, but I'm not sure where else. Maybe we need a new page called /releases/proposed-updates that explains the concept better, and then link that one from other places? FYI http://www.debian.org/security/faq#proposed-updates currently explains that. Also, http://ftp-master.debian.org/proposed-updates.html shows the status. I worry about the status of the proposed updates. Those packages are not always released; only packages accepted by the Stable Release Manager are released and other packages will be dropped. So, IMHO those packages should not be recommended, unlike security updates. Enough explanation will be required. Many thanks, -nori -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mentioning proposed-updates on the main website
Kobayashi Noritada wrote: Hi, From: Josip Rodin Subject: Re: Mentioning proposed-updates on the main website Date: Tue, 23 Oct 2007 21:57:13 +0200 On Tue, Oct 23, 2007 at 08:13:19PM +0200, Luk Claes wrote: As you may (or may not) know proposed-updates is used as a basis for the next point release. As such it would be good that people would use it more so we find most bugs *before* a point release. To make this happen I want to mention proposed-updates more visibly on the main website. Does anyone have good ideas how and where on the website I should mention proposed-updates (and oldstable-proposed-updates and maybe the process involved)? /releases/stable/errata actually includes some information about that, but I'm not sure where else. Maybe we need a new page called /releases/proposed-updates that explains the concept better, and then link that one from other places? FYI http://www.debian.org/security/faq#proposed-updates currently explains that. Also, It only explains it very briefly and only to illustrate the connection with the security archive... http://ftp-master.debian.org/proposed-updates.html shows the status. I worry about the status of the proposed updates. Those packages are not always released; only packages accepted by the Stable Release Manager are released and other packages will be dropped. So, IMHO those packages should not be recommended, unlike security updates. Enough explanation will be required. Wrong. The status shows what's in the p-u-new queue. All that is accepted is in proposed-updates and gets released in the next point release... One more reason to have proper documentation... Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mentioning proposed-updates on the main website
Hi, From: Luk Claes Subject: Re: Mentioning proposed-updates on the main website Date: Thu, 25 Oct 2007 15:03:18 +0200 From: Josip Rodin Subject: Re: Mentioning proposed-updates on the main website Date: Tue, 23 Oct 2007 21:57:13 +0200 On Tue, Oct 23, 2007 at 08:13:19PM +0200, Luk Claes wrote: As you may (or may not) know proposed-updates is used as a basis for the next point release. As such it would be good that people would use it more so we find most bugs *before* a point release. To make this happen I want to mention proposed-updates more visibly on the main website. Does anyone have good ideas how and where on the website I should mention proposed-updates (and oldstable-proposed-updates and maybe the process involved)? /releases/stable/errata actually includes some information about that, but I'm not sure where else. Maybe we need a new page called /releases/proposed-updates that explains the concept better, and then link that one from other places? FYI http://www.debian.org/security/faq#proposed-updates currently explains that. Also, It only explains it very briefly and only to illustrate the connection with the security archive... Yes, I agree. http://ftp-master.debian.org/proposed-updates.html shows the status. I worry about the status of the proposed updates. Those packages are not always released; only packages accepted by the Stable Release Manager are released and other packages will be dropped. So, IMHO those packages should not be recommended, unlike security updates. Enough explanation will be required. Wrong. The status shows what's in the p-u-new queue. All that is accepted is in proposed-updates and gets released in the next point release... Oh, sorry, I misunderstood. I didn't know about the NEW queue of the proposed-updates. Thank you for explanation. Now that what I worried has gone, I'm +1 on your idea. Regards, -nori -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mentioning proposed-updates on the main website
Josip Rodin pisze: On Tue, Oct 23, 2007 at 08:13:19PM +0200, Luk Claes wrote: As you may (or may not) know proposed-updates is used as a basis for the next point release. As such it would be good that people would use it more so we find most bugs *before* a point release. To make this happen I want to mention proposed-updates more visibly on the main website. Does anyone have good ideas how and where on the website I should mention proposed-updates (and oldstable-proposed-updates and maybe the process involved)? /releases/stable/errata actually includes some information about that, but I'm not sure where else. Maybe we need a new page called /releases/proposed-updates that explains the concept better, and then link that one from other places? This idea is very good. I like it. Before that I, as regular user, was suprised by a new point release. Besides, the BTS suggests that bugs to the stable release are deprecated... Regards Wojciech Zareba -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Mentioning proposed-updates on the main website
Hi As you may (or may not) know proposed-updates is used as a basis for the next point release. As such it would be good that people would use it more so we find most bugs *before* a point release. To make this happen I want to mention proposed-updates more visibly on the main website. Does anyone have good ideas how and where on the website I should mention proposed-updates (and oldstable-proposed-updates and maybe the process involved)? Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mentioning proposed-updates on the main website
On Tue, Oct 23, 2007 at 08:13:19PM +0200, Luk Claes wrote: As you may (or may not) know proposed-updates is used as a basis for the next point release. As such it would be good that people would use it more so we find most bugs *before* a point release. To make this happen I want to mention proposed-updates more visibly on the main website. Does anyone have good ideas how and where on the website I should mention proposed-updates (and oldstable-proposed-updates and maybe the process involved)? /releases/stable/errata actually includes some information about that, but I'm not sure where else. Maybe we need a new page called /releases/proposed-updates that explains the concept better, and then link that one from other places? -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mentioning proposed-updates on the main website
On 10/23/07, Josip Rodin [EMAIL PROTECTED] wrote: On Tue, Oct 23, 2007 at 08:13:19PM +0200, Luk Claes wrote: As you may (or may not) know proposed-updates is used as a basis for the next point release. As such it would be good that people would use it more so we find most bugs *before* a point release. To make this happen I want to mention proposed-updates more visibly on the main website. Does anyone have good ideas how and where on the website I should mention proposed-updates (and oldstable-proposed-updates and maybe the process involved)? /releases/stable/errata actually includes some information about that, but I'm not sure where else. Maybe we need a new page called /releases/proposed-updates that explains the concept better, and then link that one from other places? from http://www.debian.org//misc/ to http://www.debian.org/devel/website/ and add a tab for proposed updates and process -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
