Re: [VOTE] retire zeta components from incubation
Travis seems good, no host on our side. Is there a fee or something ? Le 14 avril 2012 18:11, Jérôme Vieilledent j...@ez.no a écrit : About CI, we could use Travis. It works perfectly with Github and PHPUnit. Several PHP projects already use it --- Jérôme Vieilledent Software engineer eZ Systems | 26 rue de la République, 69002 Lyon, France mailto:j...@ez.no skype lolautruche | twitter @jvieilledent Le samedi 14 avril 2012 à 18:04, Gaetano Giunta a écrit : Derick Rethans wrote: On Fri, 13 Apr 2012, Julien Vermillard wrote: Due to the reasons exposed later, and mainly due to lack of activity : [X] +1 Retire the Zeta components project and move to another infra like github I think it'd work better on github, but still, there needs to be a release at some point. I think github is ok for hosting the code. Pull requests and cherry-picks rock. And moving to git can have some nice PR. Things I'm a bit worried about is the rest of infrastructure: - github tracker is really de suck (imho of course) - where do we move the ml? - build/ci servers Bye Gaetano cheers, Derick -- Maxime maxime.tho...@wascou.org | www.wascou.org | http://twitter.com/wascou
Re: Github tools and discussions
@Jerome Vieilledent : How do you manage that at eZ ? 2012/4/15 David Neilsen da...@panmedia.co.nz Whos going to be responsible for managing pull requests? David Neilsen | 07 834 3366 | PANmedia ® 2012/4/15 Jérôme Vieilledent j...@ez.no Hi As Christian asked for, here's the github thread :). For CI : Travis should be OK. It's very well integrated with Github. We also talked few months ago about extra tools for code reviewing. For people that have push access to the repository, it is possible to do internal pull requests (ie. from a branch to master). It's then possible to discuss, comment line by line, just like any other PR. About the issue tracker, I think Github is sufficient, but of course we could have another stuff. Github has a lot of service hooks to link external tools like Mantis (or even Jira since Zeta is full Open Source) --- Jérôme Vieilledent Software engineer eZ Systems | 26 rue de la République, 69002 Lyon, France mailto:j...@ez.no skype lolautruche | twitter @jvieilledent -- Maxime maxime.tho...@wascou.org | www.wascou.org | http://twitter.com/wascou
Re: [zeta-dev] Missing report (was: Fwd: Incubator Board Report November 2011)
2011/11/16 Gaetano Giunta giunta.gaet...@gmail.com Daniel Fahlke wrote: 2011/11/16 Derick Rethansder...@apache.org On Wed, 16 Nov 2011, Christian Grobmeier wrote: Guys, we have missed a report. Hmm, I didn't see a reminder notice at all actually. I wonder why not? In addition I don't see very much activity on this podling. Are there still active people in this project? If so, please speak up. Sortofish... we are really small, and it seems we got a bit more on our plate since the code was donated. As far as I know, the project is right now mostly in support mode rather than let's write lots of new code. Maybe somebody else has a different opinion? cheers, Derick -- http://derickrethans.nl | http://xdebug.org Like Xdebug? Consider a donation: http://xdebug.org/donate.php twitter: @derickr and @xdebug the last reminder i got, was August 2011 But yeah, its not as active here as planed. Most people have more to do with work and related currently. I think too, that this project is already in support mode, but that we were not able to make a release yet is nothing good. We should at least now removing all blocking Tickets for this. Fully agree. I have no idea how many people are on the list, but it seems most of them are in sleeping mode, ie. have little time to devote to the project, except for the bugfix of their interest. To the outside world, the fact that there has been no release since the migration is not good pr. Maybe if there was one, we could start at least a bit of an ad campaign. the second thing i noticed. We need some plan for people who want contribute new components. In best case someone, who guide them throught the whole process and send them to the right place and person, if questions occur. For outsiders it often looks, like we are not interested in new components, this should change. Agree here too (see my recent post about a webservices-client component, that gathered only 1 response so far). Also, we should start a review of components that miss a maintainer, and make it more clear who the maintainer is for each one, so that responsibilities are better delineated, and possibly people get more committed. And maybe have a kind of board made of components maintainers that takes decisions about release dates and similar topics? Bye Gaetano Hi, Same for me. Not such time for this, but in touch to sell a Zeta Components powered soft. I'm waiting for business. Have we done some concurrency comparison to find a good idea of missing component ? Cheers, -- Maxime maxime.tho...@wascou.org | www.wascou.org | http://twitter.com/wascou
[zeta-dev] Search - Commit and Begin transaction issue
Hi fellows, I know zeta-dev is mostly in holidays, I will wait your come back to get some feedback. I've got stucked for 2 or 3 days on a commit issue using Apache SolR 3.1 with the Search component. I put the whole story, so if someone is encountering the same, it could be usable. Here was the issue : In the PHP, I was using the following code : $this-session = new ezcSearchSession( new ezcSearchSolrHandler($domain, $port , $uri./.$location), new ezcSearchEmbeddedManager() ); $this-session-index($object); Everything was going well until I tried to set the beginTransaction / commit mechanism. The following error was appearing in the solr logs : 2011-08-07 15:10:10.710:WARN::/solr/.../update/ java.lang.IllegalStateException: Committed at org.mortbay.jetty.Response.resetBuffer(Response.java:1023) at org.mortbay.jetty.Response.sendError(Response.java:240) at org.apache.solr.servlet.SolrDispatchFilter.sendError(SolrDispatchFilter.java:380) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:283) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:945) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) I've tried different things to identify where the issue was coming from and finally tried to see if it was my SolR. I've used the SolR client from this website http://www.solrclient.com/ that was very useful to send XML data quickly to test the instance. Everything has gone right with the good sequence of XML (add then commit). Digging more in the AZC Search API, I've quickly reached the index function of solr.php. At the end of this one, if the beginTransaction function was called before, the runCommit is run. Index is the only function to use the runCommit function. My question is : why put the commit logic at the end of this function ( it has not been done in the delete functions ) ? Is that an issue for you ? Let me know. -- Maxime maxime.tho...@wascou.org | www.wascou.org | http://twitter.com/wascou
Re: [zeta-dev] sqlabstraction update - multiple tables @ once
/7/9 Dominique 'NetAndroid' Schramm li...@schramm.es
Hi,
i put my head into the core of the sqlabstraction to find out how an
update performs for multiple tables. for an example:
$q = $pdb-createUpdateQuery();
$q-update('`domains`,`emailaddresses`')
-set('`domains.change`', '0')
-set('`emailaddresses.change`', '0');
$stmt = $q-prepare();
$stmt-execute();
@ the sqlabstraction i found the following code:
line:104
public function update( $table )
{
$table = $this-getIdentifier( $table );
$this-table = $table;
return $this;
}
this code means for me that only one table at once is possible. but why?
i think it will be quite simple to extend this section for multiple
tables update like the sql query. i am not perhaps i can create the code
and give it back to you?
--
Dominique 'NetAndroid' Schramm
- Twitter: @NetAndroid_BY
- Identi.ca: @netandroid
- Blog: http://netandroid.nl/
Hi Dominique,
There's a process to follow if you want to contribute to AZC.
Here it is :
http://incubator.apache.org/zetacomponents/community/dev_process.html
Regards,
--
Maxime
maxime.tho...@wascou.org | www.wascou.org | http://twitter.com/wascou
Re: [zeta-dev] Fwd: pear channels for releases
2011/4/15 Christian Grobmeier grobme...@gmail.com Just in case you didn't get it (or somebody not on the committers list is interested): -- Forwarded message -- From: Gav... ga...@16degrees.com.au Date: Fri, Apr 15, 2011 at 10:07 AM Subject: pear channels for releases To: committ...@apache.org Hi All, http://pear.apache.org Those projects that can, are welcome to release PEAR packages above as part of their release process. See the site for more details. Gav... -- http://www.grobmeier.de Hi, Is this replacing the pear channel described in the AZC conf ? http://incubator.apache.org/zetacomponents/documentation/install.html Replaced by : http://pear.apache.org/zetacomponents/index.html http://pear.apache.org/zetacomponents/index.html -- Maxime maxime.tho...@wascou.org | www.wascou.org | http://twitter.com/wascou
Re: [zeta-dev] Welcome: Benjamin and Jerome
2011/4/1 James Pic james...@gmail.com On Fri, Apr 1, 2011 at 7:49 PM, Tobias Schlitt tob...@schlitt.info wrote: Hi, I'd like to officially welcome Jerome (jeromer) and Benjamin (beberlei) as Apache Zeta Components committers. Congrats for your very well deserved promotion! Thanks again for your participation JB. Cheers Yep. Congrats guys ! You deserve it. -- Maxime maxime.tho...@wascou.org | www.wascou.org | http://twitter.com/wascou
Re: [zeta-dev] Logo - First try
2011/3/18 Tobias Schlitt tob...@schlitt.info Hi Max, thanks a lot for your work, very much appreciated! I think we should try to follow the design of the website and logo as much as possible, in order to gain a CI to some degree. This was not really the case for the recent drafts. I was more thinking of something in direction of the old Powered by eZ Components button as in [1] and [2] and possibly the typical blog buttons like the ones you can see in the right column of my website [3]. Would it be possible to try something in this direction? I know that such stuff is quite hard to make, due to the format of the logo, though. :/ Btw. you can find the original SVG sources of the logo and the website in SVN under website/layout/. That should be quite helpful, I guess. Best regards, Toby [1] http://ezcomponents.org/images/logos/powered-by-141x32-indigo.png [2] http://ezcomponents.org/images/logos/powered-by-141x32-white.png [3] http://schlitt.info/opensource.html -- Tobias Schlitthttp://schlitt.infoGPG Key: 0xC462BC14 Want to hire me? Need quality assurance?http://qafoo.com eZ Components are Zeta Components now! http://bit.ly/9S7zbn Hop, next try. This time, we focused on the background and the structure of the logo, according to Tobias feedback. Let me know if there's another attachment issue. -- Maxime maxime.tho...@wascou.org | www.wascou.org | http://twitter.com/wascou
[zeta-dev] Logo - First try
Hi, I've got some time this afternoon so I've made some tries. I've put the file in attachment. Let me know what you think about this one. It's also possible to decline the logo by color (deep blue, sky blue and silver) for a level of integration (to define). -- Max maxime.tho...@wascou.org | www.wascou.org | http://twitter.com/wascou
Re: [zeta-dev] Patch: Template string functions are not multibyte safe
Cool ! I'm maybe not pertinent but is it not a good moment to make a component called CodeBase or something else ? Could be useful in a lot of other components. Or maybe it has been a choice to not do like this... Is it redundant with the PHP6/7 UTF8 promises ? Max 2011/1/29 Andreas Schamberger m...@andreass.net Hi, I made a patch to make the template string functions handle UTF-8. Please find it for review here: https://issues.apache.org/jira/browse/ZETACOMP-15 What do you think? Regards, Andreas -- Maxime maxime.tho...@wascou.org | www.wascou.org | http://twitter.com/wascou
[zeta-dev] Search Component
Hi, I'm on a dev and needed to use the search component that I never used before. Actually, it was a pretty tough experience and spend more time understanding what was generated by ezcSearch than coding indexation and search queries. My point was very simple, I've got messages to index with a class like id (int), message (string). In SolR, I've defined in my core, only this two fields with id as uniqueKey and message as defaultSearchField. At first, I did not set up SolR to use dynamic fields. There were two problems : - first, another field was added : ez_search_field_s and I don't why. - second one, all my fields were automatically suffixed by there type... which wasn't the SolR type. Do you know why we have the ez_search_field_s added ? Why all the field are suffixed (with wrong types) ? Is it the normal way or did I miss something ? By the way, the solution was for me to inherit the ezcSearchSolrHandler and redefine the method index. Thank you for any kind of answer. -- Maxime maxime.tho...@wascou.org | www.wascou.org | http://twitter.com/wascou
Re: [zeta-dev] Persistent object vs DB Query
I finally did it with a $q-groupBy() and it's working with the PO session. The only thing I cannot do is what you've described (due to $q-select ()). Thank you anyway for the way to correctly doing the count (I was doing like this already but wondering if it was possible to do it with the PO session). Regards, Max 2011/1/3 Petar Španja petar.spa...@gmail.com Hi Maxime, PO fetches table rows through id fields, and it makes no sense to do distinct on id field, ids should be unique. Also you can't make count query through PO session. To add this functionality you should add a method in the query layer to transform your query to count query (modify select string, remove where string etc) and a method in the persistent session class that will use this. Regards, Petar On Thu, Dec 30, 2010 at 8:11 AM, Maxime Thomas maxime.t...@gmail.com wrote: Hi Zetadev, A quick question for those using ezcPersistentObject and the standard ezcPersistentSessionINstance::createFindQuery(). I'm a bit stuck with that code : code $s = ezcPersistentSessionInstance::get(); $q = $s-createFindQuery(className); ... $s-find($q, 'className'); /code How can I make distinct or count on className ? Do I have to cheat and do something like this : code $db = ezcDbInstance::get(); $q = $db-createSelectQuery(); $q-selectDistinct(id); $q-from(className); ... $s-find($q, 'className'); /code Or does it have a proper way to be run ? Or do I have to make my query with the query layer only ? Thank you for any kind of answers. -- Maxime maxime.tho...@wascou.org | www.wascou.org | http://twitter.com/wascou -- Maxime maxime.tho...@wascou.org | www.wascou.org | http://twitter.com/wascou
Re: [zeta-dev] [VOTE] Documenting coding style
2010/12/10 Tobias Schlitt tob...@schlitt.info Hi, since there was no further feedback on my patch for the coding style documentation, I'd like to call for votes on it. Find the patch to vote on attached again. Please vote [X] +1 yes, this is our official coding style [ ] 0 I don't care [ ] -1 no, I disagree, … $because … The vote will last 120 hours (72 standard voting time + weekend). Regards, Toby -- Tobias Schlitthttp://schlitt.infoGPG Key: 0xC462BC14 Want to hire me? Need quality assurance?http://qafoo.com eZ Components are Zeta Components now! http://bit.ly/9S7zbn -- Maxime maxime.tho...@wascou.org | www.wascou.org | http://twitter.com/wascou
Re: [zeta-dev] Online: Survey on PHP library release modes
I've done the same : http://www.wascou.org/eng/Company/Blog/PHP-Survey-Please-fill-in http://www.wascou.org/eng/Company/Blog/PHP-Survey-Please-fill-inMax 2010/12/2 Tobias Schlitt tob...@schlitt.info Hi Jerome, On 12/02/2010 11:21 AM, Jerome Renard wrote: I added a blog entry here (mostly a copy and paste version of your post) : - http://jrenard.info/blog/php-library-release-survey.html cool, thx. :) I wonder why I did not receive a trackback. Doesn't your blog send out trackbacks? Regards, Tiby -- Tobias Schlitthttp://schlitt.infoGPG Key: 0xC462BC14 Want to hire me? Need quality assurance?http://qafoo.com eZ Components are Zeta Components now! http://bit.ly/9S7zbn -- Maxime maxime.tho...@wascou.org | www.wascou.org | http://twitter.com/wascou
Re: [zeta-dev] Documenting our coding style
I saved in my bookmarks this one : http://pear.xplib.de/get/
http://pear.xplib.de/get/Max
2010/11/27 Jerome Renard jerome.ren...@gmail.com
Hi,
On Fri, Nov 26, 2010 at 2:23 PM, Derick Rethans der...@apache.org wrote:
On Tue, 16 Nov 2010, Tobias Schlitt wrote:
for another project I needed to give advice on the coding standard used
by Apache Zeta Components. There is some very old version of the eZ
Publish coding style in [1] (from 2001) but no reliable, recent source.
So I think we should document our coding style on the website.
Please complete / correct my following brainstorming:
- Indentation with 4 spaces
- After a {
- On breakup of long lines ( 78 chars) after a (
- { and } on a new line
- 1 space after ( and before )
- No space after [ and before ]
- 1 space after ,
- 1 space before and after .
- Almost always camelCase
- classes always start with ezc followed by an upper case char
- constants all in upper case with _
There is also a script at
http://svn.apache.org/repos/asf/incubator/zetacomponents/scripts/syntax-check.sh
that has a few rough automated checks.
I remember I used a PHP Code Sniffer standard for ZC is it still
available somewhere ?
I tried the old URL and it seems it's no longer there.
Best Regards,
--
Jérôme Renard
http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] Survey on PHP library release modes
2010/11/27 Jerome Renard jerome.ren...@gmail.com Hi Tobias, On Sat, Nov 27, 2010 at 7:40 PM, Tobias Schlitt tob...@schlitt.info wrote: Hi, I'm about to start a little online survey to check out how users in the PHP world would love to see their favorite libraries being released. I'll mainly do this out of private interest, but it might also help us to optimize our release process. Excellent idea :) Find below some questions for discussion. Whenever there is no additional info, only a single answer may be chosen. 1. Which libraries / frameworks do you use? (multiple answers possible) - ADOdb - Apache Zeta Components - Cake PHP - CodeIgniter - Doctrine 1 - Doctrine 2 - eZ Components - Horde - PEAR - Propel - Seagull - Symfony - Zend Framework - Another framework / library (free text) - I code everything on my own 2. What is your preferred way of installing PHP libraries? - PEAR - Custom installer - Manual download - OS based package management I would just add something like (apt-get, yum, rpm), just to avoid any confusion from beginner users. - Version control (SVN external, Git sub-module, etc.) - Something else (free Text) 3. Do you prefer bundles over single component installs? - I want to install each component separately - I want a bundle with all components from a library 4. How would you expect a PHP library project to do releases? - Irregularly whenever something is ready - Regularly with multiple additions bundled 5. How do you want to deploy PHP library components? - I bundle library components with my application - I deploy libraries and application separately Do you have anything to add / change? Even though I think it looks really good, would you think relevant to add a question about depedency ? For example framework needs external dependency X or Y. How do they prefer installing this dependency ? Possible options: - via PEAR - I want to get it bundled with the framework - I want to install it manually Not sure I am completely clear here. If it's not just tell me :) -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard Excellent idea. We can also ask : - the job of the person answering : system admin / webmaster / not IT - the platform : Unix / Linux systems or Windows - the level of industrialization : tailor made platform (you have every things installed as you want), shared platform (the web hosting company has decided for you you what you can do or not), generic platform (you grouped some of your application and factorize software layers : using PEAR, Zend or whatever). I think we have to segment the survey's answer because some will use it in one way and other in the other way. Will you publish the results of the survey ? Maxime maxime.tho...@wascou.org | www.wascou.org | http://twitter.com/wascou
[zeta-dev] Autoloads and autoload file
Hi there, I've got a small reflexion about the base mechanism of ezcBase that allows us to add an outside repository of classes [1]. Actually, I manage manually my autoload file and as we discussed before with James Pic [2], it could be a good point to have an extend to this mechanism and get a real script that will get the whole mapping class/file for you. I've checked in ez how is done the ezpautoloads script that does the job and the strategy is the following : list all php files, tokenize it, extract class names and make the file. Is it the optimal solution ? Can we find a better way to link classes and files ? Max [1] http://ezcomponents.org/docs/tutorials/Base#adding-class-repositories-located-outside-ez-components-to-autoload-system [2] James Pic shared autoload script : #!/bin/sh scanPath=. if [[ $1 != ]]; then scanPath=$1; fi; echo ?php; echo return array(; echo `find -L $scanPath -name *php | xargs grep ^class | sed -e s...@\([^:]*\):class \([^ ]*\).*@'\2' = '\1',\ @`; echo `find -L $scanPath -name *php | xargs grep ^abstract class | sed -e s...@\([^:]*\):abstract class \([^ ]*\).*@'\2' = '\1',\ @`; echo `find -L $scanPath -name *php | xargs grep ^interface | sed -e s...@\([^:]*\):interface \([^ ]*\).*@'\2' = '\1',\ @`; echo );; echo ?;
Re: [zeta-dev] Autoloads and autoload file
Actually, I was thinking about this autoloads script for an app as it's done with eZP. It could be part of the ezcBase as an independent script. My point was to challenge the ezpublish strategy and see how to integrate it into ezcBase. By the way, I understand the point to normalize that for a whole environment (if I correctly get it) and to follow a policy such as Debian's. I guess PHP is still the best option for this, but I cannot find a link between the files and the classes (as packages in Java) that can easily do the trick. If we can do that, and that's my next idea, we can purpose some easy extension mechanism using PHP's Reflection or replacing it, following our needs. Max 2010/11/24 Henri Bergius ber...@apache.org On Wed, Nov 24, 2010 at 11:43 AM, Ole Marius Smestad o...@ez.no wrote: For production environments it makes sense, and we have been toying with the idea of adopting the scripts to also create a similar list, which could work with components. In regular situations you probably need two setups: * Production: Zeta Components and other classes coming from PEAR or native packages (I'd love to see Zeta in Debian as soon as there is an official Apache release) * Development: Zeta Components and other classes coming from various Git/SVN checkouts The paths are likely to be quite different in these two scenarios. For production setups the relevant Debian policies are quite interesting. I recently packaged OpenPSA (a Midgard-based business management suite) to Debian and the policies made things quite clear: http://webapps-common.alioth.debian.org/draft-php/html/ http://webapps-common.alioth.debian.org/draft/html/ Ole Marius /Henri -- Henri Bergius Motorcycle Adventures and Free Software http://bergie.iki.fi/ Skype: henribergius Jabber: henri.berg...@gmail.com Microblog: http://www.qaiku.com/home/bergie/
Re: [zeta-dev] Proposal: Release process
Another point that has maybe already been discussed but how do we manage components in the SVN, do we have separate tags and branches for the set of components and each component ? My point is to chose the easiest way to deliver things : if each package must be done manually, it increases the probability of mistakes. The best option is maybe to start with a simple package and then see what happend (some feedback of people). We can keep : - the access to SVN - the pear channel with identified version (like ezc) Max 2010/11/18 Gaetano Giunta giunta.gaet...@gmail.com James Pic wrote: Hi all, I'm not qualified to participate actively to the current discussions, although i'm reading it all. However, i'd like to share how it works with python/pinax projects because it might inspire you. On Thu, Nov 18, 2010 at 9:46 AM, Tobias Schlitttob...@schlitt.info wrote: Hi Max, On 11/18/2010 09:21 AM, Maxime Thomas wrote: Actually only the packaging of zeta matters as we want to provide everything or a part of it. The jQuery UI package download system seems to be a good start, I guess. Another question comes if we do like this : will it be possible to make heterogeneous packages with this system. I mean can I ask Graph 1.0 with Config 3.2 ? or do I have a minimum rules to follow ? Pinax projects use a requierements.txt file, for example:: --extra-index-url=http://dist.pinaxproject.com/dev/ Django==1.2.1 Pinax==0.9a1 django-debug-toolbar==0.8.3 django-staticfiles==0.2.0 -e git+ssh://g...@github.com:jpic/sorl-thumbnail.git#egg=sorl-thumbnail That file is tracked by the VCS in each project. To deploy a new environment for my project, all i have to do is:: # pip is like pear, for python pip install -r requirements.txt That allows: - each project to have different component dependencies - with specific versions - deployment is piece of cake I don't think it's possible with official pear, anyway: if we decide that it's the way to go then we'll find a way. shame on pear! otoh: would we have such info available for existing components or would it be so hard to extract it in a precise and useful way that it would not be done anyway (I mean apart from the obvious compatibility that we get from the complete bundles)? Regards James
Re: [zeta-dev] Draft: Status update blog entry
Excellent ! A blog is effectively the best way to inform people with some modern way to inform (RSS). 2010/11/17 Christian Grobmeier grobme...@gmail.com I would be happy if we could provide such status updates somewhat regularly (maybe once a month?), in order to keep people informed and to attract more contributors. What do you think? Great idea! Btw, you can have an apache blog by requesting it from jira http://blogs.apache.org/ In this blog you have the chance for a preview and send the preview to the dev list were people can make suggestions or vote about. Best regards, Christian
Re: [zeta-dev] Proposal: Release process
Why not, but if I want a set of components that includes tiein, how can I do ? Do I have to download each components separately ? My opinion is maybe to get both version numbers as it was done fore ezc, a version number for the set and a version number for each components. By this way, everyone could either download the full package or just the package they want. And honestly, I cannot see the problem of downloading all even if you don't use some parts. Who can do the more can do the less. Max 2010/11/16 Patrick ALLAERT patrick.alla...@gmail.com 2010/11/16 Gaetano Giunta giunta.gaet...@gmail.com: Maxime Thomas wrote: Sound strange, if we look at what is done elsewhere : - JQuery UI : shared version number - Zend : shared version number - Former eZComponents : both version number also YUI The shared version number implies a kind of packaged application. Else it can be difficult to install and maintain (same as Gaetano). Max 2010/11/16 Patrick ALLAERTpatrickalla...@php.net 2010/11/16 Gaetano Giuntagiunta.gaet...@gmail.com: Tobias Schlitt wrote: Hi Thomas, On 11/07/2010 11:55 AM, Thomas Ernest wrote: Le 04/11/2010 17:28, Tobias Schlitt a écrit : docs/release_process.txt It is a very interesting and useful synthesis. Thank you. The document summarizes the requirements for releases roughly and then tries to relealize these in a release process specific to Zeta. There are some open issues marked with notes in this document, which need to be decided on. I read the document and I focused on the two next issues (or notes) : .. note:: Incubating phase (around line 118) I don't understand what is the matter with this one. Could you tell me more please ? We are currently incubating, which means we are under deeper control of the ASF. For a release that means we need to perform 2 steps before uploading it to the servers: 1. Vote here on the list 2. Have a second vote on the Incubator PMC list Step 1 will also be mandatory once we have been promoted to be a top level project. Step 2 is only mandatory before that. I hope that made it clearer? .. note:: Determine release times. (around line 155) It seems that a full package release is a packaging of all last *stable* component releases. Hence, a full package release could be rolled automatically after every component release. We did not realize such a procedure until now for two reasons: 1. Releasing was not that easy in the eZ Components project 2. Updating the full package install is cumbersome work for users I'd pretty much love to get rid of 1 for Zeta Components, so that should not be an issue in the future. However, the full package cannot be installed automatically by users. They need to manually unpack stuff. This kind of release is pretty much useful for people who just want to take a first look and play around with the code. However, I personally would love to have such automatic package builds, as I would love nightly builds, too. It's just quite some work to realize this and we need a volunteer to take care for it. And I'm not sure if everyone agrees with my views here. So, I see full package release as a sub part of component release process, which involves that : - There is no need for release time. - There is no need for votes. That would indeed save some bureaucratic hassle, yes. :) This possibility relies on the assumption that a full package release hasn't more value-added (or worth) than sum of stable component releases. It means that there is no additional deployment mechanism in full package releases for instance. No, so far the full package releases only contained stable component versions, which were also distributed through the PEAR channel earlier. Here comes questions : A/ What is your opinion about the proposal automate full package release ? B/ What are advantages of separating full package release process from component release process ? (It should probably be my first question before writing all this stuff :-)) For A: I would love to see such a process, as said above. For B: An advantage of the previous process was, that component maintainers always tried to have features ready by a defined date, so that they can become part of the full package release. However, I think a more agile way, which allows us to release more fast and often would be nice. As an end user, sysadmin and app developer, the idea of having per-component release makes my head hurt. While I agree that a more agile build infrastructure is a bonus, as user of the library I do not need at all separate components versions released independently. How could I possibly test the new zeta-c versions, pick the ones to integrate in my projects, decide on timing of upgrades, when a new component
Re: [zeta-dev] Configuration component proposal with override mechanism
I've put it in the Jira. Max 2010/8/12 Jerome Renard jerome.ren...@gmail.com Hi Maxime, On Thu, Aug 12, 2010 at 10:33 PM, Maxime Thomas maxime.t...@gmail.com wrote: Hi, I also would like to have this has a new feature in this update : Description = The configuration package could be able to store and retreive assoc arrays. Example = Consider an application with a block setting call MySettings and a a settings called Data. It will be useful to get a key to directly access one of the Data settings without looping on it. [MySettings] Data[key1]=foo Data[key2]=bar Data[key3]=bla ... Use === A use of it could be : $data = $cfg-getSetting(MySettings, Data); echo $data[key1]; Should print : foo I think this is a complete different feature. Please file an enhancement request for that in the issue tracker: - https://issues.apache.org/jira/browse/ZETACOMP Thanks :) -- Jérôme Renard http://39web.fr | http://jrenard.info
Re: [zeta-dev] SVN test import online; releases/ and release-info/?
Hi, Seems good, I can access it in read. What is gmcdonald reffering to ? Max 2010/7/19 Tobias Schlitt tob...@schlitt.info -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, our test import is up and running on http://svn.apache.org/repos/test/gmcdonald/zeta/ Looks good so far. :) Please check out and test! I wonder what should happen with - - releases/ - - release-info/ directories. They contain all previous eZ Components releases and corresponding release notes (release-info/). I think we should not keep them in the new SVN, but have them imported anyway. We can then delete them afterwards. This way, we still keep their history. What do you say? Cheers, Toby - -- Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 a passion for php http://schlitt.info/opensource eZ Components are Zeta Components now! http://bit.ly/9S7zbn -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxD5EwACgkQ5bO3TcRivBSfBgCgq3kGlU1GyOW6LKGNd8ni0uRO MaEAn0gbkNkEaRt3nIJfn5J1Bq2jvmvu =xVYk -END PGP SIGNATURE-
[zeta-dev] [jira] Created: (ZETACOMP-2) [TemplateTranslationTieIn]
[TemplateTranslationTieIn]
---
Key: ZETACOMP-2
URL: https://issues.apache.org/jira/browse/ZETACOMP-2
Project: Zeta Components
Issue Type: Bug
Environment: All
Reporter: Maxime THOMAS - Wascou.org
Priority: Critical
If I run the extractor against tpl files containing the following code, the
comment are not extracted.
{tr_context bla}
{tr blabla comment blibli}
In the file visitors/string_extracter.php and in the function
visitTranslationTstNode, fix the following line :
$comment = $node-comment ? $node-comment-accept($this)-value :
null;
By :
$comment = $node-comment ? $node-comment-value : null;
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
