You're correct. We should create the appropriate tag, although I suppose it
could also be done ex post facto providing that the revision number is
known.
It's hard for me to comment on the documentation, because I'm not really
sure what's being discussed. In general, I'd say I'm more of a fan of
getting M3 out there and following up with a faster M4.
As it stands, M3 probably won't actually get released for another week,
given the time to build assemblies, test, and vote. Michael had expressed
concern last time about not being able to test during the week, so it'd
likely get pushed out until after the weekend.
Granted, there's no huge rush, but as I said, I'd like to start doing more
frequent releases.
-- KevinOn 1/20/08 11:40 AM, "Andrus Adamchik" <andru..bjectstyle.org> wrote:
> > On Jan 19, 2008, at 12:22 AM, Kevin Menard wrote: > >> I think I'm going to test and build the >> artifacts over the weekend. > > Folks, should we create a release tag at this point? Otherwise ongoing > trunk commits would render meaningless any testing being done. > > Or let me rephrase - what else we need to do before we can create a tag? > > I just thought of one remaining task - switching the docs to use Ari's > shell script that scrapes them from the website instead of Confluence. > Or we can leave that for M4 and now update the docs via the old > mechanism before we tag. > > Andrus
This archive was generated by hypermail 2.0.0 : Sun Jan 20 2008 - 11:49:58 EST