precisely,
log it to the tracker (with patch/pull request) should be the standard
answer
On 27/09/2010 9:26 AM, Daniel Hölbling wrote:
+1 from me.
I've been thinking about doing the same for Dotless since I find we
loose too many feature requests and bugs in the discussion group at
times..
On Sun, Sep 26, 2010 at 11:26 AM, John Simons
<[email protected] <mailto:[email protected]>> wrote:
Yep I'm ok with everything :-)
Cheers, John
On 26/09/2010, at 13:50, Krzysztof Koźmic
<[email protected] <mailto:[email protected]>>
wrote:
While we're on the topic.
I think we should take greater advantage of the issue tracker we
have. Most notably, I like how NHibernate project uses their JIRA
to log every bug, every enhancement and every new feature they
release. This gives nice trackability and you can nicely follow
what's happening on the project.
It has happened a few times in the past to myself (and I'm
guessing not just me) that someone sent me an email or stared a
thread on the google gorup, asking for a fix or improvement and
it got lost or forgotten and never released. I would like to
avoid that.
I started doing similar thing to what guys at NHibernate project
do for the most recent Windsor 2.5.1, and I would like to *make
it part of our development standard, to make sure we have every
piece of work we do in the issue tracker*.
Also when we commit please put issue id in the commit message.
YouTrack/TeamCity integration nicely can link revisions/builds
with the issues together.
Thoughts? Objections? Ideas?
cheers,
Krzysztof
--
You received this message because you are subscribed to the
Google Groups "Castle Project Development List" group.
To post to this group, send email to
[email protected]
<mailto:[email protected]>.
To unsubscribe from this group, send email to
[email protected]
<mailto:[email protected]>.
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
--
You received this message because you are subscribed to the Google
Groups "Castle Project Development List" group.
To post to this group, send email to
[email protected]
<mailto:[email protected]>.
To unsubscribe from this group, send email to
[email protected]
<mailto:castle-project-devel%[email protected]>.
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
--
You received this message because you are subscribed to the Google
Groups "Castle Project Development List" group.
To post to this group, send email to
[email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
--
You received this message because you are subscribed to the Google Groups "Castle
Project Development List" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
