Skip to content

[Task] make maintenance 0.3 release #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
paulvi opened this issue Apr 30, 2013 · 16 comments
Closed

[Task] make maintenance 0.3 release #1

paulvi opened this issue Apr 30, 2013 · 16 comments
Assignees

Comments

@paulvi
Copy link
Member

paulvi commented Apr 30, 2013

After @damschmideg blesses migration to Nodeclipse adamschmideg#13 , build and release without new features just as starting point.

There are also some infrastructure issues to be solved.
adamschmideg#12 Compilation is difficult

@adamschmideg
Copy link
Member

blessings given

@pulse00
Copy link
Member

pulse00 commented May 16, 2013

Hi everyone!

I'd like to propose the following tasks for the maintenance release:

  • Upgrade to Xtext 2.4
  • Add maven / tycho support
  • Refactor namespace to org.nodeclipse.coffeescript
  • Setup CI

As for the CI, we could use travis-ci.org or i can also add a project to the PDT-Extensions Jenkins instance.

@paulvi
Copy link
Member Author

paulvi commented May 16, 2013

Well, initial maintenance 0.3 release idea was just to build it (at new place to check everything is OK)

Then proposed steps could be in 0.4 .

I totally agree to 1,2,4 for roadmap.
We should use latest version of XText.
Maven/Tycho would be nice to use later with nodeclipse-1 . @tomotaro1065 please take notice

For 3, I like it. It would set standard for the organization. However Adam @adamschmideg should not be against that.
(He asked his company to be reference in some way. Hope we don't delete some copyright notices)

Robert, please don't hurry to delete "Looking for owner" in readme.
Let it be for a month. Hopefully someone more would join. We are definitely in early transition phase.

I configure write access for you to this repo. If you want to experiment, I propose create own fork instead of branches.

Please wait for enough communication to happen.

@pulse00
Copy link
Member

pulse00 commented May 16, 2013

@paulvi no worries, i won't commit anything in the repo, i've created my own fork for now. I'll have plenty of other things to do the next few weeks, so there's no hurry here.

The above points of course are just suggestions. I'm fine with the current namespace, i just thought it would be concise to have the same namespace over all projects of the organisation.

Regarding maven/tycho: It has prooved to ease maintenance a lot for my projects, so i'd highly recommend it.

@paulvi
Copy link
Member Author

paulvi commented May 16, 2013

@pulse00 Totally agree.

@pushkar85 Please join us here.

@ghost ghost assigned pulse00 May 16, 2013
@tomotaro1065
Copy link
Member

@paulvi I know Maven, but not know Tycho. I will try it when I have time.

@paulvi
Copy link
Member Author

paulvi commented May 17, 2013

@tomotaro1065 me too, I know maven, not Tycho

This link I added before in README http://wiki.eclipse.org/Tycho/Reference_Card

@pulse00 Robert, can you recommend some materials?

@pulse00
Copy link
Member

pulse00 commented May 17, 2013

can you recommend some materials?

I've mainly used what's available in the Wiki you've linked. It's actually pretty simple. Tycho basically provides:

  • Eclipse packaging types
  • Resolve OSGI dependencies (p2 repositories) during the build
  • Create maven artifacts ready for p2 deployment

You can have a look at an example here:

@pushkar-g
Copy link

@paulvi @tomotaro1065
I am familiar with Tycho/ Maven. I can take up that task.

@tomotaro1065
Copy link
Member

@pushkar85

Thanks a lot. Great. We'll leave it to you.

2013/5/18 pushkar85 [email protected]

@paulvi https://github.com/PaulVI @tomotaro1065https://github.com/tomotaro1065
I am familiar with Tycho/ Maven. I can take up that task.


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

http://www.nodeclipse.org/

blog: http://d.hatena.ne.jp/tomotaro1065/
twitter: @tomotaro1065

@paulvi
Copy link
Member Author

paulvi commented May 17, 2013

Actually it was Robert who said he is going to do it for Coffee-Eclipse.

And then it is also good for Nodeclipse-1.

I hope Robert & pushkar85 can go ping pong on Coffee, just as me & Tomoyuki on Nodeclipse-1.

@pulse00
Copy link
Member

pulse00 commented May 17, 2013

@paulvi i'll do it for the coffeescript plugin, no problem.

@paulvi
Copy link
Member Author

paulvi commented May 17, 2013

At this point I think Skype would be better. My Skype ID pverest.

@pushkar-g
Copy link

Ok then I will do it for Nodeclipse.

@paulvi
Copy link
Member Author

paulvi commented May 17, 2013

We should do it for one plugin, and then exactly the same way for other.

#2 & #3 are created; for both @pulse00 Robert is assigned.
Robert please be as owner of coffeescript-eclipse.
@pushkar85 please get co-understanding with Robert.

Everybody don't hurry to do. Please talk well.
I recommend Skype, then email, then ,when it goes into details, make an issue.

paulvi added a commit that referenced this issue May 18, 2013
@paulvi
Copy link
Member Author

paulvi commented Aug 17, 2013

Closing after 0.3 release though only migration to maven/tycho was finished from the task mentioned by Robert

  • Upgrade to Xtext 2.4
  • Add maven / tycho support
  • Refactor namespace to org.nodeclipse.coffeescript
  • Setup CI

@paulvi paulvi closed this as completed Aug 17, 2013
@paulvi paulvi mentioned this issue Aug 17, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants