Hm -- a new release would be great except... I've started new feature work in trunk/ for supporting partial data sets; this work isn't baked / frozen yet. Some options:
#1) branch, remove the partial data set support, and ship 1.0.2 #2) ship partial data set support as-is in 1.0.2 #3) finish partial data set support and then ship 1.0.2 Thoughts? Eddie On 10/5/06, Ken Tam <[EMAIL PROTECTED]> wrote:
+1 for a 1.0.2 patch release On 10/2/06, Rich Feit <[EMAIL PROTECTED]> wrote: > Agreed -- seems like 1.0.2 to me... > Rich > > Chad Schoettger wrote: > > It seems like a patch release to me. We've fixed a lot of bugs -- I > > know that in the controls area there have been a number of bugs fixed > > which were found by users using Beehive from within an IDE (many of > > them APT related). Also bugs releated to security and deadlocks have > > been addressed as well. > > > > I think it would be a good thing to get these fixes into a patch > > release at this time. > > > > - Chad > > > > On 9/28/06, Carlin Rogers <[EMAIL PROTECTED]> wrote: > >> I was wondering about the scheduling of the next beehive release. > >> There's been more than 65 bugs and improvements fixed along with a few > >> smaller new features. Some of these seem like good improvements on > >> 1.0.1 and worth getting out to the user community. This includes > >> things like a security fix and some page flow deadlock fixes as well. > >> > >> What are the thoughts on whether this would be a patch release (1.0.2) > >> or a point release (1.1)? Just curious what folks where thinking and > >> getting a discussion started. > >> > >> Kind regards, > >> Carlin > >> > > >
