Welcome to the developer’s discussion channel for the Ceylon programming language. This is where we yell at each other when things are broken again; while it’s a public channel, we consider it more internal than ceylon/user, and won’t control our speech as much here. Enter with caution :)
This document:
https://projects.eclipse.org/projects/technology.ceylon/reviews/creation-review
Says, in section "Project Scheduling":
The initial contribution will arrive in Q2, 2017, with a first release soon after. It is unclear whether the first release will be named 1.3.3, or 1.4.0. (The Eclipse requirements with respect to package naming might require a break to binary compatibility, thus resulting in a bump to the minor version number.)
https://projects.eclipse.org/projects/technology.ceylon/reviews/creation-review
Says, in section "Project Scheduling":
The initial contribution will arrive in Q2, 2017, with a first release soon after. It is unclear whether the first release will be named 1.3.3, or 1.4.0. (The Eclipse requirements with respect to package naming might require a break to binary compatibility, thus resulting in a bump to the minor version number.)
There is no evidence of complicated "intellectual property" movements.
I believe the IP is fine - at least everything in the official Eclipse Foundation git repos. That part is done, but I don't know what additional standards have to be met to make a release
Or even how to make a release
The how part is still unclear to me. I think latest releases were handled by @quintesse or @FroMage
Much (most?) of what was done in the past is documented here: https://github.com/eclipse/ceylon/blob/master/dist/RELEASE.md, but we do need to figure out what to do with the infrastructure (herd, js web ide) which I don't have admin privs for (and don't want admin privs for!), and we probably need entirely new procedures for making Eclipse Foundation releases.
The biggest unknown is probably the Eclipse Foundation stuff, so it would be great if someone could take on the role of coordinating with them, and finding out what must be done for us to make a release
You just need to run
ant publish, ant test, and the like, as in the readme https://github.com/eclipse/ceylon-sdk
But if you are using Ceylon 1.3.3, you'll need to checkout
1.3.3 compatible code - the master branch is not compatible
The tag
_old/1.3.3-branching should probably work
I'm sure I'm missing some of the problems you are running into, but there shouldn't really be anything to set up to compile the SDK beyond what you are doing for your own projects. The SDK is just a regular Ceylon project. Even commands like
ceylon compile and ceylon test should work.
IIRC, the only SDK module with any special support from the language is
ceylon.test. The rest are just standalone modules that happen to use the ceylon namespace.
The first bits.
I wouldn't follow those particular directions, that's for making public releases.
I'd be slightly surprised if everything didn't work on Windows, but yeah, a Unix-like environment would definitely work. I've only built on Mac and Linux
@jvasileff can You take a look on #7460 some of commits are labeled with
! can You check them I don't seem to understand everything there. I'm in 1/3 of the list...
I'm trying to follow what's on
What happened?
https://github.com/eclipse/ceylon/blob/master/dist/BUILD.md but trying to clone the repository I'm having this errorerror: RPC failed; curl 18 transfer closed with outstanding read data remaining
fatal: the remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failedWhat happened?
@fill0llif try cloning using git protocol:
https://stackoverflow.com/questions/38618885/error-rpc-failed-curl-transfer-closed-with-outstanding-read-data-remaining
https://stackoverflow.com/questions/38618885/error-rpc-failed-curl-transfer-closed-with-outstanding-read-data-remaining
@fill0llif try cloning using git protocol:
https://stackoverflow.com/questions/38618885/error-rpc-failed-curl-transfer-closed-with-outstanding-read-data-remaining
It worked, thanks!
There is 115 commits left
If anyone could give me a hand here eclipse/ceylon#7460 we could finish before end of march
I just pick a commit on the _old/master branch straight from github and review it, right? And then put the info in the list, like every other commit that has already been reviewed there, right? Does it require me some specific knowledge? I believe it would get me a certain amount of time anyway
Well it would be good to have some knowledge of what happening in the code but for me it is not always the case. Those commits I mark with
! as when I'm not sure what is there and is it introducing backward compatiblity break. Most of commits are readable if You know Java. Dev team also made most of them obvious through the commit message and metadata on github tickets with labels and description.
If You don't know what happening in the commit just take next one, it sometimes is understadable after reviewing few what was happening in the first one, again from commit message or reference to the ticket