Great; I'll see if I've got the right permissions to add the notice
to dist/incubator and will add the appropriate link for our subsequent
nightlies and releases.
Probably worth clarifying when those links should be created
(nightlies, releases, etc).
Thanks for the update.
Eddie
On
Eddie ONeil wrote:
> > - incubation notice in the directories
> by this do you mean to add the incubation notice to the
> download directories like this one?
> http://cvs.apache.org/dist/incubator/beehive/20050526
Yes. We used to have that there, although I'm noticing that projects have
gotten
-Original Message-
From: Ken Tam [mailto:[EMAIL PROTECTED]
Sent: Friday, May 27, 2005 2:09 PM
To: general@incubator.apache.org; Beehive Developers
Subject: RE: [vote] beehive v1 milestone 1 release
+1
> -Original Message-
> From: Eddie O'Neil
> Sent: Wednesday
All--
Two of the three points Noel made have been addressed; a question
about the third is below:
> - svn.rev files
These have been removed from all of the archives.
> - zip file structure
I believe that these are correct -- we'd like for the files in the
archives to be self-contained when
g, Noel, etc. are watching from general@incubator.apache.org, they
may not have seen your comments, Eddie.
- jeremiah
-Original Message-
From: Eddie O'Neil
Sent: Friday, May 27, 2005 8:42 PM
To: Beehive Developers
Subject: Re: [vote] beehive v1 milestone 1 release
One other t
, Noel, etc. are watching from general@incubator.apache.org,
they
may not have seen your comments, Eddie.
- jeremiah
-Original Message-
From: Eddie O'Neil
Sent: Friday, May 27, 2005 8:42 PM
To: Beehive Developers
Subject: Re: [vote] beehive v1 milestone 1 release
One other thi
On 5/28/05, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
> Eddie O'Neil wrote:
>
> > I'd thought that creating the installers from the branch would be
> > sufficient preparation work. :)
>
> No. Sorry, but you really can't expect people to go searching for binaries
> and assume that they are what
Eddie O'Neil wrote:
> I'd thought that creating the installers from the branch would be
> sufficient preparation work. :)
No. Sorry, but you really can't expect people to go searching for binaries
and assume that they are what you plan to release. :-)
> Those binaries are here:
> http://cvs
Eddie ONeil wrote:
> Noel, Geir, or Craig, can you confirm for everyone that we must
> pass the JSR 181 TCK before calling a release 1.0-final?
I couldn't care less, unless we were claiming compliance. From what I've
read, we cannot make that claim yet, since there is nothing with which to
claim
al.
> > >>
> > >> It seems sensible to me to be voting on going 1.0 and then when the
> TCK
> > >> is public and if Beehive can get it, then any incompatibilities
> should
> > >> be recorded as bugs. I say 'if Beehive can get it' b
Original Message-
> > > From: Eddie O'Neil
> > > Sent: Friday, May 27, 2005 8:42 PM
> > > To: Beehive Developers
> > > Subject: Re: [vote] beehive v1 milestone 1 release
> > >
> > >
> > >One other thing -- if someone (Craig, Noe
Noel--
I'd thought that creating the installers from the branch would be
sufficient preparation work. :) Those binaries are here:
http://cvs.apache.org/dist/incubator/beehive/nightlies/20050526/
Apologies for not having sent an explicit link. The only difference
between this and the a
Eddie O'Neil wrote:
> I suggest that we kick the tires of the branch at SVN change
> 178556 in beehive/branches/v1/m1 (being created now) and let
> a few more doc / sample related checkins trickle in over the
> next couple of days.
That's fine, but you can't vote on something that doesn't exist.
+1
> -Original Message-
> From: Eddie O'Neil
> Sent: Wednesday, May 25, 2005 10:02 PM
> To: Beehive Developers; general@incubator.apache.org
> Subject: [vote] beehive v1 milestone 1 release
>
> All--
>
>The blocking bugs have been dealt with and we
All--
The blocking bugs have been dealt with and we've been adding
documentation and samples furiously over the last couple of weeks.
At this point, I'd like to propose that we release a Beehive 1.0
milestone 1. The code is ready to go -- though I believe that a few
committers have some
15 matches
Mail list logo
