Re: [zeta-dev] Zeta Components Release on 2011-12-22 - Issue Management
On Thu, Dec 15, 2011 at 10:32 AM, Daniel Fahlke wrote: > ok, lets play a game. =) > I send this mail every Day now and we count how many times i have sent it, > till it gets done. > That's a very bad idea xD
Re: [zeta-dev] Zeta Components Release on 2011-12-22 - Issue Management
ok, lets play a game. =) I send this mail every Day now and we count how many times i have sent it, till it gets done. count: 3 2011/12/9 Daniel Fahlke > Hi, > > related to my mail from before i want to change some Issue states and > asign Issues to certain Releases (primary the upcomming one) > > So, I dont have a clue how the upcomming Version should be named ( I > remember a discuss about it but not the result. ) > Anyone who can Answer this, or have I to reread the discuss about it? > > Assign to the upcomming Version i would the following Issues > #102 > #95 > #74 > #65 > #62 > #25 > #22 > > Than, close #92 as duplicate of #21 > > Would be nice if someone could do this for me or give me the rights to do > this. > > Regards, > Daniel Fahlke > aka Flyingmana >
Re: [zeta-dev] Zeta Components Release on 2011-12-22
On 12/06/2011 01:11 AM, Derick Rethans wrote: > > That'd be awesome, but I intend to be in the pub (as Dec 22nd is my > birthday :-)). Have a cuba libre on me ! Cheers, from spain
Re: [zeta-dev] Zeta Components Release on 2011-12-22 - Issue Management
2011/12/10 James Pic > "what would be nice, if you can confirm my two failing unittests for > the archive component or if they are not failing for you" > > What patch are you talking about ? > Its not a Patch, simple two Unittests they are failing for me. Have now added them as an Issue with all Output.
Re: [zeta-dev] Zeta Components Release on 2011-12-22 - Issue Management
"what would be nice, if you can confirm my two failing unittests for the archive component or if they are not failing for you" What patch are you talking about ?
Re: [zeta-dev] Zeta Components Release on 2011-12-22 - Issue Management
On 12/09/2011 05:13 PM, Daniel Fahlke wrote: > Hi, > > related to my mail from before i want to change some Issue states and asign > Issues to certain Releases (primary the upcomming one) Issue assignment is generally a good idea. In the case of Zeta Components there is not much traffic for the moment (Last 30 days summary: 5 issues created and 0 resolved) so it's pretty safe to fix something and then post the patch in the corresponding issue page. > > So, I dont have a clue how the upcomming Version should be named ( I > remember a discuss about it but not the result. ) > Anyone who can Answer this, or have I to reread the discuss about it? > A classic naming advice is to search for consonance, like cocacola, cocobongo, bestbuy, google ... Apart from that i have no idea heh . Do you have ideas ? > Assign to the upcomming Version i would the following Issues > #102 > #95 > #74 > #65 > #62 > #25 > #22 > Ready for commit & close: https://issues.apache.org/jira/browse/ZETACOMP-95 The other issues, still need patch: https://issues.apache.org/jira/browse/ZETACOMP-102 https://issues.apache.org/jira/browse/ZETACOMP-74 https://issues.apache.org/jira/browse/ZETACOMP-65 https://issues.apache.org/jira/browse/ZETACOMP-62 https://issues.apache.org/jira/browse/ZETACOMP-25 https://issues.apache.org/jira/browse/ZETACOMP-22 > Than, close #92 as duplicate of #21 > Confirmed Cheers
Re: [zeta-dev] Zeta Components Release on 2011-12-22 - Issue Management
Hi, related to my mail from before i want to change some Issue states and asign Issues to certain Releases (primary the upcomming one) So, I dont have a clue how the upcomming Version should be named ( I remember a discuss about it but not the result. ) Anyone who can Answer this, or have I to reread the discuss about it? Assign to the upcomming Version i would the following Issues #102 #95 #74 #65 #62 #25 #22 Than, close #92 as duplicate of #21 Would be nice if someone could do this for me or give me the rights to do this. Regards, Daniel Fahlke aka Flyingmana
Re: [zeta-dev] Zeta Components Release on 2011-12-22
On Tue, 6 Dec 2011, Daniel Fahlke wrote: > i have looked through the open Issues and tested checkout and unittests. > > So first, what is really blocking the release. > >- that there is still occurrence of the term eZComponents inside of code > files >- the website is still not complete with all needed information >- Unittests are not running completely without fails. And we can't run them properly, as PHPUnit breaks BC... not sure whether Sebastian already fixed the tests or not. > As this all are not heavy problems, I recommend the 22. December as > Release Target, so we have a Full working release in this year. That'd be awesome, but I intend to be in the pub (as Dec 22nd is my birthday :-)). > To be able to better organize this, it would be nice, if i can get some > more rights on the Issue Tracker or at least someone, who has time the next > days, so i can get on his nerves. I've no idea how to change that... > Also i will provide some patches and reviw some already submitted patches > to see, what is missing for adding them. Would be good, if i can reach > someeone in IRC for this, else i would need to spam the mailinglist with > every seperate Issue. (you dont want this, do you?^^) > > A Problem i Already found in Unitests is, that ldap://ezctest.ez.no:389 is > not accessable (or at least only returns a -1) > Dont know how this should be handled, but for now we should add a short > tutorial for setting up an own ldap server and /etc/hosts entry for make it > testable again. We actually have a test instance on the apache infrastructure where we should set this up. The same is true for the mail tests. > The other Issue I had with Unittests is the failing of the tests > ezcArchiveV7TarTest::testAppendArchiveAtOnce and > ezcArchiveUstarTarTest::testAppendArchiveAtOnce > Can someone reproduce this for me, so i can add it to the tracker? I can't actually figure out how to run just the Archive tests right now :-/ cheers, Derick -- http://derickrethans.nl | http://xdebug.org Like Xdebug? Consider a donation: http://xdebug.org/donate.php twitter: @derickr and @xdebug
