Re: [zeta-dev] Zeta Components Release on 2011-12-22 - Issue Management

[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 - Issue Management

[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 ?

[zeta-dev] Zeta Components Release on 2011-12-22

[Daniel Fahlke]

Hi all,

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.

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.

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.

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.

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?


Regards,
Daniel Fahlke
aka Flyingmana