Re: [leaf-devel] tagging beta1?
Am Dienstag, 23. November 2010, 20:38:07 schrieb KP Kirchdoerfer: > What else needs to be done before release? > > 1) Add wiki to our webpages > 2) Add a mailinglist (cvs-auto?) for trac Mike, can you pls take of 1) and 2) ??? > 4) add an apps section in cvs with the lrp's done kp -- Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] tagging beta1?
Am Dienstag, 23. November 2010, 20:38:07 schrieb KP Kirchdoerfer: > Gents; > > I think it's about time to tag 4.0-beta1. done. New commits will go into beta2. kp -- Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] tagging beta1?
Am Mittwoch, 24. November 2010, 22:18:56 schrieb davidMbrooke: > On Tue, 2010-11-23 at 20:38 +0100, KP Kirchdoerfer wrote: > > Gents; > > > > I think it's about time to tag 4.0-beta1. > > > > I'm aware that we do have outstanding issues - like apkg merge, lack of > > ISDN support, kernel config improvements..., but the current code runs > > well for months (more or less) and it's time to get some feedback and > > help from the community. > > > > After tagging chnages in cvs will be included in beta2. > > > > What else needs to be done before release? > > > > 1) Add wiki to our webpages > > 2) Add a mailinglist (cvs-auto?) for trac > > 3) buildimage.pl should have two new templates (i486-isolinux-vga, i696- > > syslinux-vga) > > 4) add an apps section in cvs with the lrp's > > 5) add a "known issues" chapter to wiki > > 6) use trac for remaining issues (plus bugs etc) > > > > what do you think? > > > > kp > > Hi kp, > > I have just fixed Item #3 > Andrew: Have you had chance to look at buildimage.pl? Are you OK to use > this rather than geniso.sh? > > You have fixed Item #5 :-) > > 7) What about .lwp files? They are not part of the current images. Are > they even in CVS? Actually webconf needs some attention... No they have never been in cvs, at least not in the correct place. This should be improved until final release. Anyway webconf and lwp's are an add-on, which isn't really necessary, and not that useful for somewhat more advanced setups. > 8) What about my choice of the default LRP setting for the images? I > based this on the 3.x floppy image. They've been fine for a long time and will be a good start for 4.x. Maybe some enhancements are possible during he release process, now that we have more space on the target images than the 1.6MB previously. kp -- Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] tagging beta1?
24.11.2010 23:18, davidMbrooke пишет: > > Andrew: Have you had chance to look at buildimage.pl? Are you OK to use > this rather than geniso.sh? Yes, it'll be enough for me. Mainly I use ISO only for testing changes in VM before deployment on real hardware. -- Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] tagging beta1?
On Tue, 2010-11-23 at 20:38 +0100, KP Kirchdoerfer wrote: > Gents; > > I think it's about time to tag 4.0-beta1. > > I'm aware that we do have outstanding issues - like apkg merge, lack of ISDN > support, kernel config improvements..., but the current code runs well for > months (more or less) and it's time to get some feedback and help from the > community. > > After tagging chnages in cvs will be included in beta2. > > What else needs to be done before release? > > 1) Add wiki to our webpages > 2) Add a mailinglist (cvs-auto?) for trac > 3) buildimage.pl should have two new templates (i486-isolinux-vga, i696- > syslinux-vga) > 4) add an apps section in cvs with the lrp's > 5) add a "known issues" chapter to wiki > 6) use trac for remaining issues (plus bugs etc) > > what do you think? > > kp Hi kp, I have just fixed Item #3 Andrew: Have you had chance to look at buildimage.pl? Are you OK to use this rather than geniso.sh? You have fixed Item #5 :-) 7) What about .lwp files? They are not part of the current images. Are they even in CVS? Actually webconf needs some attention... 8) What about my choice of the default LRP setting for the images? I based this on the 3.x floppy image. dMb -- Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] cvs structure
On Mon, 2010-11-22 at 23:11 +0100, KP Kirchdoerfer wrote: > Am Montag, 1. November 2010, 22:04:59 schrieb davidMbrooke: > > On Mon, 2010-11-01 at 21:32 +0100, KP Kirchdoerfer wrote: > > > David; > > > > > > Am Sonntag, 31. Oktober 2010, 22:09:54 schrieb davidMbrooke: > > > > On Sun, 2010-10-31 at 20:50 +0100, KP Kirchdoerfer wrote: > > > > > Am Freitag, 29. Oktober 2010, 20:25:58 schrieb Andrew: > > > > > > > > > > Ok; I propose: > > > > > - just "core" and "contrib" repository (names are not fixed), testing > > > > > isn't needed - we can also put packages in contrib which we > > > > > consider for testing or provided as-is. > > > > > > > > Just to make sure I understand 100%, some examples: > > > >etc.lrp: Certainly part of "core". No debate. > > > > > > Maybe this also debatable :) > > > > > > The most radical way (besides opening it all) would be just to define > > > "core" just as buildenv and buildtool itself. Which is the bare minimum > > > to build packages on a definded base (uclibc version). > > > Though even that raises pb's. What if a user wants to provide a complete > > > new kernel arch? And in the developer guidelines and policies we asked > > > to provide modules not in the package, but with modules.tgz > > > > > > During 2.x and 3.x we thought about "core" mainly as "packages that are > > > provided on the floppy image" - but as that donÄt exist any longer..., > > > and it doesn't work very well in the long term. > > > > > > >asterisk.lrp: Certainly part of "contrib" (only if it is fixed?) > > > >aiccu.lrp: Not part of "core", since only relevant to some users, > > > >but > > > > > > > > you (kp) and I (dMb) would be willing to upgrade, test, repair etc. > > > > > > Both belongs shurely to "contrib" > > > > > > > Should we distinguish "supported" contrib from "unsupported" contrib? > > > > Something like "primary" (instead of "core" - approx 10 packages that > > > > EVERY user will need), "secondary" (tested and supported, but not > > > > "core"), then "contrib" for the others? > > > > > > Hmm, the idea of "approx 10 packages that every users need" is a good > > > one. Your "secondary" and "contrib" maybe rephrased as "packages" and > > > "testing"? (primary/packages/testing) > > > > > > kp > > > > Hi kp, > > > > To me, "testing" implies a temporary state: "will move somewhere else > > when testing is successful", which isn't quite what I had in mind. A > > package in "contrib" will always stay in "contrib"... > > > > In terms of packages (i.e. ignoring buildenv and buildtool) then "core" > > or "primary" is: > >- kernel (OK, not really a "package" as such...) > >- initrd > >- root > >- etc > >- modules > > Would a system actually run with just this list (+ moddb + configdb)? > > > > Then there are "mainstream" add-on packages: > >- iptables > >- shorwall > > - Hence also libm, perl > >- ip6tables > >- shorwall6 > >- dropbear > >- dhcpcd > >- dnsmasq > >- mhttpd > >- webconf > >- A few more perhaps? > > > > Others would be "contrib". > > > > So maybe 3 categories: "core", "mainstream", "contrib" ??? > > > > dMb > > David; > > I've slept and thought over this the past weeks. > In the meantime Erich has been added to the list of developers being able to > commit and it worked out pretty well. > > I've made the experience in the past that too restrictive settings are more a > loss than a win. > > So I think we may go with a more open-minded and easy-to-understand rule. > > Current cvs should be open to every LEAF developers who asks for write > permission - assuming everyone is aware of the responsibility having write > permissions. > > A contrib section should be added with write permissions for everyone who has > been added as LEAF developer. > > Sounds easy and effetive to me :) > > kp Hi kp, I like to keep things simple so sure, let's go with what you propose. In terms of write access there would be no difference between my "core" and "mainstream" anyway. (Only difference would have been the level of support and testing, and the intent to widen the development team.) dMb -- Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] Request to Delete Directories from CVS
Hi, Two directories are no longer required in CVS: - src/bering-uclibc4/buildtool/image/Bering-uClibc-isolinux-std - src/bering-uclibc4/buildtool/image/Bering-uClibc-syslinux-std These are redundant because they do not match the revised naming convention for Bering-uClibc 4.x disk image templates. Is somebody with admin privileges able to delete these from the CVS repository? I have already "deleted" the contents. Thanks! davidMbrooke -- Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
