juneau-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Bognar <james.bog...@salesforce.com>
Subject Re: Status update.
Date Wed, 28 Sep 2016 21:36:28 GMT
Thanks Stian!

Can you check the KEYS
<https://dist.apache.org/repos/dist/release/incubator/juneau/KEYS> file and
see if it looks correct?

I've modified the names of the downloads to apache-juneau-*.

I'm augmenting the info in the Taverna with the doc I created.  I fully
expect to need a couple of dry runs the first time.  This is way more
complicated than I first anticipated :-(


On Mon, Sep 26, 2016 at 11:16 AM, Stian Soiland-Reyes <stain@apache.org>
wrote:

> I'm afraid for the dist server you need to go old-skool and use SVN
> with your apache.org credentials.
>
> See
> https://www.apache.org/dev/release-publishing
>
> (but note we belong under incubator/juneau )
>
>
> svn mkdir https://dist.apache.org/repos/dist/release/incubator/juneau
> should work for anyone in the incubator group
>
> Then you can use
>
> svn co https://dist.apache.org/repos/dist/release/incubator/juneau
>
> and add the KEYS file with "svn add" and "svn commit"
>
>
> Similarly the release candidates you should add at the /dev/ sibling
> after making:
>
> https://dist.apache.org/repos/dist/dev/incubator/juneau
>
>
> When the release has passed, you can just use "svn mv" to move it over
> - not having to worry about missing anything or getting the wrong
> version.
>
>
> To simplify such a move, then don't put the files straight into
> sources/ and binaries/ split as Commons has done (and which we want to
> move away from), but rather use a sub-folders like
> juneau-6.0-RC1 (renamed to juneau-6.0 under dist when released).
>
>
> The incubator folks like all the downloadable files to have the
> apache- prefix, e.g.
>
> apache-juneau-6.0-source.zip
>
> (You can tweak <finalName> in the assembly config)
>
> On 25 September 2016 at 17:54, Craig Russell <craig.russell@oracle.com>
> wrote:
> >
> >> On Sep 24, 2016, at 8:59 AM, James Bognar <james.bognar@salesforce.com>
> wrote:
> >>
> >> I have more questions for our mentors....
> >>
> >> 1) Do you have any thoughts/preferences on the initial version #?  6.0
> or
> >> 1.0?
> >
> > Can folks using the original project switch to this one by simply
> changing the maven coordinates? I guess not since all the import statements
> need to change.
> >
> > So I don’t think it much matters in terms of confusing the audience. If
> you like to think of Juneau 6.0 as the next release of Juno 5.x, I don’t
> see an issue. Many incubating projects leave the past in the past and start
> with 0.1. And many keep the naming of the previous project.
> >>
> >> 2) Where should release notes be kept?  Should we have a single
> >> RELEASE-NOTES.txt file in the root, or separate ones in each bundle
> >> project?
> >
> > Three places: prominently on the web as a download, as a viewable web
> page, and in the top level (root) of any distribution.
> >>
> >> 3) In the commons release notes, I see references to
> >> https://dist.apache.org/repos/dist/release/commons
> >> as the location for the KEYS file and downloads.  What exactly is this
> and
> >> how is it populated?
> >
> > This is where Apache releases are put after being voted on and approved.
> But it’s not https://dist.apache.org/repos/dist/release/juneau but
> https://dist.apache.org/repos/dist/release/incubator/juneau
> >
> >> How do we get an
> >> https://dist.apache.org/repos/dist/release/juneau?
> >
> >
> > A few years ago you could scp to the host machine. I’m not sure what the
> current protocol is. Can you try to create the directory using scp and see
> what happens?
> >>
> >> 4) The commons project refers to a "mvn commons:download-page' command.
> >> Any idea what that is and what it does?
> >
> > Dunno.
> >
> > Craig
> >>
> >>
> >
> > Craig L Russell
> > clr@apache.org
> >
> >
>
>
>
> --
> Stian Soiland-Reyes
> http://orcid.org/0000-0001-9842-9718
>



-- 
James Bognar

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message