Re: [Zope-dev] SVN: zope.bugchecker/trunk/src/zope/bugchecker/bugchecker.py Get clickable URLs in the output.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sidnei da Silva wrote:
+link = ('https://bugs.launchpad.net/%s/+bug/%s'
+% (self.project_name, bug_id))
You can actually link to the bug having an id only, by using
'http://launchpad.net/bugs/bug-id'. It's fine since you have a
project_name here to use it, but a nice tip anyway.
Cool, good to know.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkvGxzEACgkQ+gerLs4ltQ7+/ACdHBjg7rFWMBaGpJ2hadDXcAyL
xN0Anjn2jq1Vpzs0Hf9RPbz0sCTyDgFK
=kR7Z
-END PGP SIGNATURE-
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SVN: zope.bugchecker/trunk/src/zope/bugchecker/bugchecker.py Get clickable URLs in the output.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/15/10 09:58 , Tres Seaver wrote:
Sidnei da Silva wrote:
+link = ('https://bugs.launchpad.net/%s/+bug/%s'
+% (self.project_name, bug_id))
You can actually link to the bug having an id only, by using
'http://launchpad.net/bugs/bug-id'. It's fine since you have a
project_name here to use it, but a nice tip anyway.
That's a great tip for keeping short bug URLs in change log entries. I
was wondering about that myself.
jens
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iEYEARECAAYFAkvGyOsACgkQRAx5nvEhZLL7IwCgk6tY8F99q6zC1drLwtp4Y9jq
CGQAn3QMS4YnPEEk4mfjm64Nav40Wdjw
=bmKS
-END PGP SIGNATURE-
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] KGS 3.4.1 versions
Hello, There is a sheet with versions for KGS 3.4.1 http://spreadsheets.google.com/pub?key=tUE5Q72d4Kg1FXaacCA3EKQoutput=html Anyone for/against those versions? The open questions that remain: * What about pytz 2010g? * Which lxml version to take? 1.3.6? * What about zope.app.container 3.6.2? * Would be nice to have zope.testbrowser 3.5.1 Comments are welcome. -- Best regards, Adam GROSZER mailto:agros...@gmail.com -- Quote of the day: The crash of the whole solar and stellar systems could only kill you once. - Thomas Carlyle ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 10 OK, 4 Failed
Summary of messages to the zope-tests list. Period Wed Apr 14 12:00:00 2010 UTC to Thu Apr 15 12:00:00 2010 UTC. There were 14 messages: 6 from Zope Tests, 7 from ccomb at free.fr, 1 from ct at gocept.com. Test failures - Subject: FAILED: Repository policy check found errors in 669 projects From: ct at gocept.com Date: Wed Apr 14 21:13:43 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013957.html Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 32bit From: ccomb at free.fr Date: Wed Apr 14 23:56:47 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013968.html Subject: FAILED : ZTK 1.0dev / Python2.5.2 Linux 32bit From: ccomb at free.fr Date: Wed Apr 14 23:57:58 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013969.html Subject: FAILED : ZTK 1.0dev / Python2.6.4 Linux 32bit From: ccomb at free.fr Date: Wed Apr 14 23:57:58 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013970.html Tests passed OK --- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Wed Apr 14 21:43:31 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013958.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Wed Apr 14 21:45:31 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013959.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Wed Apr 14 21:47:31 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013960.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Wed Apr 14 21:49:32 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013961.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Wed Apr 14 21:51:32 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013962.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Wed Apr 14 21:53:32 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013963.html Subject: OK : BlueBream template / Python2.4.6 32bit linux From: ccomb at free.fr Date: Wed Apr 14 22:00:44 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013964.html Subject: OK : BlueBream template / Python2.5.2 32bit linux From: ccomb at free.fr Date: Wed Apr 14 22:00:47 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013965.html Subject: OK : BlueBream template / Python2.6.4 32bit linux From: ccomb at free.fr Date: Wed Apr 14 22:00:47 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013966.html Subject: OK : BlueBream template / Python2.7b1 32bit linux From: ccomb at free.fr Date: Wed Apr 14 22:00:48 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013967.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 10 OK, 4 Failed
On 04/15/2010 01:59 PM, Zope Tests Summarizer wrote: Summary of messages to the zope-tests list. Period Wed Apr 14 12:00:00 2010 UTC to Thu Apr 15 12:00:00 2010 UTC. There were 14 messages: 6 from Zope Tests, 7 from ccomb at free.fr, 1 from ct at gocept.com. Test failures - Subject: FAILED: Repository policy check found errors in 669 projects From: ct at gocept.com Date: Wed Apr 14 21:13:43 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013957.html Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 32bit From: ccomb at free.fr Date: Wed Apr 14 23:56:47 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013968.html Subject: FAILED : ZTK 1.0dev / Python2.5.2 Linux 32bit From: ccomb at free.fr Date: Wed Apr 14 23:57:58 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013969.html Subject: FAILED : ZTK 1.0dev / Python2.6.4 Linux 32bit From: ccomb at free.fr Date: Wed Apr 14 23:57:58 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013970.html The X-Powered-By header has gone away. Huh? -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Launchpad gardening
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (oops, I thought this went out earlier). I wanted to let the zope-dev community know a bit about what Christian Theune and I have been doing this week. We have done a fair bit of tidying for the ZTK projects on Launchpad: - - Each ZTK package is now a separate Launchpad project, under the umbrella of the 'zopetoolkit' project group: https://launchpad.net/zopetoolkit/ I did some minimal branding (the circle Z logo) across the ZTK projects; Christian updated the metadata on them, including fixing up descriptinons and adding PyPI download links. - - Each of those projects has bug tracking turned on. You can drill down into any of them from the umbrella page and click the Bugs tab at the top. You can also see an overview for the whole ZTK: https://bugs.launchpad.net/zopetoolkit - - I did a bit of Augean stable shoveling in the Zope3 tracker, moving bugs which were obviously tied to one of the ZTK projects into the appropriate project, and leaving behind a wontfix in the Zope3 project (since we're not making new Zope3 releases, we can't be fixing bugs there). I left behind about 70 bugs which are tied up with packages whcih don't yet have a real home. At this point, there are significant sets of bugs to be tackled in many of the ZTK projects: I'm hoping that having them grouped together that way will enable folks to focus on getting a number of bugs for a given project closed quickly, as in at a bug day. - - Charlie Clarke put together a script which polls Launchpad for languishing bugs for a project. I hacked on it a bit, allowing running the report against the 'zopetoolkit' project group, etc.: http://svn.zope.org/zope.bugchecker/trunk I am attaching a copy of the report for the ZTK projects. - - I requested that the Launchpad folks set up mirrored imports of the SVN trunks for all the ZTK projects (some were already being imported, some aren't yet done). Each project's branch can now be checked out using a nicely mnemonic bzr command, e.g.: $ bzr branch lp:zope.interface You can drill down to a project, and click the Branches tab to see any branches (most have only the one trunk branc). You can also see an overview of all the ZTK branches: https://code.launchpad.net/zopetoolkit I am hopeful that having the code easily branchable with a DVCS will lower the barrier to contributing at something like a bug day, for instance. Enjoy! Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvHIqEACgkQ+gerLs4ltQ5GogCfT2yDPYb3w6zsRvCWyeRt8jSe 22QAnRiaOmFy3DHvCC40t56dGhVc/1/V =3zbq -END PGP SIGNATURE- == Languishing bugs report == States included: New, Confirmed Minimum age: 30 -- zope.annotation : languishing bugs: 0 -- -- zope.applicationcontrol : languishing bugs: 0 -- -- zope.authentication : languishing bugs: 0 -- -- zope.browser: languishing bugs: 0 -- -- zope.browsermenu: languishing bugs: 0 -- -- zope.browserpage: languishing bugs: 0 -- -- zope.browserresource: languishing bugs: 0 -- -- zope.cachedescriptors : languishing bugs: 0 --
Re: [Zope-dev] Launchpad gardening
Excellent work! On 4/15/10 16:28 , Tres Seaver wrote: - - Charlie Clarke put together a script which polls Launchpad for languishing bugs for a project. I hacked on it a bit, allowing running the report against the 'zopetoolkit' project group, etc.: http://svn.zope.org/zope.bugchecker/trunk I am attaching a copy of the report for the ZTK projects. How is 'languishing' determined? I would expect a bug which has seen no activity for a year to be marked as such, but https://bugs.launchpad.net/zope3/+bug/430662 is not on the list. Is that because moving it from Zope3 to zope.tal counted as activity? Wichert. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Launchpad gardening
On Thu, Apr 15, 2010 at 10:28 AM, Tres Seaver tsea...@palladion.com wrote: I wanted to let the zope-dev community know a bit about what Christian Theune and I have been doing this week. We have done a fair bit of tidying for the ZTK projects on Launchpad: ... Enjoy! Thank you very much! Jim -- Jim Fulton ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Poposal: Split zope.app.preference into two packages
Hi, I propose to split zope.app.preference into two separate packages: - zope.preference -- which contains the ZMI independent stuff, - zope.app.preference -- which contains the ZMI stuff and depends on zope.preference. By ZMI stuff I mean the views and page templates which depend on ZMI to be displayed. As there are no tests for these views I'll write some testbrowser tests first. Later on there might be a package z3c.preference which integrates zope.preference using z3c.pagelet. Risks: I do not see any. Any objections, hints, …? Yours sincerely, -- Michael Howitz · m...@gocept.com · software developer gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 8 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Launchpad gardening
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Leonardo Rochael Almeida wrote: this is really nice. Observations below Thanks! I'm CC'ing the list in case your question is in somebody else's mind. On Thu, Apr 15, 2010 at 11:28, Tres Seaver tsea...@palladion.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [...] - - I requested that the Launchpad folks set up mirrored imports of the SVN trunks for all the ZTK projects (some were already being imported, some aren't yet done). Each project's branch can now be checked out using a nicely mnemonic bzr command, e.g.: $ bzr branch lp:zope.interface You can drill down to a project, and click the Branches tab to see any branches (most have only the one trunk branc). You can also see an overview of all the ZTK branches: https://code.launchpad.net/zopetoolkit I am hopeful that having the code easily branchable with a DVCS will lower the barrier to contributing at something like a bug day, for instance. How does this impact committing? Can we use bzr to commit back to lp and it gets reflected back to svn.zope.org? Nope, the bzr branches are one-way mirrors, like in an interrogation room in a police procedural TV show. (Hmm, I wonder: could this approoach be giving the ZTK the third degree'?) How does access-control work in this case? Anybody with a Launchpad account can push a branch with a fix or feature change back to Launchpad. E.g., assuming that I want to work on fixing bug #12345, which maybe even has a partial suggested fix (but no full patch). First, I branch the code, run the buildout, and run the tests to get a baseline:: $ bzr clone lp:zope.interface $ cd zope.interface $ /opt/Python-2.6.5/bin/python bootstrap.py ... $ bin/buildout ... $ bin/test ... Then I add tests for the bug, and make them pass (lather, rinse, repeat):: $ gvim src/zope/interface # fix a bug, add a test, etc. $ bin/test ... When I'm satisfied with the fix, I commit my changes to the local branch, creating a link to the bug:: $ gvim CHANGES.txt # note the fix $ bzr commit -m Fix LP #12345. --fixes lp:12345 Finally, I push my branch up to Launchpad:: $ bzr push lp:~tseaver/zope.interface/lp_12345 I can also create and e-mail a fully-annotated patch bundle:: $ bzr send --message=Cool feature --mail-to=maintai...@example.com or save it as a file, e.g. to upload to the bug:: $ bzr send --message=Cool feature \ -o /tmp/repoze.who-my_cool_feature.patch Similar development patterns would apply with hg or git, only we don't have mirrors set up for them (yet, at least). If not, can we commit straight into svn.zope.org with bzr-svn? I have been working directly against svn.zope.org with bzr (and git, and hg, but not as much) for the past few weeks. Given a recent enough version of each DVCS (and for bzr and hg, the svn plugin), it works pretty much just like using svn. E.g.: $ bzr co svn+ssh://svn.zope.org/repos/main/zope.interface/trunk \ zope.interface One immediate win for this (works with git and hg, too) is the patchwork version of the log command, which interleaves the patch for each commit with the commit metadata: $ bzr log -p A branch made using 'bzr checkout' is bound to the SVN repository: commits are automatically pushed back to the master. When working in bzr, I really like the ability to batch up local commits, so I often create a local branch of the bound one, hack on it with multiple commits, and then push back to the bound branch. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvHLhAACgkQ+gerLs4ltQ5icwCgx1siQUt9ufKsNhW7i5HtBZU9 HXgAn3uuvz+Ux/zM/Ju9k12t5nthZndv =GC9h -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Launchpad gardening
On Thu, Apr 15, 2010 at 12:17 PM, Tres Seaver tsea...@palladion.com wrote: snip Finally, I push my branch up to Launchpad:: $ bzr push lp:~tseaver/zope.interface/lp_12345 Once the branch is submitted to Launchpad, it is also possible to create a Merge Proposal, which is a step up from a patch. Reviewers can see a live diff on the Merge Proposal that gets updated every time you do a new 'push'. Merge Proposals also have their own state. There's a dashboard for keeping track of pending and approved Merge Proposals, eg: https://launchpad.net/zopetoolkit/+activereviews (the same exists for users: https://launchpad.net/~sidnei/+activereviews) If you have bzrtools installed, you can use the 'bzr lp-submit' command to create a Merge Proposal from the command line, IIRC. It might seem like extra work at first, but once you get used to using Merge Proposals to track work that's pending a merge it pays off very quickly. snip A branch made using 'bzr checkout' is bound to the SVN repository: commits are automatically pushed back to the master. When working in bzr, I really like the ability to batch up local commits, so I often create a local branch of the bound one, hack on it with multiple commits, and then push back to the bound branch. That's how I work too, even with branches stored in bzr, by having a 'trunk' branch that is bound it saves you a few steps when merging work back into the main tree. For people that prefer to be really explicit, you can use 'bzr branch svn+ssh://...' instead of 'bzr checkout' to create an unbound branch by default. You can also use 'bzr bind' and 'bzr unbind' to switch between bound and unbound. -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Launchpad gardening
There's a dashboard for keeping track of pending and approved Merge Proposals, eg: https://launchpad.net/zopetoolkit/+activereviews Not very useful since it's empty. Look at the pending proposals from zc.buildout for a better example: https://edge.launchpad.net/zc.buildout/+activereviews -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Launchpad gardening
Thanks Tres and Sidnei, My questions were intended to go to the list anyway. Can we take a branch from the launchpad mirror and bind it back directly at svn+ssh://svn.zope.org/ to commit? For instance, say I'm reviewing a bugfix proposed by someone that doesn't currently have access to svn.zope.org but added a merge-proposal to lp, can I branch it, bind it to svn+ssh://svn.zope.org and then commit? Wouldn't it be nice if it was possible? Cheers, Leo On Thu, Apr 15, 2010 at 12:34, Sidnei da Silva sidnei.da.si...@gmail.com wrote: On Thu, Apr 15, 2010 at 12:17 PM, Tres Seaver tsea...@palladion.com wrote: snip Finally, I push my branch up to Launchpad:: $ bzr push lp:~tseaver/zope.interface/lp_12345 Once the branch is submitted to Launchpad, it is also possible to create a Merge Proposal, which is a step up from a patch. Reviewers can see a live diff on the Merge Proposal that gets updated every time you do a new 'push'. Merge Proposals also have their own state. There's a dashboard for keeping track of pending and approved Merge Proposals, eg: https://launchpad.net/zopetoolkit/+activereviews (the same exists for users: https://launchpad.net/~sidnei/+activereviews) If you have bzrtools installed, you can use the 'bzr lp-submit' command to create a Merge Proposal from the command line, IIRC. It might seem like extra work at first, but once you get used to using Merge Proposals to track work that's pending a merge it pays off very quickly. snip A branch made using 'bzr checkout' is bound to the SVN repository: commits are automatically pushed back to the master. When working in bzr, I really like the ability to batch up local commits, so I often create a local branch of the bound one, hack on it with multiple commits, and then push back to the bound branch. That's how I work too, even with branches stored in bzr, by having a 'trunk' branch that is bound it saves you a few steps when merging work back into the main tree. For people that prefer to be really explicit, you can use 'bzr branch svn+ssh://...' instead of 'bzr checkout' to create an unbound branch by default. You can also use 'bzr bind' and 'bzr unbind' to switch between bound and unbound. -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Minutes from this weeks meeting
Hi, here's the minutes. As I've been adventurous, I'll add a few comments: * I've started diving into the matter of how to manage items that we park/defer/postpone/wait for and thus started using an online system. (The only one I was able to find anyway.) * The output is a PDF which is currently a bit messy as I wanted to get rid of my text files that had the open issues sitting in there and thus had to add all of them to our agenda on Tuesday and then defer them. I think next week will become less noisy. * In general I can give access to stuff there to more people. I'll probably add those of you that step up for some tasks so I can mark the assignments appropriately. I hope this helps, at least I have the feeling it helps me stay organized and thus take less time in the future to write up the agendas and minutes. Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development 2010 (15).pdf Description: Adobe PDF document ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Launchpad gardening
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Leonardo Rochael Almeida wrote: Thanks Tres and Sidnei, My questions were intended to go to the list anyway. Can we take a branch from the launchpad mirror and bind it back directly at svn+ssh://svn.zope.org/ to commit? For instance, say I'm reviewing a bugfix proposed by someone that doesn't currently have access to svn.zope.org but added a merge-proposal to lp, can I branch it, bind it to svn+ssh://svn.zope.org and then commit? Wouldn't it be nice if it was possible? It is possible, at least in theory. I have tried that out on my local machine:: $ cd /tmp $ mkdir wibn $ cd wibn/ $ svnadmin create svn-repo $ svn mkdir -m Wouldn't it be nice? file:///`pwd`/svn-repo/wibn $ svn mkdir -m Wouldn't it be nice? file:///`pwd`/svn-repo/wibn/trunk $ svn co file:///`pwd`/svn-repo/wibn/trunk svn-trunk $ cat svn-trunk/nice.txt Wouldn't it be nice if we were older and we didn't have to wait so long? ^D $ svn add svn-trunk/nice.txt $ svn commit -m Sing. svn-trunk/nice.txt $ mkdir bzr-repo $ bzr init-repo bzr-repo $ cd bzr-repo/ $ bzr co file:///`cd .. pwd`/svn-repo/wibn/trunk bzr-trunk $ bzr branch bzr-trunk non-commital $ cd non-commital/ $ gvim nice.txt # add more lyrics $ bzr commit -m Sing more. $ bzr push file:///`cd ../.. pwd`/svn-repo/wibn/trunk $ cd ../../svn-trunk/ $ svn up $ cat nice.txt # see the changes I'm not quite sure how it will work for pushing to SVN from a branch made against the Launchpad mirror of SVN: there are a few more possible points of disconnection in that path. Maybe Sidnei already works this way? Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvHQRoACgkQ+gerLs4ltQ4wNACdE9SWMrx/tIxHL1C8cFvauN+w U9kAoMBt21n24BIUXW+Sf9HYU2HIVrlK =G69T -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Launchpad gardening
On Thu, Apr 15, 2010 at 12:41 PM, Leonardo Rochael Almeida leoroch...@gmail.com wrote: Thanks Tres and Sidnei, My questions were intended to go to the list anyway. Can we take a branch from the launchpad mirror and bind it back directly at svn+ssh://svn.zope.org/ to commit? For instance, say I'm reviewing a bugfix proposed by someone that doesn't currently have access to svn.zope.org but added a merge-proposal to lp, can I branch it, bind it to svn+ssh://svn.zope.org and then commit? Wouldn't it be nice if it was possible? Not sure if it would. What you really want to do is to merge the bzr branch you got from Launchpad into the 'trunk' you got from svn.zope.org, which behaves exactly as Tres described on his previous email. Pushing the branch directly without merging first would overwrite the contents of the target branch with the contents of the pushed branch. -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Launchpad gardening
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wichert Akkerman wrote: Excellent work! On 4/15/10 16:28 , Tres Seaver wrote: - - Charlie Clarke put together a script which polls Launchpad for languishing bugs for a project. I hacked on it a bit, allowing running the report against the 'zopetoolkit' project group, etc.: http://svn.zope.org/zope.bugchecker/trunk I am attaching a copy of the report for the ZTK projects. How is 'languishing' determined? I would expect a bug which has seen no activity for a year to be marked as such, but https://bugs.launchpad.net/zope3/+bug/430662 is not on the list. Is that because moving it from Zope3 to zope.tal counted as activity? The report I ran was for bugs in the 'New' or 'Confirmed' states which were older than 30 days. The check-bugs script has command-line options for tweaking those values: the defaults are actually just 'New' and 14 days. As for that bug: I would have expected it to show up against 'zope.tal', so I may not understand the launchpadlib query semantics quite correctly. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvHRMIACgkQ+gerLs4ltQ5eGgCg1qqeH+kd+VQRHPK5I0WSyJnw nL0An1Q9vlx8/hYwHKtwCri+IgXkxwcj =PYnW -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SVN: zc.buildout/branch/regebro-python3/ OK, now fails on installing zope.testing under Python 3. Good checkpoint.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lennart Regebro wrote: Log message for revision 110937: OK, now fails on installing zope.testing under Python 3. Good checkpoint. /me cheers at Lennart's trailblazing efforts. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvHRXQACgkQ+gerLs4ltQ7VFwCcCNeMSzQUR3UAWDs4v7/7Cim2 sz4An2dk1+Q/Tc5UmcrKD4CRaBgZZ3QG =/cXs -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope2: 261 languishing issues
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Here is how I got the report: $ svn co $ZSVN/zope.bugchecker/trunk bugchecker $ cd bugchecker $ /opt/Python-2.6.5/bin/python bootstrap.py ... $ bin/buildout ... $ bin/check-bugs zope2 Start your engines! Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvHRnsACgkQ+gerLs4ltQ4flgCeIFWes9aEhLA234qIqEiOP+iF hC4AoNm9q4QMK79oomdwk3k85oj59Hcy =z/jv -END PGP SIGNATURE- == Languishing bugs report == States included: New Minimum age: 14 -- zope2 : languishing bugs: 261 -- Bug #142226 in Zope 2: Zope cookies unconditionally quoted New 2002-09-13 None https://bugs.launchpad.net/zope2/+bug/142226 Bug #142410 in Zope 2: inconsistencies in the way to detect a missing attribute New 2003-01-02 None https://bugs.launchpad.net/zope2/+bug/142410 Bug #142481 in Zope 2: Improve VirtualHostMonster documentation New 2003-02-24 None https://bugs.launchpad.net/zope2/+bug/142481 Bug #142484 in Zope 2: TAL: Inconsistent slot filling with nested macros New 2003-02-27 None https://bugs.launchpad.net/zope2/+bug/142484 Bug #142501 in Zope 2: DA instances open connection too early New 2003-03-10 None https://bugs.launchpad.net/zope2/+bug/142501 Bug #142536 in Zope 2: incorrect DAV:getcontenttype for collections New 2003-04-10 None https://bugs.launchpad.net/zope2/+bug/142536 Bug #142576 in Zope 2: HEAD returns 404, GET returns 200 for the same url New 2003-05-22 None https://bugs.launchpad.net/zope2/+bug/142576 Bug #142595 in Zope 2: manage_workspace logic is buggy New 2003-06-12 None https://bugs.launchpad.net/zope2/+bug/142595 Bug #142685 in Zope 2: manage_afterClone called with wrong parameter New 2003-08-29 None https://bugs.launchpad.net/zope2/+bug/142685 Bug #142695 in Zope 2: Records with File uploads and tainted values die New 2003-09-03 None https://bugs.launchpad.net/zope2/+bug/142695 Bug #142717 in Zope 2: Cannot call manage_copyObjects from script with proxy roles New 2003-09-23 None https://bugs.launchpad.net/zope2/+bug/142717 Bug #142743 in Zope 2: ZSearchInterface: DTML renders correctly, ZPT doesn't New 2003-10-15 None https://bugs.launchpad.net/zope2/+bug/142743 Bug #142750 in Zope 2: Adding and deleting a virtual host monster to a folder which already contains one breaks virtual hosting New 2003-10-25 None https://bugs.launchpad.net/zope2/+bug/142750 Bug #142782 in Zope 2: Function manage_ paste ignores proxy manager role New 2003-11-18 None https://bugs.launchpad.net/zope2/+bug/142782 Bug #142794 in Zope 2: CopySupport breaks all_meta_types New 2003-12-01 None https://bugs.launchpad.net/zope2/+bug/142794 Bug #142814 in Zope 2: copy/paste does not change ownership New 2003-12-19 None https://bugs.launchpad.net/zope2/+bug/142814 Bug #142832 in Zope 2: 404 errors caused by xml-rpc calls are masked New 2004-01-12 None https://bugs.launchpad.net/zope2/+bug/142832 Bug #142848 in Zope 2: misplaced trust in Host header New 2004-01-19 None https://bugs.launchpad.net/zope2/+bug/142848 Bug #142878 in Zope 2: AccessRules can't safely be used for security New 2004-02-09 None https://bugs.launchpad.net/zope2/+bug/142878 Bug #142910 in Zope 2: OFS.SimpleItem initialization problem: infinite loop New 2004-03-11 None https://bugs.launchpad.net/zope2/+bug/142910 Bug #142968 in Zope 2: script headers and execute permission New 2004-05-04 None https://bugs.launchpad.net/zope2/+bug/142968 Bug #142995 in Zope 2: Publishing machinery should not pass around traceback objects New 2004-05-17 None https://bugs.launchpad.net/zope2/+bug/142995 Bug #143001 in Zope 2: NullResource doesn't aq-wrap newly created object during PUT New 2004-05-20 None https://bugs.launchpad.net/zope2/+bug/143001 Bug #143022 in Zope 2: BaseRequest.traverse doesn't handle __bobo_traverse__ correctly New 2004-06-01 None https://bugs.launchpad.net/zope2/+bug/143022 Bug #143045 in Zope 2: bin\mkzeoinstance.py creates unix instance on windows New 2004-06-28 None https://bugs.launchpad.net/zope2/+bug/143045 Bug #143070 in Zope 2: DateTime object with timezone GMT+XX.XX New 2004-07-08 None https://bugs.launchpad.net/zope2/+bug/143070 Bug #143116 in Zope 2: Medusa doesn't catch Connection reset by peer sometimes New 2004-08-08 None https://bugs.launchpad.net/zope2/+bug/143116 Bug #143129 in Zope 2: Allow for
Re: [Zope-dev] Launchpad gardening
On Apr 15, 2010, at 12:51 PM, Sidnei da Silva wrote: On Thu, Apr 15, 2010 at 12:41 PM, Leonardo Rochael Almeida leoroch...@gmail.com wrote: Thanks Tres and Sidnei, My questions were intended to go to the list anyway. Can we take a branch from the launchpad mirror and bind it back directly at svn+ssh://svn.zope.org/ to commit? For instance, say I'm reviewing a bugfix proposed by someone that doesn't currently have access to svn.zope.org but added a merge-proposal to lp, can I branch it, bind it to svn+ssh://svn.zope.org and then commit? Wouldn't it be nice if it was possible? Not sure if it would. What you really want to do is to merge the bzr branch you got from Launchpad into the 'trunk' you got from svn.zope.org, which behaves exactly as Tres described on his previous email. Pushing the branch directly without merging first would overwrite the contents of the target branch with the contents of the pushed branch. I didn't think this was true, so I checked another source. :-) bzr does not allow that, actually--at least for bzr branches, and I suspect for svn branches. If the branches are diverged, you can't just push. You need to merge and then push. But, my source for bzr knowledge warns me, if you merge with the public version, and then try to push to the public version, your revno will change, and that will confuse people. So, a better story is to use bzr as if it were svn at that point: bzr co the trunk, bzr merge your changes, and bzr commit. If the Launchpad import of a given SVN package was recently created (since late 2009) then it works quite nicely. If it was made earlier, you will encounter hiccups. With the new imports I've done stuff like this. - bzr branch the import from LP. - Make changes locally and commit. - push branch to LP - make a merge proposal on LP and get a review - bzr push the branch to a new branch on zope's svn (each commit you made locally shows up separately even though it is one big push) - bzr co the svn trunk, merge my changes, and commit. It's quite nice. Handling merges is wildly nicer in the correct dvcs options than svn. The only limitation for bzr right now is that bzr doesn't handle svn externals. That's slated to change this year, I think. If people are curious, Sidnei or I could reach out and get more details of the timeline. Gary ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Launchpad gardening
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gary Poster wrote: On Apr 15, 2010, at 12:51 PM, Sidnei da Silva wrote: On Thu, Apr 15, 2010 at 12:41 PM, Leonardo Rochael Almeida leoroch...@gmail.com wrote: Thanks Tres and Sidnei, My questions were intended to go to the list anyway. Can we take a branch from the launchpad mirror and bind it back directly at svn+ssh://svn.zope.org/ to commit? For instance, say I'm reviewing a bugfix proposed by someone that doesn't currently have access to svn.zope.org but added a merge-proposal to lp, can I branch it, bind it to svn+ssh://svn.zope.org and then commit? Wouldn't it be nice if it was possible? Not sure if it would. What you really want to do is to merge the bzr branch you got from Launchpad into the 'trunk' you got from svn.zope.org, which behaves exactly as Tres described on his previous email. Pushing the branch directly without merging first would overwrite the contents of the target branch with the contents of the pushed branch. I didn't think this was true, so I checked another source. :-) bzr does not allow that, actually--at least for bzr branches, and I suspect for svn branches. If the branches are diverged, you can't just push. You need to merge and then push. But, my source for bzr knowledge warns me, if you merge with the public version, and then try to push to the public version, your revno will change, and that will confuse people. So, a better story is to use bzr as if it were svn at that point: bzr co the trunk, bzr merge your changes, and bzr commit. If the Launchpad import of a given SVN package was recently created (since late 2009) then it works quite nicely. If it was made earlier, you will encounter hiccups. With the new imports I've done stuff like this. - bzr branch the import from LP. - Make changes locally and commit. - push branch to LP - make a merge proposal on LP and get a review - bzr push the branch to a new branch on zope's svn (each commit you made locally shows up separately even though it is one big push) - bzr co the svn trunk, merge my changes, and commit. It's quite nice. Handling merges is wildly nicer in the correct dvcs options than svn. The only limitation for bzr right now is that bzr doesn't handle svn externals. That's slated to change this year, I think. If people are curious, Sidnei or I could reach out and get more details of the timeline. - From my research, support for svn:externals in bzr-svn is actually blocked on an upstream bzr feature which is itself stalled (no activity for 2 years now, I think). svn:externals are already kind of a wart, although recent SVN versions have fixed one long-standing issue (they allow relative externals now). I think we have a few recurring patterns in the repository: - using an external to pull in $ZSVN/bootstrap, rather than copying the bootstrap.py file. I'm ambivalent here, and could easily see dumping the external. - using an external to work around setuptools' inablility to install headers in a useful way, e.g. Zope's 'include' directory. Maybe a new recipe would be better? - using externals to stitch together omnibus buildouts, e.g. CMF.buildout. We could probably use something like 'infrae.subversion' instead, maybe with a hook that allowed local customization of the command used to fetch the sub-checkout. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvHTH4ACgkQ+gerLs4ltQ5imwCgz9YvLWyVMqRTJbqgjYPntzGg FE8AnR0LZivfJM9tjC5TJI2uTQmV3LZE =N1uu -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Launchpad gardening
On Apr 15, 2010, at 1:27 PM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gary Poster wrote: On Apr 15, 2010, at 12:51 PM, Sidnei da Silva wrote: On Thu, Apr 15, 2010 at 12:41 PM, Leonardo Rochael Almeida leoroch...@gmail.com wrote: Thanks Tres and Sidnei, My questions were intended to go to the list anyway. Can we take a branch from the launchpad mirror and bind it back directly at svn+ssh://svn.zope.org/ to commit? For instance, say I'm reviewing a bugfix proposed by someone that doesn't currently have access to svn.zope.org but added a merge-proposal to lp, can I branch it, bind it to svn+ssh://svn.zope.org and then commit? Wouldn't it be nice if it was possible? Not sure if it would. What you really want to do is to merge the bzr branch you got from Launchpad into the 'trunk' you got from svn.zope.org, which behaves exactly as Tres described on his previous email. Pushing the branch directly without merging first would overwrite the contents of the target branch with the contents of the pushed branch. I didn't think this was true, so I checked another source. :-) bzr does not allow that, actually--at least for bzr branches, and I suspect for svn branches. If the branches are diverged, you can't just push. You need to merge and then push. But, my source for bzr knowledge warns me, if you merge with the public version, and then try to push to the public version, your revno will change, and that will confuse people. So, a better story is to use bzr as if it were svn at that point: bzr co the trunk, bzr merge your changes, and bzr commit. If the Launchpad import of a given SVN package was recently created (since late 2009) then it works quite nicely. If it was made earlier, you will encounter hiccups. With the new imports I've done stuff like this. - bzr branch the import from LP. - Make changes locally and commit. - push branch to LP - make a merge proposal on LP and get a review - bzr push the branch to a new branch on zope's svn (each commit you made locally shows up separately even though it is one big push) - bzr co the svn trunk, merge my changes, and commit. It's quite nice. Handling merges is wildly nicer in the correct dvcs options than svn. The only limitation for bzr right now is that bzr doesn't handle svn externals. That's slated to change this year, I think. If people are curious, Sidnei or I could reach out and get more details of the timeline. - From my research, support for svn:externals in bzr-svn is actually blocked on an upstream bzr feature which is itself stalled (no activity for 2 years now, I think). Yes. That's the thing that should be worked on soonish. svn:externals are already kind of a wart, although recent SVN versions have fixed one long-standing issue (they allow relative externals now). I think we have a few recurring patterns in the repository: - using an external to pull in $ZSVN/bootstrap, rather than copying the bootstrap.py file. I'm ambivalent here, and could easily see dumping the external. - using an external to work around setuptools' inablility to install headers in a useful way, e.g. Zope's 'include' directory. Maybe a new recipe would be better? Not clear if it would help, but I'm actively maintaining z3c.recipe.filetemplate. In the process of adding support for relative paths. - using externals to stitch together omnibus buildouts, e.g. CMF.buildout. We could probably use something like 'infrae.subversion' instead, maybe with a hook that allowed local customization of the command used to fetch the sub-checkout. That would be cool. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Launchpad gardening
On Thu, Apr 15, 2010 at 2:27 PM, Tres Seaver tsea...@palladion.com wrote: - using externals to stitch together omnibus buildouts, e.g. CMF.buildout. We could probably use something like 'infrae.subversion' instead, maybe with a hook that allowed local customization of the command used to fetch the sub-checkout. I'd recommend mr.developer then, if you haven't looked at it yet. http://pypi.python.org/pypi/mr.developer I believe it *might* be using infrae.subversion under the covers, though I'm not 100% confident. The nice thing it adds on top of that is switching between a release version and a checkout in a single command, IIRC. -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] KGS 3.4.1 versions
Adam GROSZER a écrit : Hello, There is a sheet with versions for KGS 3.4.1 http://spreadsheets.google.com/pub?key=tUE5Q72d4Kg1FXaacCA3EKQoutput=html Anyone for/against those versions? The open questions that remain: * What about pytz 2010g? * Which lxml version to take? 1.3.6? * What about zope.app.container 3.6.2? * Would be nice to have zope.testbrowser 3.5.1 Comments are welcome. z3c.layer has a major security issue, because of trusted traversing adapters that removes the security proxy everywhere. This package has been retired and splitted into its 3 subpackages : z3c.layer.minimal z3c.layer.pagelet z3c.layer.trusted There is no problem upgrading to branch 1.0 of these packages, as they don't have any significant changes, excepted the splitting. However: z3c.layer.pagelet should be in version 1.0.2. Nothing below. z3c.layer.minimal has no corrected 1.0 branch. A new maintenance release 1.0.2 of this package should be released. z3c.layer.trusted is OK, since this is trusted in purpose. (I think) Christophe ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Minutes from this weeks meeting
Christian Theune a écrit : Hi, Hi thanks for the minutes! here's the minutes. As I've been adventurous, I'll add a few comments: * I've started diving into the matter of how to manage items that we park/defer/postpone/wait for and thus started using an online system. (The only one I was able to find anyway.) which online system are you talking about? * The output is a PDF which is currently a bit messy as I wanted to get rid of my text files that had the open issues sitting in there and thus had to add all of them to our agenda on Tuesday and then defer them. I think next week will become less noisy. * In general I can give access to stuff there to more people. I'll probably add those of you that step up for some tasks so I can mark the assignments appropriately. I hope this helps, at least I have the feeling it helps me stay organized and thus take less time in the future to write up the agendas and minutes. Christian ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Minutes from this weeks meeting
On 2010-4-15 17:59, Christian Theune wrote: Hi, here's the minutes. As I've been adventurous, I'll add a few comments: * I've started diving into the matter of how to manage items that we park/defer/postpone/wait for and thus started using an online system. (The only one I was able to find anyway.) * The output is a PDF which is currently a bit messy as I wanted to get rid of my text files that had the open issues sitting in there and thus had to add all of them to our agenda on Tuesday and then defer them. I think next week will become less noisy. Will next week be text again? Wichert. -- Wichert Akkerman wich...@wiggy.net It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Minutes from this weeks meeting
On 04/15/2010 10:44 PM, Christophe Combelles wrote: Christian Theune a écrit : Hi, Hi thanks for the minutes! here's the minutes. As I've been adventurous, I'll add a few comments: * I've started diving into the matter of how to manage items that we park/defer/postpone/wait for and thus started using an online system. (The only one I was able to find anyway.) which online system are you talking about? mycommittee.com -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Launchpad gardening
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sidnei da Silva wrote: On Thu, Apr 15, 2010 at 2:27 PM, Tres Seaver tsea...@palladion.com wrote: - using externals to stitch together omnibus buildouts, e.g. CMF.buildout. We could probably use something like 'infrae.subversion' instead, maybe with a hook that allowed local customization of the command used to fetch the sub-checkout. I'd recommend mr.developer then, if you haven't looked at it yet. http://pypi.python.org/pypi/mr.developer I believe it *might* be using infrae.subversion under the covers, though I'm not 100% confident. The nice thing it adds on top of that is switching between a release version and a checkout in a single command, IIRC. What, y'all haven't hacked bzr support into it yet? They support svn, cvs, hg, git... :) Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvHhnoACgkQ+gerLs4ltQ6B1ACgyTx8xbL/4MGwgnW0RmRRH5cN wEoAoKLcqUJGwdFZRTfMnIJ1R9aNWdRU =8jt0 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Minutes from this weeks meeting
On 04/15/2010 11:27 PM, Wichert Akkerman wrote: On 2010-4-15 17:59, Christian Theune wrote: Hi, here's the minutes. As I've been adventurous, I'll add a few comments: * I've started diving into the matter of how to manage items that we park/defer/postpone/wait for and thus started using an online system. (The only one I was able to find anyway.) * The output is a PDF which is currently a bit messy as I wanted to get rid of my text files that had the open issues sitting in there and thus had to add all of them to our agenda on Tuesday and then defer them. I think next week will become less noisy. Will next week be text again? Probably not - the system currently only allows for PDF output, but I've mailed them a question about getting plain text. Something I think will happen next week is that the noisy irrelevant items will appear neither on the agenda nor the minutes. Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
