Hi, >> Once the package is stable again it should be proposed to the various >> Linux distributions (I could upload a Debian package) and to all the >> Web Frameworks like Zend or Symfony who have started to build their own >> logging framework and advertise this and to those who do not already >> recommend one.
This is a good idea, thanks! Even if it sorts out that this is not possible with incubator releases, this is a good idea for later too. > Certainly a TODO list is a good idea. As an incubating project I'm not sure > about the packaging ideas yet. I agree. When updating the website, I will link up with the already existing Wiki were we can place such a TODO list. > Also, blog early and blog often -- I know Christian already does this on his > own blog. We also have blogs.apache.org - every project is entitled to have > their own blog there and committers of those projects can have accounts. > Christian (Grobmeier) let me know if you are interested and I'll set one up > for log4php straight away. OpenEJB and others use it quite successfully. Do you think a blog on blogs.apache.org is more useful than having it on personal blogs? If so, I think we should start one. I am not sure about this. > So, first job then is I would look at that batch of 15 open issues on Jira - > 1. decide out of those which will form part of the initial release > 2.0-incubating, > 2. change the rest to become part of the 2.1 schedule. I think this is fine too - lets start this after we have a proper website running and a todo list on the wiki. > 3. Decide after that if there is anything else left hanging, i.e. not in the > issue tracker but needs finishing off before a release. (Such as producing > RAT reports to indicate if any files are missing license headers etc - this > should actually be added to the Issue Tracker - I can do this part) Yes please that would be great. We also don't have any plans of "how to" doing a release. Therre is a maven pom file in the project, but i am unsure how we should use it. I think this task stopped while evaluation phase. > Christian (Grobmeier), as the main active committer, you know your timeline > better than anyone, so coming up with a guestimate of a release date should > be down to you, OK, I will think about that. At the moment I would see that we still have some code improvements left and need to work on the base. So more help so earlier we can talk again about a release, but at the moment I see it somewhere in autumn or beginning winter. Best, Christian
