Yes, release 1.2 final now, but before uploading it to sf.net please give us 2-3 days to test what you bundle as 1.2 final :-)
Ara. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:xdoclet-devel- > [EMAIL PROTECTED] On Behalf Of Andrew Stevens > Sent: Sunday, November 09, 2003 4:59 AM > To: [EMAIL PROTECTED] > Subject: RE: [Xdoclet-devel] 1.2 Final release? > > On Sat, 2003-11-08 at 23:27, Craig Walls wrote: > > I do not mean to rush anyone, but... > > > > It has been a month now and we still don't have a new build of XDoclet > 1.2. > > Sorry about that; I've been busy again, both with work and with > preparing for a more important release - my wife & I are expecting our > first child some time in the next few weeks :-) > > > As I stated before, I'd prefer to cut a final build and fix any issues > in a > > follow-up point release, but I'm also okay with just cutting another > beta > > build. Either way, I think it's time we do a cut of the newest stuff. > > Agreed. Let's get 1.2 out the door. There's still plenty of open > issues in JIRA, but we can always do a 1.2.1 with any fixes for those > (though possibly not till after a beta release of 2.0?) > > I just tried a clean build of xdoclet in isolation and it fails ("Can't > resolve symbol" errors on XJavadoc classes). However, I notice the > build properties specify xjavadoc 1.0.1, so I guess something's changed > since that version (Aslak, do you know if that's the case?) My "normal" > build environment works, but that picks up the latest XJD version as > it's able to find the sources at the same level. So we'll need to do a > xjavadoc 1.0.2 release (it's not really a good idea to have xdoclet > release versions dependent on xjavadoc snapshot versions...) > > > Again...let me know what I can do to help. If there are any issues in > JIRA > > that you think are a *must* to have fixed before 1.2 is final, point me > at > > them and I'll see what I can do. > > Looking through the 9 "blocker" issues in JIRA, and the 24 targetted at > 1.2, about the only one that I'd say was a "must have" is the one about > including xjavadoc's jar in the distribution files, to avoid people > having to download it themselves again (and I think that's the case now > anyway). Unless any of the other developers think there's any other > open issues which should hold up the release? > > Seeing as it's past 1am, I'm not about to start building things right > now :-) I'll take a stab at it tomorrow, though. > > In the meantime, if you're after something relatively quick to do, I > reckon anything that improves the documentation is a good move: there's > a handful of Documentation issues in JIRA; I think various tag handlers > are missing @doc.tag javadocs, leading to omissions in the template tag > documentation; there's probably still missing xtags entries to be found; > or just improve (or add) javadocs on things so the task/subtask > documentation doesn't have so many blanks appearing. Plus, any changes > to those aren't likely to break anything vital while we're doing the > release... > > > Andrew. > > > > ------------------------------------------------------- > This SF.Net email sponsored by: ApacheCon 2003, > 16-19 November in Las Vegas. Learn firsthand the latest > developments in Apache, PHP, Perl, XML, Java, MySQL, > WebDAV, and more! http://www.apachecon.com/ > _______________________________________________ > xdoclet-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-devel ------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
