search

forsyde / forsyde-deep

Other
1 stars 2 forks source link

Migrate this repository to the public github #28

Closed HWoidt closed 6 years ago

HWoidt commented 8 years ago

Issue by HWoidt Wednesday Feb 03, 2016 at 18:25 GMT Originally opened as https://gits-15.sys.kth.se/ingo/forsyde-deep/issues/28

  1. When to do this?
  2. How do we transfer the issues? maybe: https://github.com/michaelgwelch/migrate-issues
    • [x] Fix FSVec problems #23
    • [x] stabilize
    • [x] review licence and change if needed
    • [x] move code
    • [x] migrate issues
    • [x] migrate type-level and parameterized-data
HWoidt commented 8 years ago

Comment by ingo-sander Wednesday Feb 03, 2016 at 18:59 GMT

Regarding the when, I think we need to have a more stable version first. FSVec should be fixed.

HWoidt commented 8 years ago

Comment by ingo-sander Tuesday Feb 09, 2016 at 12:50 GMT

What is the status of the ForSyDe.Deep now? Do I understand it correctly from the ForSyDe issue tracker that the issue with FSVec (#23) works now?

What is left to do for the release?

  1. I see that #4,#6,#7,#10,#24 are still marked as bugs. How easy are they to fix? Some of these issues are marked with 'help wanted'. Can you be more precise in the individual issues?
  2. How about #30? Shall it be fixed before the release?
  3. How about the integration with Travis CI? Should this be done before the release?
HWoidt commented 8 years ago

Comment by HWoidt Friday Feb 12, 2016 at 17:25 GMT

Yes #23 is fixed now and conversion works.

regarding 1:

The help wanted tag marks all the issues that have a relatively small scope and should be doable by a beginner not familiar with the code base. I thought this would be a good idea for interested students to help the development.

regarding 2:

30 => I commented on this in the ticket. This is some significant work for which I am not sure about the actual benefits. Are there users stuck with 7.8?

regarding 3: I would say we publish the sources on github, configure travisCI and stabilize it a bit, then do the actual release announcement and upload to Hackage.

HWoidt commented 8 years ago

Comment by ingo-sander Friday Feb 12, 2016 at 19:26 GMT

regarding 1: Do you want to fix #4 soon? regarding 2: #30 is not really needed, once the version for 7.10.3 works. regarding 3: Good plan. How can I move it to github (including the issues)?

HWoidt commented 8 years ago

Comment by ingo-sander Friday Feb 12, 2016 at 19:29 GMT

I also think that we should not any longer use version numbers like 3.2. It would be better to be more modest and use for both the shallow and the deep version, a version number 0.4 or something (downgrading it one level). What do you think?