Moving towards v1.0 ...

[b2z]

So guys what is the current state? What issues/problems we need to resolve?

Here is my proposal plan for the nearest time:

1. Stabilize the code base: review/merge all the PRs that we have currently, try not to issue new PRs against the code base (only for fixes). Fix current issues/bugs.
2. Call for a testers. Fix the issues found.
3. Determine the features that are stopping us from v1 release and implement them.
4. Test again. Fix again.
5. Ready for the launch.

And one more thing to note for the devs - do not forget to assign yourself for the issue to avoid a duplicate work.

Thoughts??

[eddieajau]

I think there are three more things we need to do:

1. Write a test plan for what the JIssues application is supposed to do (basic UI operations).
2. A synchronisation test plan for how things done on Github affect the JIssue application and visa versa.
3. Nailing down the workflow that we'll be using going forward with Github/JIssues

I suggest putting those in the wiki and keeping them up to date. The test plans can eventually be converted to system test. The workflow, however, seems to be a ball that is just kicking around and around. If someone can tell me "here is the definitive discussion on workflow that is going to lead to a decision" I will help.

[b2z]

Code base is pretty stable now. No major issues currently. Now we need to determine the features that are stopping us from v1 release and implement them.

Any help is appreciated. Thank you!

[betweenbrain]

As far as I can tell, things look fairly stable here. The question that I need to ask is if the current state of JTracker is better than Joomlacode. If it is, I suggest that we start discussing the plan to cut over. As soon as we have more people using this, I'm sure more bugs will surface, as well as help to solve them and improve the system.
You may blame the J!Tracker Application for transmitting this comment.

[b2z]

Yeap you are right we need more experienced JoomlaCode users to define what is missing in JTracker now.

[wilsonge]

The biggest issue to me is that I can't easily tell whether an issue is RTC (etc). The only way is to look down the comments and count up the tests and make sure they all apply to the latest version of the patch etc. etc.

[mbabker]

The webhooks are programmed to handle opened and closed statuses only. In
the UI, a status field with all of the statuses we currently use is
available.

On Wednesday, February 12, 2014, George Wilson notifications@github.com
wrote:

The biggest issue to me is that I can't easily tell whether an issue is
RTC (etc). The only way is to look down the comments and count up the tests
and make sure they all apply to the latest version of the patch etc. etc.

Reply to this email directly or view it on GitHubhttps://github.com//issues/253#issuecomment-34933767
.

[pjwiseman]

PW#1 When I was actively testing (something I hope to get back to one day), I started with "Issues that needed one further test". There doesn't appear to be a way to filter those "I'm almost there, just need a little further push" issues in JIssues.

PW#2 This might have been resolved, but last I looked (many months ago), JIssues only included GitHub issues. Is there an intend to import the current JoomlaCode-only issues? If not, what's the plan for migrating those?

PW#3 There's no "this one is easy" tag to help newbies get started on processing issues?

[mbabker]

PW#1 When I was actively testing (something I hope to get back to one day), I started with "Issues that needed one further test". There doesn't appear to be a way to filter those "I'm almost there, just need a little further push" issues in JIssues.

Filters are still a work in progress. We have some stuff in place for really basic functions, but more advanced "canned queries" aren't set up yet.

PW#2 This might have been resolved, but last I looked (many months ago), JIssues only included GitHub issues. Is there an intend to import the current JoomlaCode-only issues? If not, what's the plan for migrating those?

A migration plan hasn't been discussed yet. We could use the built in API of JoomlaCode to move items over (which in turn opens GitHub issues) or we could just do something so that new items can't be added there but open items are worked through. It's going to require someone to triage JoomlaCode too; there's a lot of stuff there that hasn't been touched in ages.

PW#3 There's no "this one is easy" tag to help newbies get started on processing issues?

We have a field for it in the database and on the item edit view, and a badge should display in the item view. However, it looks like the save function isn't properly working at the moment as I tried to flag http://issues.joomla.org/tracker/joomla-cms/3088 as easy but it didn't take. Real estate on the main list view though is at a premium so we have to figure out the best way to show key data there compared to what we have on JoomlaCode now.

[b2z]

PW#2 This might have been resolved, but last I looked (many months ago), JIssues only included GitHub issues. Is there an intend to import the current JoomlaCode-only issues? If not, what's the plan for migrating those?

A migration plan hasn't been discussed yet.

Here is the proposal of @eddieajau for cutting over JoomlaCode.

Real estate on the main list view though is at a premium so we have to figure out the best way to show key data there compared to what we have on JoomlaCode now.

That's what I am talking about in #234. We need to redesign the main layout for better UI.

@pjwiseman we do remember about better filtering - your #6 is still not closed ;)

[elkuku]

"The truth is there's no perfect time for a transition like this one, but I believe now is as good a time as many, and there are a number of reasons why."

-Rackspace, CEO Lanham Napier source

[b2z]

Tracker is launched.

[wilsonge]

parties

[elkuku]

🎉