Brian McCallister wrote:
Erg, just tagged, umh. We should have all fixes for a release in before we vote on that release, I think.
yep, this will be the preferable procedure to build a release. But sometimes it is needed to check in some "last-minute" files (I know it's evil and other will say "this have to wait till next release", but nobody is perfect ;-)) or to say "stop I found an critical issue while last testing".
Thus before the release build starts a "release build at 20:00 pm today"-post to the dev-list will be helpful.
regards, Armin
-Brian
On Apr 2, 2005, at 12:02 PM, Armin Waibel wrote:
Hi Brian,
when will you start with the 1.0.3 release build?
I have one open issue (handling DCollection add/remove action). Currently I'm working on that stuff and I wish to fix it today.
regards, Armin
Martin Kal�n wrote:
Armin Waibel wrote:
call me crazy, but I suggest to make a OJB 1.0.3 bug fix release as soon as possible.
Critical bug = release as fast as possible IMO. I don't think we should call it 1.0.2sp1 or just replace the binary 1.0.2 that was actually downloadable for a while (the last one is a _horrible_ support-scenario). For me a service-pack, patch-set, hotfix or similar is a small binary package you drop "next to" the relase and not a full release-drop. My suggestion is 1.0.2a or 1.0.3 with clear release notes ("this is a bug fix release"?). Since OJB has no history of lettered versioning, 1.0.3 seems more consistent. Some other thoughts summarizing my view on recent release discussions (given as hypothetical voting standpoints): +1 for normal release-cycle on a, say, monthly basis (I'm not picky with the exact cycle, 3-6 weeks is OK IMO.) -1 for pushing site only on release (let's push it more often!) -0 for holding off release beacuse of tutorial or site-changes +1 for scheduled code-freeze or vote on binaries Regards, Martin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
