How will we make sure that repacked bundle has not been corrupted?
2007/6/29, Alexey Petrenko <[EMAIL PROTECTED]>:
I agree to not include ReleaseNotes if it does not ready yet. But we need to start preparing release notes a little bit earlier next times. :) According to readme.txt for M2... At least we need to remove doc directory mentioning from it. SY, Alexey 2007/6/29, Mikhail Loenko <[EMAIL PROTECTED]>: > I think they are not yet ready. And we agreed to have fixed schedule. > Can we update them in M3? :) > > Thanks, > Mikhail > > 2007/6/29, Alexey Petrenko <[EMAIL PROTECTED]>: > > Just not forget to update readme.txt and ReleaseNotes.html. > > Everything else is looks ok for me. > > > > SY, Alexey > > > > 2007/6/29, Mikhail Loenko <[EMAIL PROTECTED]>: > > > So far the following suites and scenarios either passed or had no > > > unexpected failures or regressions: > > > > > > Windows 32: > > > Classlib (HUT), EUT, Functional, GUT, JDKTools, Reliability, Stress, > > > TPTP, and VTSVM suites > > > Ant, Axis, Dacapo, EHWA, Jetty, SciMark, Struts, and Tomcat scenarios > > > > > > EGAx48 has been running without problems so far > > > > > > Linux 32: > > > Classlib (HUT), Functional, GUT, JDKTools, > > > Ant, Axis, Dacapo, EHWA, Jetty, Scimark, Struts > > > > > > No other results are vailable so far. > > > > > > I suggest that [if we pass EGAx48?] we announce r551077 as M2 on two > > > platforms: win32 and linux32. > > > > > > Comments? Known blockers? TODOs? > > > > > > Thanks, > > > Mikhail > > > > > >
