Re: [vos-d] what to do for 0.23?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You're right, doing a prerelease is a good solution. Building the Windows installer is probably the easist part. It has only changed slightly from the 0.21 release, and so it's mostly just a matter of hitting "build". Unless of course I decide to switch from NSIS to WiX or something that produces MSI files. The Debian installer should be a bit less of a pain than it has been in the past, simply because the turnaround time to build and test a package is much, much shorter on my new dev box. I have things configured here so I should be able to build both ia32 and amd64 packages. It's mostly the fact that the whole entire process is the sum of many little things, each of which don't take up that much time but as a whole can take up weeks if it's just me doing it. I'd certainly appreciate some help this time around :-) On Sat, 9 Jul 2005, Reed Hedges wrote: 1. release source code "release candidate" first, 2. then release source code 0.23, 3. then start work on the manual, and release the Windows installer a few days later, 4. then finish the manual, release it, 5. then start on the Linux installers for release a week or so later. That way both developers and most non-developer users will be able to get started using the release first, and critical bugfixes can go in before spending lots of time on polishing the manual and working on the linux binary packages. reed ___ vos-d mailing list [email protected] http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d [ Peter Amstutz ][ [EMAIL PROTECTED] ][ [EMAIL PROTECTED] ] [Lead Programmer][Interreality Project][Virtual Reality for the Internet] [ VOS: Next Generation Internet Communication][ http://interreality.org ] [ http://interreality.org/~tetron ][ pgpkey: pgpkeys.mit.edu 18C21DF7 ] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC1dy4aeHUyhjCHfcRAmlmAJ9/2LHzE7bfDzVtsG/Y1gDDEaCJlACggOSG eogS2kVSk5jp1N+SA4Vzuhg= =v4qy -END PGP SIGNATURE- ___ vos-d mailing list [email protected] http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
Re: [vos-d] what to do for 0.23?
Hi developers, On Sat, 9 Jul 2005, Reed Hedges wrote: That way both developers and most non-developer users will be able to get started using the release first, and critical bugfixes can go in before spending lots of time on polishing the manual and working on the linux binary packages. sounds clever also I think to have a main topic solved on every release is a good idea, thus I can't wait to see how the vrml will work on next release ;) Wouldnt it mean that vos is a nice vrml application then? (even if I understand it's only plain geometry, no javascripting) A great perspective if vos has sometime cristal-zilla inside, then we could also forget the shitty browser/plugin stress and surf the web 3d as we ever wanted. Have you checked http://www.spatialknowledge.com/projects/clara/ buggy, but a nice try, sadly death since two jears I think CU hermetic ___ vos-d mailing list [email protected] http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
Re: [vos-d] what to do for 0.23?
1. release source code "release candidate" first, 2. then release source code 0.23, 3. then start work on the manual, and release the Windows installer a few days later, 4. then finish the manual, release it, 5. then start on the Linux installers for release a week or so later. Also, if Peter is making the Windows installer, others of us can simultaneously work on the manual, and Linux binary packages. We have a Debian setup that just needs to be updated for 0.23, but if anyone is able to make RPMs, Fedora packages, Gentoo packages, etc. that would be great. reed ___ vos-d mailing list [email protected] http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
Re: [vos-d] what to do for 0.23?
On Jul 9, 2005, at 2:44 AM, Peter Amstutz wrote: The thing is, the full release process is quite time consuming. It involves updating documentation, building binary packages, and lots of other stuff. I wonder if, for 0.23, it would be alright to skip some of that to get the release out faster. So 0.23 would probably basically be just a source tarball and a Windows installer for the binary. Why not 1. release source code "release candidate" first, 2. then release source code 0.23, 3. then start work on the manual, and release the Windows installer a few days later, 4. then finish the manual, release it, 5. then start on the Linux installers for release a week or so later. That way both developers and most non-developer users will be able to get started using the release first, and critical bugfixes can go in before spending lots of time on polishing the manual and working on the linux binary packages. reed ___ vos-d mailing list [email protected] http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
