On 6/9/06, Don Brown [EMAIL PROTECTED] wrote:
Also, I'll be
moving items from our TODO lists over to issues so be prepared for more
emails :)
Which TODO lists?
This JIRA report [1] should contain everything we are planning for in
the 2.0.0 release slated for August.
For 2.x, I'd like to
On 6/12/06, Ted Husted [EMAIL PROTECTED] wrote:
The plugin should pickup any unadorned reference to a JIRA ticket. I
tend to put it by itself on the first line, just to be sure, followed
by the usual commit message. (Though, it doesn't look like the plugin
is working quite yet. )
It was
Ted Husted wrote:
On 6/9/06, Don Brown [EMAIL PROTECTED] wrote:
Also, I'll be
moving items from our TODO lists over to issues so be prepared for more
emails :)
Which TODO lists?
I'm thinking of all the rough spots and that short list of features on the
release plan.
This JIRA report [1]
On 6/12/06, Don Brown [EMAIL PROTECTED] wrote:
I'm thinking of all the rough spots and that short list of features on the
release plan.
I setup issues for the short list, but not every rough spot. Anyone
who is ready, willing, and able to work on any of the others is
welcome to create the
On 6/12/06, Ted Husted [EMAIL PROTECTED] wrote:
For 2.x, I'd like to take this one step farther and ask that ALL SVN
commits to Action2 refer to a JIRA issue, even if we have to create a
new one.
But, we should still try to include a meaningful log message about
each commit. The reference to
On 6/12/06, Ted Husted [EMAIL PROTECTED] wrote:
On 6/12/06, Ted Husted [EMAIL PROTECTED] wrote:
For 2.x, I'd like to take this one step farther and ask that ALL SVN
commits to Action2 refer to a JIRA issue, even if we have to create a
new one.
But, we should still try to include a
Perfect! I agree, we shouldn't make tickets for everything yet, but let
developer and user demand drive it. I know turning all this brainstorming talk
into specific tickets has helped me to better organize my time and visualize
where we are in the development process. Thanks for the hard
Speaking of reviewing the commit messages... can we get FishEye set up? I'd
love to use RSS to review the commits :)
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=33879messageID=66381#66381
I changed the JIRA version to 2.0.0 and have started to pair down the
actual tickets we are signing up to resolve for 2.0.0. Please go
through the list of those improvements moved to Future and see if there
are any you'd be willing to tackle for this release. Also, I'll be
moving items from
