[Falcon] What would be needed in order to release two tiny parts of Falcon?

[Christofer Dutz <ch...@c-ware.de>]

Hi,


I'm hoping on Justin to give me a heads-up on this ;-)


As I mentioned a few times now we will need to release some parts of Falcon prior to being able to actually release Falcon itself. Namely this will be the compiler-build-tools and the compiler-jburg-types module. Later module only consists of one interface that I bet will not change in the near future. Same with the compiler-build-tools.


In order to release these modules (will probably be two separately released modules), do we have to equip all of them with Readmes and Licence things? If yes, should I simply copy them from the root and strip them down to the parts needed? I really suck when it comes to the legal stuff :-(


Chris

AW: [Falcon] What would be needed in order to release two tiny parts of Falcon?

[Christofer Dutz <ch...@c-ware.de>]

Well all I want is these two binary artifacts released so they can be synced to maven-central. Then we could go down to one maven build per SDK fragment (compiler, type-definitions, framework + distribution). I would prefer a simple binary release build without the fuss of posting release Notifications as the libraries are use nothing to anyone.


Would such a release be ok? if yes, what do I have to do to initiate it?


Chris

________________________________
Von: Alex Harui <ah...@adobe.com>
Gesendet: Freitag, 15. Juli 2016 16:32:29
An: dev@flex.apache.org
Betreff: Re: [Falcon] What would be needed in order to release two tiny parts of Falcon?

IMO, it depends on the source packaging.

If you release source packages for these two parts, then yes, they need
LICENSE, NOTICE and should have README.  If you only release binary Maven
artifacts when we release the other Falcon artifacts and the only source
package is pretty much what we have right now in the nightly Ant build,
then no, there is no additional NOTICE/LICENSE/README work, although we
need to verify that any JARs have LICENSE and NOTICE in them regardless of
how we package the source and have separate source releases or not.

-Alex

On 7/15/16, 12:51 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:

>Hi,
>
>
>I'm hoping on Justin to give me a heads-up on this ;-)
>
>
>As I mentioned a few times now we will need to release some parts of
>Falcon prior to being able to actually release Falcon itself. Namely this
>will be the compiler-build-tools and the compiler-jburg-types module.
>Later module only consists of one interface that I bet will not change in
>the near future. Same with the compiler-build-tools.
>
>
>In order to release these modules (will probably be two separately
>released modules), do we have to equip all of them with Readmes and
>Licence things? If yes, should I simply copy them from the root and strip
>them down to the parts needed? I really suck when it comes to the legal
>stuff :-(
>
>
>Chris

Re: [Falcon] What would be needed in order to release two tiny parts of Falcon?

[Alex Harui <ah...@adobe.com>]

IMO, it depends on the source packaging.

If you release source packages for these two parts, then yes, they need
LICENSE, NOTICE and should have README.  If you only release binary Maven
artifacts when we release the other Falcon artifacts and the only source
package is pretty much what we have right now in the nightly Ant build,
then no, there is no additional NOTICE/LICENSE/README work, although we
need to verify that any JARs have LICENSE and NOTICE in them regardless of
how we package the source and have separate source releases or not.

-Alex

On 7/15/16, 12:51 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:

>Hi,
>
>
>I'm hoping on Justin to give me a heads-up on this ;-)
>
>
>As I mentioned a few times now we will need to release some parts of
>Falcon prior to being able to actually release Falcon itself. Namely this
>will be the compiler-build-tools and the compiler-jburg-types module.
>Later module only consists of one interface that I bet will not change in
>the near future. Same with the compiler-build-tools.
>
>
>In order to release these modules (will probably be two separately
>released modules), do we have to equip all of them with Readmes and
>Licence things? If yes, should I simply copy them from the root and strip
>them down to the parts needed? I really suck when it comes to the legal
>stuff :-(
>
>
>Chris