RE: [Zope-dev] ACTION: 2.6 project status updates...
> > The appointed time is upon us :) We'd like to shoot for a > > 2.6 alpha 1 release at the beginning of next week (around > > the 10th). > > Eeek - six days before a hard deadline is less notice than I > would have liked. What?! It's a month past the "hard deadline" I gave at the beginning! :^) http://lists.zope.org/pipermail/zope-dev/2002-March/015587.html > All my items are code complete. They all have documention > *somewhere*, but for > some the documentation hasnt been merged into *all* the > appropriate places. I > definitely wont have time to do that before the alpha1 deadline. That's ok, so long as it won't be a problem to get that done in the next 2 weeks. > There are a number of items for which people have committed, but are now > marked as "deferred". Its a PITA that people couldnt have retracted the > commitment sooner. In particular, I would have been keen to take over the > HTTP_X_FORWARDED_FOR proposal. but not before the 10th. I fully expect that this first community-driven release cycle will teach us a lot. For one, I think that there were way too many proposals on the 2.6 plan. For the next rev, we need to refine the process to try to keep the scope tighter and probably also refine the commitment process so that we know the real status of things sooner. Brian Lloyd[EMAIL PROTECTED] V.P. Engineering 540.361.1716 Zope Corporation http://www.zope.com ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] ACTION: 2.6 project status updates...
I am quite positive that when you put __refresh_module__ = 0 into your module it will not be refreshed. Stefan --On Freitag, 07. Juni 2002 21:37 +1000 Anthony Baxter <[EMAIL PROTECTED]> wrote: > > I haven't yet finished of the CallProfiler bits, but it's a long weekend > here, and I plan to attack and finish it over this weekend. I've had more > of a go at the refresh problem, and I think I'll just make sure there's no > refresh.txt for now :( > -- BLOWFISH, n. - Preference for beef. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] ACTION: 2.6 project status updates...
I haven't yet finished of the CallProfiler bits, but it's a long weekend here, and I plan to attack and finish it over this weekend. I've had more of a go at the refresh problem, and I think I'll just make sure there's no refresh.txt for now :( Anthony -- Anthony Baxter <[EMAIL PROTECTED]> It's never too late to have a happy childhood. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] ACTION: 2.6 project status updates...
On Tuesday 04 Jun 2002 3:56 pm, Brian Lloyd wrote: > Hi all - > > The appointed time is upon us :) We'd like to shoot for a > 2.6 alpha 1 release at the beginning of next week (around > the 10th). Eeek - six days before a hard deadline is less notice than I would have liked. > ...but there are a number of items that we need to clarify > the status of. There are a couple of "99% complete" notes, > etc. All my items are code complete. They all have documention *somewhere*, but for some the documentation hasnt been merged into *all* the appropriate places. I definitely wont have time to do that before the alpha1 deadline. There are a number of items for which people have committed, but are now marked as "deferred". Its a PITA that people couldnt have retracted the commitment sooner. In particular, I would have been keen to take over the HTTP_X_FORWARDED_FOR proposal. but not before the 10th. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] ACTION: 2.6 project status updates...
Hi all - The appointed time is upon us :) We'd like to shoot for a 2.6 alpha 1 release at the beginning of next week (around the 10th). I updated the 2.6 proposed feature page this morning: http://dev.zope.org/Wikis/DevSite/Projects/Zope2.6/ProposedFeatures ...but there are a number of items that we need to clarify the status of. There are a couple of "99% complete" notes, etc. For everyone who is on the hook for a 2.6 feature that is not marked "Complete" on the list, I'd like to get a status update that includes: - whether the work _and_ docs are done - if not, whether you will be able to do them by Fri. - whether your branch is merged. Note that "Complete" on the feature page means that you have finished both the code and docs, and have merged your working branch to the HEAD (and run and passed the unit tests). If something is marked complete that isn't really, let me know that as well! Silence is consent for me to move your incomplete item to the deferred items section, so please drop me a status update even if its just to say "I still want to do it, but I don't think I can make the deadline". Note that its OK if you won't be able to get done in time - that comes with the territory. I'll add anything that doesn't make the deadline to the 2.7 plan, assuming the volunteers are still actively trying to work on it. FYI, I expect that the main focus of Zope 2.7 will be updating the supported platform to Python 2.2. My best guestimate at timing at this point is early-to-mid Q4. Thanks all! Brian Lloyd[EMAIL PROTECTED] V.P. Engineering 540.361.1716 Zope Corporation http://www.zope.com ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
