Bugtracker, new repo, Google group

[i.pals...@jdi.nl]

Hi,

Some issues we need to consider : 

- Do we keep using the playone group, or do we use the new name ? I've created the ionstorm group just in case

- There is a large issue list in the Play 1 lighthouse issue tracker. I want to stick to the GitHub issue tracker for now, unless someone has

  a compelling reason to use something else. I can arrange a JIRA license if there are a lot of Pro-JIRA people here. Are we going to transfer all open issues,

  or do we start from scratch

- The new repo : I've created the IonStorm organisation on Github.

The repo : https://github.com/ionstorm/ionstorm

I'm going to stop sending pull requests to the playframework/play repo myself.

To keep the code quality in order, code commits should go through pull requests, even if you have write access to the repo.

Regards,

     Igmar

[i.pals...@jdi.nl]

- Do we keep using the playone group, or do we use the new name ? I've created the ionstorm group just in case

New group in place in case we want to switch : ionframework

 

- There is a large issue list in the Play 1 lighthouse issue tracker. I want to stick to the GitHub issue tracker for now, unless someone has

  a compelling reason to use something else. I can arrange a JIRA license if there are a lot of Pro-JIRA people here. Are we going to transfer all open issues,

  or do we start from scratch

- The new repo : I've created the IonStorm organisation on Github.

The repo : https://github.com/ionstorm/ionstorm

Final repo : https://github.com/ionframework/ion

Regards,

 

      Igmar

[i.pals...@jdi.nl]

 

- There is a large issue list in the Play 1 lighthouse issue tracker. I want to stick to the GitHub issue tracker for now, unless someone has

  a compelling reason to use something else. I can arrange a JIRA license if there are a lot of Pro-JIRA people here. Are we going to transfer all open issues,

  or do we start from scratch

We need to make a decision on this.

Igmar 

[Ivan San José García]

I think that all issues which are still opened in Lighthouseapp, should be transfered to GitHub or whatever will be the new bug tracker system. Because these issues aren't solved.

2013/2/22 <i.pals...@jdi.nl>

Igmar 

--
You received this message because you are subscribed to the Google Groups "playone" group.
To unsubscribe from this group and stop receiving emails from it, send an email to playone+u...@googlegroups.com.
To post to this group, send email to pla...@googlegroups.com.
Visit this group at http://groups.google.com/group/playone?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[green]

I prefer to start from zero as ion will have fairly big updates on top of play1 and might have incompatible changes even. Migrating all existing issue is less relevant, if people using ion and believe the old issue is still on ion, they can easily submit new issues (much easier than the original issue tracker) again.

[i.pals...@jdi.nl]

On Friday, February 22, 2013 8:41:28 PM UTC+1, greenlaw110 wrote:

I prefer to start from zero as ion will have fairly big updates on top of play1 and might have incompatible changes even. Migrating all existing issue is less relevant, if people using ion and believe the old issue is still on ion, they can easily submit new issues (much easier than the original issue tracker) again.

My thoughts exactly. Green, can you create issue for issues that need resolving ? I'm in an urgent need to het some coding done :-)

Igmar