Creating an initial release.

[James Bognar <ja...@salesforce.com>]

I think we're ready to take a stab at creating a release of Juneau.

How exactly do we do that?

Questions...
What's the process involved?
What are the encryption keys that I see mentioned on the incubator mailing
list?
Where are the downloads going to be hosted?  Ideally it would be nice to be
able to track how many downloads are occurring.


-- 
James Bognar

Re: Creating an initial release.

[James Bognar <ja...@salesforce.com>]

Thanks Jochen...I'll give it a try over the weekend.

On Fri, Sep 16, 2016 at 3:47 AM, Jochen Wiedmann <jo...@gmail.com>
wrote:

> Hi, James,
>
> On Thu, Sep 15, 2016 at 11:38 PM, James Bognar
> <ja...@salesforce.com> wrote:
>
> > I think we're ready to take a stab at creating a release of Juneau.
> >
> > How exactly do we do that?
>
> I haven't had a look at the code, since some weeks. My recommendation:
>
> - Make sure, that everything can be built with Maven. (Perhaps already
> done.)
> - Follow the procedures, as outlined by another project, which are
> basically built on top of the maven-release-plugins,
>   for example: https://commons.apache.org/releases/
>   (Note, that this example assumes use of the commons-parent POM. You
> might want to introduce such a POM for Juneau, and
>   copy stuff from there, Might as well be, that use of the apache
> parent POM is sufficient, can't tell in advance.)
>
> Basic stuff to check:
>
>   - Have a reproducable procedure, which can be repeated in the
> future. (For example, by introducing a junea-dist module, which
>     depends on the modules to release.) This module should emit
> something like a junea-<incubating-VERSION>-bin.zip, and
>     (more important) a junea-<incubating-VERSION>-src.zip. The former
> should be recreatable from the latter.
>   -  Both files, should include proper NOTICE, and LICENSE files. (See
> http://www.apache.org/dev/licensing-howto.html.)
>   -  Have the dist module run, and pass, a Rat check on the
> distributed files, for example by copying them to a temp directory.
>
> This list is incomplete, but it should give you a feeling on the steps
> involved.
>
> Jochen
>
>
>
> --
> The next time you hear: "Don't reinvent the wheel!"
>
> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/
> evolution-of-the-wheel-300x85.jpg
>



-- 
James Bognar

Re: Creating an initial release.

[Jochen Wiedmann <jo...@gmail.com>]

Hi, James,

On Thu, Sep 15, 2016 at 11:38 PM, James Bognar
<ja...@salesforce.com> wrote:

> I think we're ready to take a stab at creating a release of Juneau.
>
> How exactly do we do that?

I haven't had a look at the code, since some weeks. My recommendation:

- Make sure, that everything can be built with Maven. (Perhaps already done.)
- Follow the procedures, as outlined by another project, which are
basically built on top of the maven-release-plugins,
  for example: https://commons.apache.org/releases/
  (Note, that this example assumes use of the commons-parent POM. You
might want to introduce such a POM for Juneau, and
  copy stuff from there, Might as well be, that use of the apache
parent POM is sufficient, can't tell in advance.)

Basic stuff to check:

  - Have a reproducable procedure, which can be repeated in the
future. (For example, by introducing a junea-dist module, which
    depends on the modules to release.) This module should emit
something like a junea-<incubating-VERSION>-bin.zip, and
    (more important) a junea-<incubating-VERSION>-src.zip. The former
should be recreatable from the latter.
  -  Both files, should include proper NOTICE, and LICENSE files. (See
http://www.apache.org/dev/licensing-howto.html.)
  -  Have the dist module run, and pass, a Rat check on the
distributed files, for example by copying them to a temp directory.

This list is incomplete, but it should give you a feeling on the steps involved.

Jochen



-- 
The next time you hear: "Don't reinvent the wheel!"

http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg