[Squeakfoundation]re: Outstanding 3.4 bugs?
danielv at netvision.net.il
Sat Mar 1 02:36:15 CET 2003
I agree this is the most important bug that's up for discussion about
3.4. I'm not sure it's worse than the 3.2 bug we're trying to solve
(public release doesn't include SM).
Suggestion - make 3.5 a very short release, consisting mainly of getting
as many fixes in as we can, and giving them a proper testing. It's an
opportunity for us Guides to warm up at doing the whole process
ourselves. I'm talking about a time scale of 1 month total - 2 weeks
alpha, 1 week beta, 1 week gamma, release. We start with specific, very
doable goals (maybe even decide in advance a prioritized list of fixes
we want to get in, not trying to catch up with everything that's up for
harvesting), and basically spill them all into the update stream on day
one, with the rest of the time for integration. Fixes that aren't ready
for integration (meaning, posted tested, and reviewed by someone) by the
end of week 1 will wait for 3.6.
Doug, guys, do you think this is reasonable? desirable?
Bert Freudenberg <bert at isg.cs.uni-magdeburg.de> wrote:
> Am Freitag, 28.02.03 um 02:01 Uhr schrieb Doug Way:
> > Craig Latta wrote:
> >> Hi Ned--
> >>> Are we going to do anything about them?
> >> I think we should address them in 3.5, not 3.4. In the
> >> absence of other
> >> open issues, I think we should release 3.4.
> > I was going to agree with Craig here, these bugs alone don't seem
> > serious
> > enough to postpone the 3.4 release.
> Are you going to include the other things that already have fixes?
> The "release" will be the one newbies use. They might not know how to
> update, or even if they do, they might hesitate to do so (it is
> somewhat scary to change your tires while running at 100 mph, isn't
> For example, I consider project publishing to be extremely important
> for newbies and it has a bug we ran into, which fortunately was fixed
> by Nishihara Satoshi
> (http://groups.yahoo.com/group/squeak/message/54616). I tried with
> 3.4gammaOne and the fix is not in there.
> -- Bert
> Squeakfoundation mailing list
> Squeakfoundation at lists.squeakfoundation.org
More information about the Squeakfoundation