regular releases

[paulvi]

As you may have heard from different source regular and often releases are considered good practice. Even with alpha/beta there should be some reference points for users,
and one more reason for developers to keep thing clean and ready for release.

[angelozerr]

At first, AngularJS Eclipse + Tern IDE are build with couldbee and each commit start a job https://opensagres.ci.cloudbees.com/job/angularjs-eclipse/ which create the updat esite.

But I will plan soon a release of AngularJS Eclipse.

Perhaps it could be good to provide a wiki page for each releases to explain what contains the release?

[paulvi]

Perhaps it could be good to provide a wiki page for each releases to explain what contains the release?

Yes. Using GitHub releases tab or GitHub issues milestones, or just history file as wiki.

http://www.nodeclipse.org/history

[paulvi]

Can there be release before April ?

[angelozerr]

Yes. Using GitHub releases tab or GitHub issues milestones, or just history file as wiki.

Thank's for your info.

Can there be release before April ?
Yes, we plan with Pascal to create a release. Perhaps this month (March).

[pascalleclercq]

Will do It soon, possibly tomorrow evening if we all agree.

[angelozerr]

For me, there is no problem. I think before creating release, we must :

• do Less categories in update site #31 for angular eclipse and tern ide.
• decide version (1.0.0?) Spread the word and binaries #28 (comment)

@pascalleclercq when you will do that, I will check the update site and if it works, it will be ok for me.

[angelozerr]

I close this issue. I don't know today when new release of tern ide will be available (I have a lot of idea to improve it, but there is a lot of work too).

[paulvi]

That is work regular releases are about, no matter big or small changes they are released regularly: e.g. monthly, bi-monthly and so on., but it is know when next release is coming.

That lets keep quality good and not do "oh, I fix that before release (that I don't know when)"