[arch-dev-public] New ISO release thread, please all read!
Ok, according to the last thread about releasing on saturday i summarize: - most agree with releasing a new iso that just works - New codename? A new iso will be released in november which contains a new major kernel, which we all agreed earlier this year should trigger a new codename and release/filename. At the moment it would mean much work to regenerate the ISOs with only to include a new code name. With entering kernel .23 series we should bump initscripts to a new code name, suggestions are welcome :) one mentioned was Hardcore - Release/File name of ISOs? ok here started the confusion, these ISOs will still contain the same major kernel series as in 2007.08 ISOs. There was also a thread about name scheme and we wanted to use -0.x as developer ISOs and [1-9] as release/bugfix versions. According to this it would be logical to use here 2007.08-2 as release/filename we could still use the iso/2007.08 directory on ftp and remove the others directories, see section below. - Remove of old ISOs and addons? All old ISOs ftp routines are broken. Also every ISO had some kind of itches which now are all fixed, it would make sense to remove all old ISOs and addons from ftp/iso. Addons are not necessary anymore with latest ISOs because most fast enough drivers are now included on the media itself. comments, thoughts and simple agrees/denies are welcome thanks greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
On Thu, 2007-10-04 at 22:22 +0200, Tobias Powalowski wrote:
Ok, according to the last thread about releasing on saturday i summarize: - most agree with releasing a new iso that just works
- New codename? A new iso will be released in november which contains a new major kernel, which we all agreed earlier this year should trigger a new codename and release/filename.
agreed
At the moment it would mean much work to regenerate the ISOs with only to include a new code name. With entering kernel .23 series we should bump initscripts to a new code name, suggestions are welcome :) one mentioned was Hardcore
+1 for Hardcore
- Release/File name of ISOs? ok here started the confusion, these ISOs will still contain the same major kernel series as in 2007.08 ISOs. There was also a thread about name scheme and we wanted to use -0.x as developer ISOs and [1-9] as release/bugfix versions. According to this it would be logical to use here 2007.08-2 as release/filename we could still use the iso/2007.08 directory on ftp and remove the others directories, see section below.
Maybe I missed it, but what's wrong with 2007.08.2 to follow 2007.08.1?
- Remove of old ISOs and addons? All old ISOs ftp routines are broken. Also every ISO had some kind of itches which now are all fixed, it would make sense to remove all old ISOs and addons from ftp/iso. Addons are not necessary anymore with latest ISOs because most fast enough drivers are now included on the media itself.
-1. We shouldn't go deleting iso's just because they don't work anymore for FTP installs. Nothing would keep a user from installing 0.6 or so even and upgrading to current. We just need to make sure that everything links to the proper places. Dale
On 10/4/07, Dale Blount <dale@archlinux.org> wrote:
On Thu, 2007-10-04 at 22:22 +0200, Tobias Powalowski wrote:
Ok, according to the last thread about releasing on saturday i summarize: - most agree with releasing a new iso that just works
- New codename? A new iso will be released in november which contains a new major kernel, which we all agreed earlier this year should trigger a new codename and release/filename.
agreed
At the moment it would mean much work to regenerate the ISOs with only to include a new code name. With entering kernel .23 series we should bump initscripts to a new code name, suggestions are welcome :) one mentioned was Hardcore
+1 for Hardcore
- Release/File name of ISOs? ok here started the confusion, these ISOs will still contain the same major kernel series as in 2007.08 ISOs. There was also a thread about name scheme and we wanted to use -0.x as developer ISOs and [1-9] as release/bugfix versions. According to this it would be logical to use here 2007.08-2 as release/filename we could still use the iso/2007.08 directory on ftp and remove the others directories, see section below.
Maybe I missed it, but what's wrong with 2007.08.2 to follow 2007.08.1?
Yeah this was a long thread - it's a minor semantic difference to alleviate confusion YYYY.MM.X makes the X look like a day. The dash is used because everything else in our releases uses the dash to indicate a "release number".
Am Thu, 4 Oct 2007 22:22:44 +0200 schrieb Tobias Powalowski <t.powa@gmx.de>:
- New codename? A new iso will be released in november which contains a new major kernel, which we all agreed earlier this year should trigger a new codename and release/filename. At the moment it would mean much work to regenerate the ISOs with only to include a new code name. With entering kernel .23 series we should bump initscripts to a new code name, suggestions are welcome :) one mentioned was Hardcore
All members of FroSCon event alredy voted for "All you can Wuerstchen". Thanks again Google for sausages and O'Reilly for for the yellow water ;) Andy
All members of FroSCon event alredy voted for "All you can Wuerstchen".
Thanks again Google for sausages and O'Reilly for for the yellow water ;)
Andy
Does that mean that only the people at Froscon matter? I feel so important now. :(
On 10/4/07, eliott <eliott@cactuswax.net> wrote:
All members of FroSCon event alredy voted for "All you can Wuerstchen".
Thanks again Google for sausages and O'Reilly for for the yellow water ;)
Andy
Does that mean that only the people at Froscon matter? I feel so important now. :(
Do you actually *want* to drink yellow water? Ew
Friday 05 October 2007, Aaron Griffin wrote: | Do you actually *want* to drink yellow water? better than blue water - D -- .·´¯`·.¸.·´¯`·.¸¸.·´¯`·.¸.·´¯`·.¸.·´¯`·.¸.·´¯`·.¸¸.·´ ° ° ° ° ° ° ><((((º> ° ° ° ° ° <º)))>< <º)))><
-----Oorspronkelijk bericht----- Van: arch-dev-public-bounces@archlinux.org [mailto:arch-dev-public- bounces@archlinux.org] Namens Aaron Griffin Verzonden: vrijdag 5 oktober 2007 0:52 Aan: Public mailing list for ArchLinux development Onderwerp: Re: [arch-dev-public] New ISO release thread, please all read!
On 10/4/07, eliott <eliott@cactuswax.net> wrote:
All members of FroSCon event alredy voted for "All you can Wuerstchen".
Thanks again Google for sausages and O'Reilly for for the yellow water ;)
Andy
Does that mean that only the people at Froscon matter? I feel so important now. :(
Do you actually *want* to drink yellow water? Ew
They called it beer though, but we think it's something else... Kölsch...
Aaron Griffin schrieb:
Thanks again Google for sausages and O'Reilly for for the yellow water ;)
Andy Does that mean that only the people at Froscon matter? I feel so important now. :(
Do you actually *want* to drink yellow water? Ew
I didn't really want to, but I did anyway, after all it was for free. I wanted to eat Google Food and I did. Google knew what I wanted without me even telling them, it's awesome.
On Fri, October 5, 2007 06:22, Tobias Powalowski wrote:
Ok, according to the last thread about releasing on saturday i summarize: - most agree with releasing a new iso that just works
- New codename?
How about Sputnik? Yesterday/Today 4th October was 50 years since Sputnik was launched by the Russians, marking the beginning of the space race. Apart from that, agree with everything else :) James
Hi is it now okay if i do the ftp action this evening? removing all old isos and move in the new ones to iso/2007.08/ greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
-----Oorspronkelijk bericht----- Van: arch-dev-public-bounces@archlinux.org [mailto:arch-dev-public- bounces@archlinux.org] Namens Tobias Powalowski Verzonden: vrijdag 5 oktober 2007 11:29 Aan: Public mailing list for ArchLinux development Onderwerp: Re: [arch-dev-public] New ISO release thread, please all read!
Hi is it now okay if i do the ftp action this evening? removing all old isos and move in the new ones to iso/2007.08/
What about moving them to the archive? The non-FTP install ISOs still work, and in case there's someone having problems with a newer kernel on their hardware, they can't install arch if they don't have an old install CD around.
2007/10/5, Jan de Groot <jan@jgc.homeip.net>:
-----Oorspronkelijk bericht----- Van: arch-dev-public-bounces@archlinux.org [mailto:arch-dev-public- bounces@archlinux.org] Namens Tobias Powalowski Verzonden: vrijdag 5 oktober 2007 11:29 Aan: Public mailing list for ArchLinux development Onderwerp: Re: [arch-dev-public] New ISO release thread, please all read!
Hi is it now okay if i do the ftp action this evening? removing all old isos and move in the new ones to iso/2007.08/
What about moving them to the archive? The non-FTP install ISOs still work, and in case there's someone having problems with a newer kernel on their hardware, they can't install arch if they don't have an old install CD around.
I suggest this: 1) move all *-ftp.iso's to archive/ 2) move all *-base.iso's to archive/ too, except the last ISO with previous kernel version. -- Roman Kyrylych (Роман Кирилич)
On 10/5/07, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
I suggest this: 1) move all *-ftp.iso's to archive/ 2) move all *-base.iso's to archive/ too, except the last ISO with previous kernel version.
This sounds like a plan, but it's going to bork our rsyncing hard. Eliott, Dale, Jan - do you guys have any sort of plan of attack here? What would be the best way to do this that wouldn't force everything to rsync like 5gigs all at once? On 10/5/07, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
2007/10/5, Pierre Schmitz <pierre@archlinux.de>:
I am still confused why its not named 2007.10. So the iso got its name from the date when the major release of the kernel included was done?
Yes.
Correct. As a proof-of-concept, ubuntu version 6.06 was released (which is date based but they mung it a bit) and later on on 08-2006 they released a bug fix 6.06.1 version. We're doing the same thing. I think this date+version thing is confusing people here. Don't think of it as the date of release - think of it as a version number that just happens to be the date of release.
Am Freitag, 5. Oktober 2007 schrieb Aaron Griffin:
On 10/5/07, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
I suggest this: 1) move all *-ftp.iso's to archive/ 2) move all *-base.iso's to archive/ too, except the last ISO with previous kernel version.
This sounds like a plan, but it's going to bork our rsyncing hard.
Eliott, Dale, Jan - do you guys have any sort of plan of attack here? What would be the best way to do this that wouldn't force everything to rsync like 5gigs all at once?
Hi I moved in the ISOs to 2007.08/ directory and remove the 2007.10 directory just a suggestion would it make sense to move the archive isos to a dir which is not rsynced and then add them slowly again to archive/ directory? just an idea greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
On 10/5/07, Tobias Powalowski <t.powa@gmx.de> wrote:
Am Freitag, 5. Oktober 2007 schrieb Aaron Griffin:
On 10/5/07, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
I suggest this: 1) move all *-ftp.iso's to archive/ 2) move all *-base.iso's to archive/ too, except the last ISO with previous kernel version.
This sounds like a plan, but it's going to bork our rsyncing hard.
Eliott, Dale, Jan - do you guys have any sort of plan of attack here? What would be the best way to do this that wouldn't force everything to rsync like 5gigs all at once?
Hi I moved in the ISOs to 2007.08/ directory and remove the 2007.10 directory just a suggestion would it make sense to move the archive isos to a dir which is not rsynced and then add them slowly again to archive/ directory? just an idea
1) I have no idea what you just said tobias. 2) Is Aaron's question now a moot point since you just said you moved isos or something? Or were you talking about moving them but didn't do it yet? 3) pants
Am Samstag, 6. Oktober 2007 schrieb eliott:
On 10/5/07, Tobias Powalowski <t.powa@gmx.de> wrote:
Am Freitag, 5. Oktober 2007 schrieb Aaron Griffin:
On 10/5/07, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
I suggest this: 1) move all *-ftp.iso's to archive/ 2) move all *-base.iso's to archive/ too, except the last ISO with previous kernel version.
This sounds like a plan, but it's going to bork our rsyncing hard.
Eliott, Dale, Jan - do you guys have any sort of plan of attack here? What would be the best way to do this that wouldn't force everything to rsync like 5gigs all at once?
Hi I moved in the ISOs to 2007.08/ directory and remove the 2007.10 directory just a suggestion would it make sense to move the archive isos to a dir which is not rsynced and then add them slowly again to archive/ directory? just an idea
1) I have no idea what you just said tobias. 2) Is Aaron's question now a moot point since you just said you moved isos or something? Or were you talking about moving them but didn't do it yet? 3) pants
_______________________________________________ arch-dev-public mailing list arch-dev-public@archlinux.org http://archlinux.org/mailman/listinfo/arch-dev-public
i placed the new isos to 2007.08 directory, the old isos need to move somehow. greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
On 10/6/07, eliott <eliott@cactuswax.net> wrote:
On 10/5/07, Tobias Powalowski <t.powa@gmx.de> wrote:
Am Freitag, 5. Oktober 2007 schrieb Aaron Griffin:
On 10/5/07, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
I suggest this: 1) move all *-ftp.iso's to archive/ 2) move all *-base.iso's to archive/ too, except the last ISO with previous kernel version.
This sounds like a plan, but it's going to bork our rsyncing hard.
Eliott, Dale, Jan - do you guys have any sort of plan of attack here? What would be the best way to do this that wouldn't force everything to rsync like 5gigs all at once?
Hi I moved in the ISOs to 2007.08/ directory and remove the 2007.10 directory just a suggestion would it make sense to move the archive isos to a dir which is not rsynced and then add them slowly again to archive/ directory? just an idea
1) I have no idea what you just said tobias. 2) Is Aaron's question now a moot point since you just said you moved isos or something? Or were you talking about moving them but didn't do it yet? 3) pants
Yeah ok. The ISO releases are floating around but we need to get rid of the OLD isos... it seems like moving them to some archive/ dir would be ideal, but that's a few gigs worth of rsyncing from each server - we are looking for an intelligent way to do this. Ideas?
2007/10/7, Aaron Griffin <aaronmgriffin@gmail.com>:
On 10/6/07, eliott <eliott@cactuswax.net> wrote:
On 10/5/07, Tobias Powalowski <t.powa@gmx.de> wrote:
Am Freitag, 5. Oktober 2007 schrieb Aaron Griffin:
On 10/5/07, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
I suggest this: 1) move all *-ftp.iso's to archive/ 2) move all *-base.iso's to archive/ too, except the last ISO with previous kernel version.
This sounds like a plan, but it's going to bork our rsyncing hard.
Eliott, Dale, Jan - do you guys have any sort of plan of attack here? What would be the best way to do this that wouldn't force everything to rsync like 5gigs all at once?
Hi I moved in the ISOs to 2007.08/ directory and remove the 2007.10 directory just a suggestion would it make sense to move the archive isos to a dir which is not rsynced and then add them slowly again to archive/ directory? just an idea
1) I have no idea what you just said tobias. 2) Is Aaron's question now a moot point since you just said you moved isos or something? Or were you talking about moving them but didn't do it yet? 3) pants
Yeah ok. The ISO releases are floating around but we need to get rid of the OLD isos... it seems like moving them to some archive/ dir would be ideal, but that's a few gigs worth of rsyncing from each server - we are looking for an intelligent way to do this. Ideas?
Do all mirrors sync the archive directory? Recently I checked all our mirrors and AFAIR there was no archive/ on (most of) them. -- Roman Kyrylych (Роман Кирилич)
Do all mirrors sync the archive directory? Recently I checked all our mirrors and AFAIR there was no archive/ on (most of) them.
No. Not all mirrors do, and that is the point. We don't want to place an undue space burden on mirrors to hold very old data. A few mirrors do sync archive, and that is their prerogative.
On Fri, 2007-10-05 at 11:13 -0500, Aaron Griffin wrote:
On 10/5/07, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
I suggest this: 1) move all *-ftp.iso's to archive/ 2) move all *-base.iso's to archive/ too, except the last ISO with previous kernel version.
This sounds like a plan, but it's going to bork our rsyncing hard.
Eliott, Dale, Jan - do you guys have any sort of plan of attack here? What would be the best way to do this that wouldn't force everything to rsync like 5gigs all at once?
Move one ISO back to /archive/, wait 48 hours, rinse, repeat. Dale
On 10/8/07, Dale Blount <dale@archlinux.org> wrote:
On Fri, 2007-10-05 at 11:13 -0500, Aaron Griffin wrote:
On 10/5/07, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
I suggest this: 1) move all *-ftp.iso's to archive/ 2) move all *-base.iso's to archive/ too, except the last ISO with previous kernel version.
This sounds like a plan, but it's going to bork our rsyncing hard.
Eliott, Dale, Jan - do you guys have any sort of plan of attack here? What would be the best way to do this that wouldn't force everything to rsync like 5gigs all at once?
Move one ISO back to /archive/, wait 48 hours, rinse, repeat.
This was tpowa's suggestion as well 8) You win this round tpowa!
Am Freitag, 5. Oktober 2007 11:29:06 schrieb Tobias Powalowski:
removing all old isos and move in the new ones to iso/2007.08/
I am still confused why its not named 2007.10. So the iso got its name from the date when the major release of the kernel included was done? But it's only a name so I don't mind that much. -- archlinux.de
2007/10/5, Pierre Schmitz <pierre@archlinux.de>:
Am Freitag, 5. Oktober 2007 11:29:06 schrieb Tobias Powalowski:
removing all old isos and move in the new ones to iso/2007.08/
I am still confused why its not named 2007.10. So the iso got its name from the date when the major release of the kernel included was done?
Yes. -- Roman Kyrylych (Роман Кирилич)
participants (11)
-
Aaron Griffin
-
Andreas Radke
-
Dale Blount
-
Damir Perisa
-
eliott
-
James Rayner
-
Jan de Groot
-
Pierre Schmitz
-
Roman Kyrylych
-
Thomas Bächler
-
Tobias Powalowski