| Summary: | log4j 1.2.16 release considerations and discussion | ||
|---|---|---|---|
| Product: | Log4j - Now in Jira | Reporter: | Curt Arnold <carnold> |
| Component: | Other | Assignee: | log4j-dev <log4j-dev> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | hugues, randomshelley, thorbjoern |
| Priority: | P2 | ||
| Version: | 1.2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | other | ||
| Bug Depends on: | 44386, 43325, 45029, 46404 | ||
| Bug Blocks: | |||
|
Description
Curt Arnold
2007-09-05 10:22:15 UTC
Could we release the Receivers sub-projects and zeroconf before hand though? The natural time for 1.2.16 in my opinion (barring any emerging critical issue) would be simulatenous with the initial release of Chainsaw 2 based on log4j 1.2.x which would imply at the same time or after receivers or zeroconf are released. Seeing nine months later that 1.2.16 has not been released, it might be appropriate to have a short list what needs to be done where? Am I correct in assuming that it is primarily ChainSaw issues that are pending? I don't think anything is preventing log4j 1.2.16 from being finalized. I can't think of what else was planned to go. I wouldn't mind having 1.2.16 out in the wild as it is, because then some of the sub-projects can also be voted on for release. Perhaps Curt can comment on what else he might have had in mind to do? Not that it's terribly related to this bug (other than the 1st comment was re: chainsaw being ready), but I have an in-progress Chainsaw change to add hide/show of drag & drop tab as a preference...it gets in the way if you don't use xml layout. If this doesn't go, that's ok...the prefs logic is a bit to work through but it's close.. I am looking through the current log4j issues so we can put those aside which is not holding up this release. Feel free to help. I have created bug 45527 as an "umbrella-issue" and set this issue to block it (meaning that we should agree first :) ) If there is work needing to be done, that is not covered by an issue, please create issues for them as it helps others to see what is going on. One such would be to get the official build process to be simply "extract from SVN, run "maven foo:bar" and deploy the resulting libraries. *** Bug 45527 has been marked as a duplicate of this bug. *** 1.2.16 is out |