release
Locked
 
|
Ok, seriously. This is ridiculous.
We need to release. I'm starting to find this actually embarrassing. :) What do we need to do? Just testing/packaging/release announcement? Here's the best I can think of: I'll commit to spending half a day this weekend working on a Release Candidate. After that, I won't have any free time until mid-June. That would give the vendors and interested users fair warning and a few weeks to test, port, and report any showstoppers. Then we do a final (hopefully just repacking, probably some minor fix integration). So: a) will that plan work? b) who can help this weekend? Julian _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
I'd like to see the load order tests pass (they have been broken for a month or so; see my prior emails...).
James On May 19, 2010, at 2:18 PM, Julian Fitzell wrote: > Ok, seriously. This is ridiculous. > > We need to release. I'm starting to find this actually embarrassing. :) > > What do we need to do? Just testing/packaging/release announcement? > > Here's the best I can think of: I'll commit to spending half a day this weekend working on a Release Candidate. After that, I won't have any free time until mid-June. That would give the vendors and interested users fair warning and a few weeks to test, port, and report any showstoppers. Then we do a final (hopefully just repacking, probably some minor fix integration). > > So: > a) will that plan work? > b) who can help this weekend? > > Julian > _______________________________________________ > seaside-dev mailing list > [hidden email] > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
In reply to this post by Julian Fitzell-2
On 5/19/10 2:18 PM, Julian Fitzell wrote:
> Ok, seriously. This is ridiculous. > > We need to release. I'm starting to find this actually embarrassing. :) > > What do we need to do? Just testing/packaging/release announcement? > > Here's the best I can think of: I'll commit to spending half a day > this weekend working on a Release Candidate. After that, I won't have > any free time until mid-June. That would give the vendors and > interested users fair warning and a few weeks to test, port, and > report any showstoppers. Then we do a final (hopefully just repacking, > probably some minor fix integration). > > So: > a) will that plan work? > b) who can help this weekend? WebVelocity 1.1 - so doing it with the full release would be even better. I can do live ports to VisualWorks and contribute fixes back. Are we talking a 3.0 release, or a 3.0a6 release, or a 3.0b1 release? Michael _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
In reply to this post by jgfoster
Yes, fair enough. I've been sort of looking at the emails and hoping someone else would deal with it. :) Agreed we should have those passing. They'll undoubtedly end up biting John, if nobody else.
Julian On Wed, May 19, 2010 at 10:23 PM, James Foster <[hidden email]> wrote: I'd like to see the load order tests pass (they have been broken for a month or so; see my prior emails...). _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
In reply to this post by Michael Lucas-Smith-3
On Wed, May 19, 2010 at 10:31 PM, Michael Lucas-Smith <[hidden email]> wrote:
I think consensus is we're talking a 3.0 (RC, I'm suggesting). We need to shorten our cycles and reduce the friction to releasing. We don't have the manpower to ensure a prefectly bug-free release anyway so all these release levels are a bit pointless. It felt necessary given the degree of change between 2.8 and 3.0 but given that people are using the current alpha in production already, there's not reason to add 6 months and several more releases into that process. We'll just release a 3.0.1 with bugfixes. And then we need to agree on one or two significant milestones to mark 3.1 but that's a topic for another day. Julian _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
2010/5/19 Julian Fitzell <[hidden email]>:
> On Wed, May 19, 2010 at 10:31 PM, Michael Lucas-Smith > <[hidden email]> wrote: >> >> On 5/19/10 2:18 PM, Julian Fitzell wrote: >>> >>> Ok, seriously. This is ridiculous. >>> >>> We need to release. I'm starting to find this actually embarrassing. :) >>> >>> What do we need to do? Just testing/packaging/release announcement? >>> >>> Here's the best I can think of: I'll commit to spending half a day this >>> weekend working on a Release Candidate. After that, I won't have any free >>> time until mid-June. That would give the vendors and interested users fair >>> warning and a few weeks to test, port, and report any showstoppers. Then we >>> do a final (hopefully just repacking, probably some minor fix integration). >>> >>> So: >>> a) will that plan work? >>> b) who can help this weekend? >> >> I'll help. I'm close to integrating in to VisualWorks 7.7.1 and >> WebVelocity 1.1 - so doing it with the full release would be even better. >> I can do live ports to VisualWorks and contribute fixes back. >> >> Are we talking a 3.0 release, or a 3.0a6 release, or a 3.0b1 release? > > I think consensus is we're talking a 3.0 (RC, I'm suggesting). > > We need to shorten our cycles and reduce the friction to releasing. We don't > have the manpower to ensure a prefectly bug-free release anyway so all these > release levels are a bit pointless. It felt necessary given the degree of > change between 2.8 and 3.0 but given that people are using the current alpha > in production already, there's not reason to add 6 months and several more > releases into that process. > > We'll just release a 3.0.1 with bugfixes. > > And then we need to agree on one or two significant milestones to mark 3.1 > but that's a topic for another day. +1 Cheers Philippe _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
«
Return to Seaside Development
|
1 view|%1 views
| Free forum by Nabble | Edit this page |