Exactly, even if we're lazy, it should take 1h15 for 3 of us to do that, we could take a whole day if necessary... one person can even do all of that (apart from Mac, where Jerome is needed and I know Jerome well enough to say he'll be the first one to act!) and on IRC it is so much easier/faster to communicate.... yes, you are right, if we do it this way, if the releases are now that easy to do we should create an RC every time we want to.. we could even release an RC every 2 or 3 bug fixes (more like an RC every 2 weeks)... RC1 is already 1 month old and the SVN version is so much more improved... maybe we should already have an RC2 :P btw, Phil, you said we need code modifs for AP package to be universal, what are they? can you do that or do you have a good link or a quick howto you can write ? thanks!
and finally, my PC is still dead so I can't do much, but someone REALLY has to check the commits ONE BY ONE (I know, it's huge), and port every 0.96-related change into the 0.96 branch!!! and see if anything was done in the branch and not in the trunk/ too... in the end, I want to do a diff between branch and trunk/ and look line by line in the diff and see ONLY differences that are "oh yeah, this should not be ported to the branch" and release number in the configure file... Once it's done, DO the diff yourself, THEN answer this ML to say "ok, branch is secure"! p.s.: a tip, instead of reading every commit, it might be easier to do a diff, then every modified line that doesn't seem to belong to only one branch of the two, do a 'svn blame' on it to see in which revision it came from, then read that commit and if necessary 'svn merge' that commit, or if there are many changes in it and not all should be in the branch, then manually patch the branch and commit it.. do the diff again and repeat until the diff is satisfactory... p.s.2: he or she who decides to do that task, please advice us by email then proceed, just to make sure only one people do it and we can avoid problems + this way if noone answers, I will have to yell and force someone to do it :p take care KaKaRoTo On Wed, Jul 12, 2006 at 11:16:46PM -0400, J?r?me Gagnon-Voyer wrote: > I think you're right. It's really fast, we just take too much time. > Of course there's always the last minute problem but still...it's > really fast. 0.95 took a long time because we decided to re-build the > website at the same time. > > If by example we find something very stable...and we decide, "next > day, in the evening (ET) try to be on IRC so we can make everything", > with the help of a lot of people on IRC it's really fast. > > (Yes the mac package is fast to do, I was just lazy for the RC1) > > J?r?me > Courriel: [EMAIL PROTECTED] > MSN Messenger: [EMAIL PROTECTED] > iChat & AIM: [EMAIL PROTECTED] > Skype: germinator5000 > > > Le 12 juillet 2006 ? 22:54, Youness Alaoui a ?crit : > > >Humm.. but why in the world would you put it as active ? > >also, don't forget, what packagers you want to notify ? in theory, it > >would go as : > >10:00 : decide to release > >10:15 : tag the release, export and create tarball > >10:30 : someone on windows launches a script that creates the > >windows installer > >10:45 : upload to SF and create the release version > >10:55 : 'makeinstaller' and create the AP release > >11:00 : Jerome finished creating the mac binaries (he had 45 minutes > >already) > >11:05 : we have the AP, windows and Mac binaries uploaded, we set the > >release as active > >11:15 : we finished setting up the news page and updating everything > >that has to be updated... > > > >you see, we need 1h15 to do all that, there is no 'announce it to > >packagers', anyone can do the windows binary in a few seconds, > >especially if we switch to the nsis installer which works with a > >script, > >so is a lot easier to configure than bitrock... > >for mac, Jerome usually has it all prepared so he just updates a > >folder > >and a single click makes it into a .dmg (correct me if I'm wrong) and > >for autopackage, the same, one command and we're done... > >no hassle... > >no wait... > > > >KKRT > > > >On Wed, Jul 12, 2006 at 09:17:24PM +0200, Sander Hoentjen wrote: > >>On Wed, 2006-07-12 at 10:35 -0400, Youness Alaoui wrote: > >>>On Wed, Jul 12, 2006 at 08:16:55AM +0200, Harry Vennik wrote: > >>>>I agree 100%. We just shouldn't do this anymore. We should just > >>>>offer the > >>>>source package and the Windows and Mac binary packages, and the > >>>>autopackage > >>>>for Linux. The packages for the various distros will be done by > >>>>the distros, > >>>>and if the distro doesn't include amsn, some volunteer may also > >>>>create it > >>>>after the official release date, we should not wait for it. > >>>>Maybe we should > >>>>not even wait for any binary packages at all, and announce a > >>>>release like: > >>>> > >>>>Release .... is out! You can now download the source package > >>>>from ... and as > >>>>soon as possible binary packages will also be published for Mac, > >>>>Windows and > >>>>Linux (generic autopackage). Linux distribution-specific > >>>>packages are not > >>>>created by us, but many distros include aMSN themselves, and > >>>>will soon > >>>>provide a package of this new release. > >>>> > >>> > >>>i would disagree.. as much as I want to shorten the trouble for > >>>us, I don't want to make it more difficult for > >>>our users either... the windows/mac/AP packages MUST be available > >>>before announcing the release... > >>>howtos for other distros should also be available. > >>> > >>>KKRT > >> > >>Then what about this: > >> > >>step 1: We tag, create tarball, upload tarball, put it in file > >>release > >>as active (not hidden), (we notify packagers?) > >>step 2: We create binary packages and add them to the release > >>step 3: we change the website, announce the release > >>step 4: ??? > >>step 5: profit! > >> > >> > >> > >>--------------------------------------------------------------------- > >>---- > >>Using Tomcat but need to do more? Need to support web services, > >>security? > >>Get stuff done quickly with pre-integrated technology to make your > >>job easier > >>Download IBM WebSphere Application Server v.1.0.1 based on Apache > >>Geronimo > >>http://sel.as-us.falkag.net/sel? > >>cmd=lnk&kid=120709&bid=263057&dat=121642 > >>_______________________________________________ > >>Amsn-devel mailing list > >>[email protected] > >>https://lists.sourceforge.net/lists/listinfo/amsn-devel > > > > > >---------------------------------------------------------------------- > >--- > >Using Tomcat but need to do more? Need to support web services, > >security? > >Get stuff done quickly with pre-integrated technology to make your > >job easier > >Download IBM WebSphere Application Server v.1.0.1 based on Apache > >Geronimo > >http://sel.as-us.falkag.net/sel? > >cmd=lnk&kid=120709&bid=263057&dat=121642 > >_______________________________________________ > >Amsn-devel mailing list > >[email protected] > >https://lists.sourceforge.net/lists/listinfo/amsn-devel > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Amsn-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/amsn-devel ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Amsn-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amsn-devel
