Re: Checkins without JIRA's

2014-01-13 Thread Peter Ent
On 1/10/14 6:17 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Hmm. That wouldn't be my preference. Do other projects do this? In general yes but each project is different and can do what they want basically. The framework is still pre-alpha and I would find it very difficult to

Re: Checkins without JIRA's

2014-01-13 Thread Erik de Bruin
Agreed. There is just too much to do and too little time. I pick and chose what to work on based on how I feel like (do I want to copy paste a kazillion license headers, or do I want to deep dive into the compiler to fix a bug?) and I'd rather not have to waste time to first enter a JIRA ticket

Checkins without JIRA's

2014-01-10 Thread Justin Mclean
Hi, I've noticed that Alex and Peter tend to work on something for a while and then the first we know about it is when it's checked in. A possibly better process would be to raise each change as a new feature/improvement in JIRA, that way there would be better visibility to what's been worked

Re: Checkins without JIRA's

2014-01-10 Thread Alex Harui
Hmm. That wouldn't be my preference. Do other projects do this? JIRA is not my favorite tool. Regarding history, the commit logs should be sufficient. What kind of information are you really looking for? Was it not clear that I've been working on the installer and ant_on_air for a while now?

Re: Checkins without JIRA's

2014-01-10 Thread Justin Mclean
Hi, Hmm. That wouldn't be my preference. Do other projects do this? In general yes but each project is different and can do what they want basically. JIRA is not my favorite tool. Regarding history, the commit logs should be sufficient. For people not familiar with the code or who are