Found 12 entries.
I’d just like to mention that cil v0.07 has had a belated release. It had a bit of work done to it (6 issues) back in January and February and since it’s been working fine for me since then, I thought it about time to release.
Please see the project page for cil for the download link and other information.
Note, the six issues that have been completed are (generated by `cil summary —is-closed —label=Milestone-v0.07`:
Labels: cil
Inserted: 2010-05-17 10:25 (3 months, 2 weeks ago)
Whilst I was away, there were a number of things cropping up that people wanted for Cil.
The two most interesting requests that people have submitted are:
.cil config filecil work commandThe 2nd idea strikes me as being really useful so thanks to Yanick for all of his ideas, keep them coming.
Both of the ideas above are good but there are just a few things I'll want to discuss with the authors. There were also some requests that I create a mailing list for Cil development - now done - so we can talk these things through.
Please join up if you are interested in Cil and where this little adventure might take us.
Finally, a big hello to everyone ... I'm back in the country so I'll see you all very soon.
Labels: cil, planet-catalyst
Inserted: 2008-09-05 00:45 (1 year, 12 months ago)
I'm amazed at the reception Cil is getting so far. Further news now is ...
... Cil has been made a featured project on GitHub's Homepaage (though you have to be logged out to see it).
I spoke with Tom Preston-Werner a couple of weeks ago about projects which help drive Git adoption and thought he would be interested in Cil. He told me he'd feature it on the front page of GitHub so thanks very much Tom, that's awesome.
My Ohloh stats on Cil are also looking good and will soon show that the project has already had 6 contributors, some of whom have jumped completely out of left-field.
Thanks to everyone for helping out so far.
Labels: git, cil, planet-geek, planet-catalyst, github
Inserted: 2008-07-31 21:28 (2 years, 1 month ago)
Cil has been through Debian Unstable and is now in Debian Testing.
If you didn't know, Cil is a command-line issue list which lends itself well to distributed bug tracking. It saves issues, comments and attachments locally and already there are some powerful features and ideas in it.
Cil v0.5.1 is now in testing and hopefully will be in the Lenny release. That particular version of Cil has all of the basic structure required to start using it and a number of great commands to help use it.
There is no v0.6 of Cil yet but there are a number of things planned. I added some initial abstractions about how Cil can integrate with various VCS systems and SamV has gone one step further and added some actual features which integrate even more to what I initial imagined. v0.6 will hope to tie up and pull together a number of loose ends around this whole area.
Further out, there are even more ideas on the horizon but I shall tell you about those closer to the time.
Some of you know I shall be off on my hols shortly so it may have to wait until after that but as I said, v0.5.1 is a nicely round and complete version to appear in Lenny. Have fun and happy hacking.
Labels: debian-lenny, cil, debian, planet-geek, planet-catalyst
Inserted: 2008-07-22 18:18 (2 years, 1 month ago)
There have been a number of good things things happening with Cil in the past week or so.
Just a few quick notes to start off with:
When writing Open Source Software, it usually feels good to be able to give something back but it also feels better when someone is helping you too. Francois deserves all the credit getting Cil into Debian and a lot of the credit for many other features already in Cil.
Now I just need to get my act together so I can contribute to email-reminder - I promise there will be patches before sunrise.
Labels: cil, planet-geek, planet-catalyst, dbts
Inserted: 2008-07-05 19:13 (2 years, 1 month ago)
This release has a number of new things and functionality.
Here's the short version of the changes, though there are quite a few since Saturday's release:
~/.cilrc config file, so set your UserName and UserEmail in there--is-mine which takes your email from your ~/.cilrcDocumentation has been made a little nicer too.
There are still lots more ideas to get through but I'm sure it'll slow down at some point. As always, thanks to those who provide me with inspiration and ideas, you know who you are.
Have fun, let me know how it goes and happy hacking.
Update: fix to packaging, patched to v0.4.1, see the main cil page for tarball details.
Labels: cil, planet-catalyst
Inserted: 2008-07-02 23:47 (2 years, 2 months ago)
Here's another release of cil for your perusal. Staying true to the "Release early, release often" mantra, I hope you have fun playing with it.
I'll quickly go through all the features in this release:
For example:
$ cil list --label=Type-Critical $ cil list --status=New $ cil list --assigned-to=andychilton-at-gmail-dot-com
(Note: --label and --status were in v0.2.1.) These can be combined too. For example, this is the command line I used to make sure there were no outstanding issues for this release of cil:
$ cil list --is-open --label=Milestone-v0.3
and opposite to that, for the changelog I could figure out what had changed since the last release by doing this:
$ cil list --is-closed --label=Milestone-v0.3
If I was on a big project, I'd probably cron something like this to send me an email each morning:
$ cil list --is-open --assigned-to=andychilton-at-gmail-dot-com --label=Priority-Critical
That's a pretty nice filter :-)
To be able to do some of the filters above (e.g. --is-open and --is-closed) cil now reads a config file and can determine which statuses and labels are valid. There are also lists to say which statuses are considered open or closed. Of course, if you want neither of features you can just turn them off (which is the default behaviour).
Cil saves it's issues, comments and attachments in the filesystem which isn't usually a good way for (slightly) relational data. The new 'fsck' command can help you figure out missing entities though. For example, if an issue is missing its comments or attachments and whether comments or attachments have been orphaned. It also runs some validation against each issue. Validation at the moment consists of checking statuses and labels in their respective allowed list.
Here is some example output you might see from this command (usually if you or someone else has not been tracking the right things):
=============================================================================== --- Issue c4fa2e27 ----------------------------------------------------------- * StatusStrict is turned on but this issue has an invalid status 'InProg' * LabelStrict is turned on but this issue has an invalid label 'Something' --- Issue 1f67bc27 ----------------------------------------------------------- * comment '8dfe256c' listed in issue '1f67bc27' does not exist * comment '99b20701' is listed under issue '1f67bc27' but does not reciprocate * attachment '29afc3ef' listed in issue '1f67bc27' does not exist =============================================================================== --- Comment 99b20701 --------------------------------------------------------- * comment '99b20701' refers to issue '893f7ea6' but issue does not exist =============================================================================== --- Attachment 37873839 ------------------------------------------------------ * attachment '37873839' refers to issue '8af89d74' but issue does not exist ===============================================================================
More validation checks will be in v0.4.
(Where 'entities' are issues, commands or attachments.)
As stated in a previous post, there is now bash completion for cil.
As I said earlier, I use a few command lines to let me figure out when I can release a version. For example, the next release is going to be v0.4.0 (barring any bug fixes to v0.3.0) so I tag all of the issues I want done for that release with Milestone-v0.4. This makes it easy to see what needs doing and what is already done:
$ cil list --is-open --label=Milestone-v0.4 $ cil list --is-closed --label=Milestone-v0.4
For example, an issue might have been added at some stage in the past, complete with labels:
$ cil add ... added issue 'cafebabe' ...
I usually commit the new issue to my VCS immediately. When I start working on it, I'll mark it InProgress, even if it is just locally. Sometimes I check this in too if it's going to be longer than a few hours:
$ cil status cafebabe InProgress
Once I've finished hacking on the issue and I'm happy with it, I set it to Finished and add a comment to say what I've done:
$ cil status cafebabe Finished $ cil comment cafebabe ... added comment 'decaf7ea' ...
I use Git for my VCS so prior to check in I stage all the working file changes but also make sure Git is tracking the issue properly too. It already knew about the issue file but I need to add the comment file that goes with it:
$ git add issues/c_decaf7ea.cil
Finally when I commit, I commit the code, the issue and the comment all together. In the message I usually put the text '(closes #cafebabe)'. This keeps everything together.
The next release of cil will be Milestone-v0.4 so I'll add that label to a few items I want in it. If there is something I want for the future but haven't roadmapped them yet (into v0.5, v0.6 etc) then I just put a Milestone-Future label on them so I know I want to do them but just don't know when.
Happy hacking and look out for v0.4 sometime in the next week or so.
Labels: cil, planet-geek, planet-catalyst
Inserted: 2008-06-29 11:05 (2 years, 2 months ago)
Another day, another feature added to cil. It's rocketing along.
I've never written anything for bash completion before (someone else has always done it for me) but I had a go at it tonight. After an hour and 15 I had it working quite well.
I was suitably impressed with the whole thing since even though I knew doing it for commands and/or options would be easy enough, I managed to do it for a few other things too (more later).
For example:
$ cil a<tab><tab> add attach $ cil s<tab><tab> show status summary $ cil --<tab><tab> --filename --help --label --path --status --version
That's all happy and nice but the following feature is the killer and will make working with issues a breeze. It also completes the actual issue/comment/attachment name, giving you the choice of the correct type where necessary.
Let's say your issues/ dir contains three issues, two comments and one attachment:
$ ls -1 issues/*.cil issues/a_85eceee9.cil issues/c_d8dd779f.cil issues/c_feb65ae7.cil issues/i_02ee35bd.cil issues/i_5c88cb30.cil issues/i_98203ce8.cil
When doing the following, it completes to one of the three issue names:
$ cil show <tab><tab> 02ee35bd 5c88cb30 98203ce8
as it also does for the other commands that act on issues (status, edit, comment and attach).
Another example would be for extracting attachments:
$ cil extract <tab><tab>
completes to:
$ cil extract 85eceee9
This is pretty good stuff already but I can already see that it can be used a lot more in the future...
Let's say you allow the following statusus in your issues: New, InProgress, Finished and WontFix. Then, setting the status of an issue would work like:
$ cil status 02ee35bd <tab><tab> InProgress Finished New WontFix
Really straightforward and really fast, which are basically two of the things I wanted cil to be from the start - I just didn't realise it would be so easy :-)
Seeing as I try and credit people where I can, thanks to Francois for the suggestion of adding bash completion. It's given me a chance to learn something new to me but very powerful.
Note: this feature is in Git and will be in the v0.3.0 release.
Labels: cil, bash-completion, planet-catalyst
Inserted: 2008-06-24 23:44 (2 years, 2 months ago)
Already there is a lot of news on the 'cil' front just 24 hrs after releasing v0.2.
I've had a number of enquiries about \l{cil|/software/cil.html} consisting of emails asking for help, emails giving advice but even better fixes from both \l{Francois|http://feeding.cloud.geek.nz/} and \l{Sam|http://vilain.net/}. Thanks guys.
Francois has also already uploaded v0.2.1 to Debian Sid for inclusion in Lenny. Many thanks Francois, it's a pleasure being able to work with someone so passionate and involved in Free Software. We all have lots to learn from you.
Anyway, I'd just like to say that v0.2.1 released earlier tonight had the dependency on Term::CallEditor removed to simplify a couple of things. Also, there really wasn't that much code in there anyway.
If you get the HEAD of the cil git repo, you'll already get some new funky features such as the following:
$ cil list --status=New $ cil list --label=Release-v0.2 $ cil list --label=Type-Enhancement
These, of course, can be combined:
$ cil list --status=InProgress --label=Milestone-v0.3
and you can also use these same filters with the summary command.
From issue #85eceee9, there are also plans to have something like the following too:
$ cil list --assigned-to=andychilton-at-gmail.com $ cil list --has-attachments --has-comments $ cil list --is-open $ cil list --is-closed
(These last two will only happen when there is config to say which Statuses are Open/Closed.)
I'm liking these filters already and with the new ones above it'll be great. Heck, I'm even thinking of cron'ing various filters so I know what I have to work on each day :-)
I have also added an issue, #98203ce8, which describes how to add proper searching to cil. This will supplement the above filters quite nicely.
BTW: I have searched and searched and searched for a nice, small and instant indexing system within the Debian repos. I've tried a couple of things which didn't quite work how I wanted it, so if anyone has any ideas, I'd love to talk to you so get in touch.
e.g something like this would be fantastic:
$ cil reindex $ cil search 'Project Blah refactoring' $ cil search 'screenshot table formatting'
Then we'd just list the issues found. It should be very simple with no setting up (except inside cil itself.) If git can 'init' and cil can 'init' then search should be able to set up real quick too.
I'm already using cil to track itself and I'll be shortly adding it to most of my other little projects too. I'm already getting quite competent at getting at the issues, adding, editing them, making sure they're in the repo and all of that jazz. It's coming together quite nicely.
Labels: cil, debian, planet-catalyst
Inserted: 2008-06-24 01:03 (2 years, 2 months ago)
I'm happy to announce that cil v0.2.0 is now available for download.
When I released v0.1.0 it was a test release for two reasons:
While (1) didn't happen, (2) did. I got lots of feedback even though no-one was using it. I did tell people it wasn't quite where I wanted it to be but this release changes all that.
Now it has all the makings of a tool which can just get better over time. Obviously it being v0.2, there are some things it is lacking but as it is, it's perfectly usable and nicely contained.
Some new features of cil v0.2 (over v0.1):
So far, most of the commands I added to cil were quite obvious but already there are some ideas for commands to allow you to work a lot faster. Such as:
$ cil status ISSUE Finished
Quite neat huh?
See cil for more information and also see this cil example for more of an idea about what cil can do.
Before I sign off I'd just like to point out one commit I did earlier today. My vision for cil is so that you can keep your bug tracking inside your repository. This means you can do things that weren't possible before. For example, closing the bug along with the commit(*).
This commit for example shows you that along with the fix, the bug gained an additional comment and the issue was closed, all in the same transaction. That's pretty cool.
So guys, go and have a play with this one. Thanks to Nigel, Francois and Martyn for allowing me to bounce ideas off you. And please, keep those ideas, suggestions, feedback and more importantly, patches, coming ;-)
(*) Yes, I know you can link your version control with your bug tracking system - usually with sticky-tape and superglue - but when they're in the same place, it's much easier :-)
Labels: cil, planet-catalyst, distributed-bug-tracking
Inserted: 2008-06-22 17:48 (2 years, 2 months ago)
This month has been hectic. Last month was mad too because I moved house. Work has been crazy recently too.
This month, I signed up for doing a novel. Seeing as I am a founder member of KiwiWriters, I have to do it. So far, I haven't managed to get into it yet but then finally, when I thought work would settle down, it went beserk again. Hopefully it will settle down sometime soon otherwise I'll never get this thing written.
I'm happy and settled into the new flat now though so that helps. Finally I can see the carpet which is always a bonus.
And then, when I thought I'd be able to get into my novel for SoCNoC, I somehow volunteered to do a talk at PerlMongers tomorrow night (Tuesday). Silly me.
Then again, I've just written the talk and I'm happy with it. It's only short but I'm hoping to open it out into a discussion at the end of the presentation. It's about my idea of a distributed issue tracking program, initially conceived as 'cil'. There are already a few people interested in it including both Nigel and Francois so hopefully, they'll ship me patches (hint hint ...) though their ideas have already been immensely invaluable. Thanks lads, it's always a pleasure prying into your brains.
Labels: cil, planet-catalyst, distributed-issue-tracking
Inserted: 2008-06-10 00:12 (2 years, 2 months ago)
Wow, it's been busy recently. Just thought I'd keep you abrest of what's been happening.
I've been:
As you can see, I'm liking Git :-)
Labels: git, cil, zaapt, debian, kiwiwriters, socnoc
Inserted: 2008-05-07 22:15 (2 years, 3 months ago)