Bug postings on xaraya 1.2 release bugs
jojodee <jojodee-8nna1qhvBBM9QQeoy3GH/[email protected]> Wed, 15 Apr 2009 13:22:17 +0930
| Newsgroups | gmane.comp.cms.xaraya.devel |
|---|---|
| Organization | Xaraya |
| Message-ID | <[email protected]> |
Dracos You asked people to address the bugs for Xaraya 1.2 that you posted. I posted in the bugs were ones I logged myself in that list, and also in bugs that i noticed were fixed some time ago in my own private branch, when changes were not permitted in the xaraya 1x branch (either before 1x for reasons, or after due to the focus on 2x). You are now, implementing some type of focused attack on any of my posts there. I've done a lot of work on the bugs that you want for 1.2, it's been in openly available code for some time, I don't have the time now because you've decided it's OK now to post to 1x - to go through and tease it out just for you. If you want the code, then review it and use it, else not then please desist on your misguided, self indulgent endeavours currently in bugzilla, replying the way you are to my legitimate bug posts. I made legitimate posts on the bugs you requested people to focus on. If you don't want that, you dont' want the code, then don't ask. As for the list of bugs for 1.2 release: 1. At least 2 are not bugs, the features exists 2. At at least 3 possibly 6 that are probably already implemented some years ago in the core. 3. There are at least 10 that i can see off hand are imlemented during the freeze on 1x work and in my private branch (calling it that because you don't like mention of the word xarigami branch but in fact it has other people's contributions other than just mine) 4. There are some that will not be fixed unless there is major changes in the underlying code of block layout, or the server files, or the blocks module. Some of this was so major it was left for 2x. Is this what you want for 1.2? Is it worth doing this in 1x when 2x is pending? 5. There are non-core module bugs in that bug list. Previously for a xaraya release we have focused on core and core module distribution bugs. The other modules and issues related have not usually been included in the release milestones. Is this an oversight or are you changing this now? Finally, the last word here regarding 1x code changes was that there was a release pending, and that no changes to the core API were to be accepted and any already done were to be reviewed and removed if not suitable. I think you need to clarify. Jo -- http://xarigami.com :: Creative web development with Xaraya http://2skies.com :: Open source hosting and development