Re: Bug postings on xaraya 1.2 release bugs
Marty Vance <[email protected]> Tue, 14 Apr 2009 23:41:11 -0600
| Newsgroups | gmane.comp.cms.xaraya.devel |
|---|---|
| Organization | Xaraya |
| Message-ID | <[email protected]> |
jojodee wrote: > 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). Fixes in your "private branch" (which I assume means your Xarigami fork) are irrelevant vapor as far as Xaraya is concerned *until you push them*. > > 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. You see it as an attack because you want to be the victim. I do not enjoy repeating myself, but you seem not to be listening. Any work you have done on these bugs which is not available via mt.xaraya.com is irrelevant to Xaraya, and is not part of Xaraya. Likewise, I don't have the time to "tease it out" either. Perhaps someone else does. Regardless, if someone did do you that favor, I would not be suprised if you later claimed the code was stolen, or not credited properly. I am not taking your bait. I take your use of the phrase "just for you" as evidence that you consider this ongoing tête à tête to be a personal matter between you and I, and despite statements to the contrary, you do have personal issues with me, which I have strongly suspected for years now. If your issues with me now define your relationship with Xaraya, then I suggest it is beyond time for you to pursue other efforts. > > 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. NO. If anyone wants specific fixes to appear in Xaraya, it is their responsibility to push it or submit a patch. If you don't have time to extract fixes from *your* repo, assume no one here has that time either. Although, you do seem to have the time to troll through our Bugzilla, forums, and mail list... time which could be better spent extracting *your fixes* from *your repo* and pushing them. > > 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. Are you not reading my comments? They should be clear: IF YOU HAVE A FIX, PUSH IT OR SUBMIT A PATCH. If you would rather keep taunting this community, I suggest you sit down and enjoy a nice tall glass of STFU instead. > > As for the list of bugs for 1.2 release: > > 1. At least 2 are not bugs, the features exists Which ones? > > 2. At at least 3 possibly 6 that are probably already implemented some > years ago in the core. Which ones? > > 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) Which ones? Again, your "private branch" (Xarigami fork) is irrelevant to Xaraya. Regardless of who has contributed to it, it's still a fork. > > 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? In case you missed it in the forum post of the bug list, some of these bugs may be assinged resolutions other than "fixed". > > 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? Which ones? Then this list needs to be triaged. > > 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. I think you need to read: ------------------------------- Subj: 1x (aruba) is no longer in maintenance mode Date: 13 Mar 2009 00:36:08 GMT Aruba is now accepting bugfixes. Any patches targeted to specific bugs known in Bugzilla should be pushed or submitted to Bugzilla as an attachment to the bug. Patches are vapor until they exist in the repository or in Bugzilla. A roadmap for aruba is being worked on, which will commence with planning a 1.2 release. The previous 1.5 plan is scrapped. Until the roadmap is complete, aruba is accepting bug fixes only. Any API and/or database changes which have been pushed to com.xaraya.core since 1.1.5 are subject to review, and may be reverted pending QA assessment. No further API or database changes will be accepted until the roadmap is worked out. ------------------------------- News flash: the roadmap for 1.2 has been worked out in a rough form, published, announced, and the discussion/addition period has ended. The milestones on it will be fleshed out in specific discussions beginning shortly. If you continue to insist on wasting the time of everyone here, I implore you to follow through on your threats of leaving the project. > > Jo >