Stéphane Épardaud

Something like: ``` OPTIONS / Link: ; rel="http://modules.ceylon-lang.org/rel/upload-new", ... ``` ``` POST https://herd.ceylon-lang.org/api/6/upload/new ... CREATED Location: https://herd.ceylon-lang.org/api/6/upload/76523 Link: ; rel="http://modules.ceylon-lang.org/rel/upload-publish", ... ``` I don't _think_ we need a link/rel for...

> Somewhere we have to stick links to the upload UI too. The UI, and the upload repo URL that the tools can use to publish things to.

We can also have the following CLI plugins: ``` $ ceylon herd new-upload New upload at: https://... # Saves current upload ID in `.ceylon/config`, yells if there was already one...

We also need a reset option: ``` POST https://herd.ceylon-lang.org/api/6/upload/new ... CREATED Location: https://herd.ceylon-lang.org/api/6/upload/76523 Link: ; rel="http://modules.ceylon-lang.org/rel/upload-reset", ... ``` Again, implied `POST`

Idea cancelled, we're not going to have anything special for snapshot versions, though we could turn it into a warning?

Perhaps otherwise add a checkbox that identifies a specific upload as being stable, so we can then filter unstable releases?

We can certainly check the published docs more, including checking for `.resources`, but how did this happen exactly? Did you upload by zip perhaps? Checking the links for each HTML...

We don't enforce the presence of source files even for Ceylon archives, so we won't for Java either. But we should support having source files for Java archives yes. >...

I guess the rationale is that if people depend on something that is closed-source but redistributable, we shouldn't make it impossible to use it. It's certainly a debate we can...

That's a good idea, but it sounds very hard to implement, especially if we can search for subtypes.