#11950 closed update (fixed)
UPDATE: rasqal-0.9.13 -> rasqal-0.9.14
| Reported by: | lyle.johnson@… | Owned by: | lyle.johnson@… |
|---|---|---|---|
| Priority: | Low | Milestone: | |
| Component: | ports | Version: | 1.4.3 |
| Keywords: | Cc: | markd@…,lyle.johnson@… | |
| Port: |
Description
There's a new version of rasqal.
Attachments (1)
Change History (7)
Changed 18 years ago by lyle.johnson@…
comment:1 Changed 17 years ago by markd@…
| Cc: | markd@… added; macports-dev@… removed |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Oops. I didn't notice you had it assigned to yourself before I committed it. Did you want this to be committed?
comment:2 Changed 17 years ago by lyle.johnson@…
Yes, I wanted it committed; thanks. I may have forgotten how this process should work. I assigned it to myself because I'm the maintainer of the port. I also Cc'd macports-dev@… with the intent that someone with committer privileges would pick it up. I knew that it still hadn't been committed, but it wasn't urgent and I didn't want to bug anyone about it.
Should I just Cc a specific committer (like you) in the future, or what's the best way to handle it?
comment:3 Changed 17 years ago by markd@…
Our rules are sort of loose no doubt; rather than you unfamiliar with thm. And then I don't like rules anyway. :) It is just that sometimes committers assign tickets to themselves when they want to handle it when they get a chance. Since I wasn't sure if you were a committer or not I wondered after I committed it if that was what you intended, but since you also cc'ed the list that probably should have been my clue that you weren't holding it for yourself. I think the rules are none too firm here, at least from my perspective, and we could discuss this on the list, but I would say that it might be slightly better not to asign it to oneself for non-committers, because it when people are scanning the list fortickets to work on it might get passed over as "being dealt with" or "don't mess with it" when that is not the case. But truth is, you often have to bug the mailing list in any case because trac is such a blunt instrument for what we use it for that tickets get overlooked with great frequency anyway. So whatever you do, don't worry about pinging the list if your contributions aren't getting committed.
comment:4 Changed 17 years ago by lyle.johnson@…
Thanks for the help and advice, Mark. I'll try to be a bit more vocal in the future when I need help getting something committed. ;)
comment:5 Changed 16 years ago by jmroot (Joshua Root)
| Type: | enhancement → update |
|---|
Updated Portfile for rasqal-0.9.14