You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by Josh Thompson <jo...@ncsu.edu> on 2010/09/16 20:12:56 UTC
[mentors] release artifact question
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Mentors:
I have a question about bundling 3rd party software in the release artifact.
I'm planning to include the Dojo Toolkit in the artifact. It is released
under the Academic Free License. I've done what is needed with the LICENSE
and NOTICE files.
What I can't find information about is if it should be added to subversion. I
don't see a need to have it there. I was just planning on adding it in after
doing the svn export of the release tagged code. However, I seem to remember
something about the contents of the artifact needing to exactly match an
export of the release tag.
So, do I need to add the Dojo Toolkit code to subversion or not?
Thanks,
Josh
- --
- -------------------------------
Josh Thompson
Systems Programmer
Advanced Computing | VCL Developer
North Carolina State University
Josh_Thompson@ncsu.edu
919-515-5323
my GPG/PGP key can be found at pgp.mit.edu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
iEYEARECAAYFAkySXisACgkQV/LQcNdtPQMd5gCcDtMxyiT/8DoNbgIvKprJLKdf
3+UAnAkGB8WUWo48H2MH7UP8rzRMnABr
=n/0a
-----END PGP SIGNATURE-----
Re: [mentors] release artifact question
Posted by Matt Hogstrom <ma...@hogstrom.org>.
On Sep 17, 2010, at 2:25 PM, Josh Thompson wrote:
>
> Kevan and Matt - thanks for the info. I added instructions to
>
> https://cwiki.apache.org/confluence/display/VCL/VCL+Release+Procedures
>
> on downloading and including Dojo Toolkit in the section that explains how to
> create the RC.
>
> Josh
I'd add a comment about updating a document that indicates the version used. Basically, if someone comes back later and wants create the release form the tag they'd need to know what release was used as the current is not guaranteed to be the one you used when you released. It could be a couple of years. This isn't a hard requirement but is a convenience for your users.
Cheers.
Re: [mentors] release artifact question
Posted by Josh Thompson <jo...@ncsu.edu>.
On Friday September 17, 2010, Kevan Miller wrote:
> On Sep 17, 2010, at 10:52 AM, Josh Thompson wrote:
> > So, it just needs to be somewhere in the repo to ensure it is always
> > available, but it doesn't actually have to be part of the release tag
> > such that an export of the release tag includes it? My plan was to
> > actually include it in the release already untarred and in place to
> > remove a few steps of the installation.
>
> The source distribution archive is your "release". Though svn tags
> typically mirror the source distribution, this is not a requirement.
>
> Many java-based projects use maven for managing binary dependencies. So,
> neither svn nor the source distribution contain all of the binary
> dependencies of the project. The resources that Matt pointed out in the
> Geronimo project are resources that were not available via maven. So, they
> exist to circumvent some other problems...
>
> IMO, you aren't required to have the original artifact in svn. Though it
> might well be something the project wants to do. In either case, the
> general process should be documented for posterity. I would expect that
> this documentation would be included in svn (and the source distribution).
>
> --kevan
Kevan and Matt - thanks for the info. I added instructions to
https://cwiki.apache.org/confluence/display/VCL/VCL+Release+Procedures
on downloading and including Dojo Toolkit in the section that explains how to
create the RC.
Josh
--
-------------------------------
Josh Thompson
Systems Programmer
Advanced Computing | VCL Developer
North Carolina State University
Josh_Thompson@ncsu.edu
919-515-5323
my GPG/PGP key can be found at pgp.mit.edu
Re: [mentors] release artifact question
Posted by Kevan Miller <ke...@gmail.com>.
On Sep 17, 2010, at 10:52 AM, Josh Thompson wrote:
> So, it just needs to be somewhere in the repo to ensure it is always
> available, but it doesn't actually have to be part of the release tag such
> that an export of the release tag includes it? My plan was to actually
> include it in the release already untarred and in place to remove a few steps
> of the installation.
The source distribution archive is your "release". Though svn tags typically mirror the source distribution, this is not a requirement.
Many java-based projects use maven for managing binary dependencies. So, neither svn nor the source distribution contain all of the binary dependencies of the project. The resources that Matt pointed out in the Geronimo project are resources that were not available via maven. So, they exist to circumvent some other problems...
IMO, you aren't required to have the original artifact in svn. Though it might well be something the project wants to do. In either case, the general process should be documented for posterity. I would expect that this documentation would be included in svn (and the source distribution).
--kevan
Re: [mentors] release artifact question
Posted by Josh Thompson <jo...@ncsu.edu>.
So, it just needs to be somewhere in the repo to ensure it is always
available, but it doesn't actually have to be part of the release tag such
that an export of the release tag includes it? My plan was to actually
include it in the release already untarred and in place to remove a few steps
of the installation.
Josh
On Friday September 17, 2010, Matt Hogstrom wrote:
> Geronimo had similar issues where they needed to include jars from other
> projects so that they could have a repeatable build process. Take for
> instance, a customer that is trying to build the project 10 years from now
> (unlikely but that is the thought).
>
> They included the tar balls for Dojo in a place called repository which
> contained the artifacts in question. See the following reference:
>
> https://svn.apache.org/repos/asf/geronimo/server/tags/2.1.4/repository/org/
> dojotoolkit/dojo/1.0.2/
>
> On Sep 16, 2010, at 2:12 PM, Josh Thompson wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Mentors:
> >
> > I have a question about bundling 3rd party software in the release
> > artifact. I'm planning to include the Dojo Toolkit in the artifact. It
> > is released under the Academic Free License. I've done what is needed
> > with the LICENSE and NOTICE files.
> >
> > What I can't find information about is if it should be added to
> > subversion. I don't see a need to have it there. I was just planning
> > on adding it in after doing the svn export of the release tagged code.
> > However, I seem to remember something about the contents of the artifact
> > needing to exactly match an export of the release tag.
> >
> > So, do I need to add the Dojo Toolkit code to subversion or not?
> >
> > Thanks,
> > Josh
> > - --
> > - -------------------------------
> > Josh Thompson
> > Systems Programmer
> > Advanced Computing | VCL Developer
> > North Carolina State University
> >
> > Josh_Thompson@ncsu.edu
> > 919-515-5323
> >
> > my GPG/PGP key can be found at pgp.mit.edu
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v2.0.16 (GNU/Linux)
> >
> > iEYEARECAAYFAkySXisACgkQV/LQcNdtPQMd5gCcDtMxyiT/8DoNbgIvKprJLKdf
> > 3+UAnAkGB8WUWo48H2MH7UP8rzRMnABr
> > =n/0a
> > -----END PGP SIGNATURE-----
--
-------------------------------
Josh Thompson
Systems Programmer
Advanced Computing | VCL Developer
North Carolina State University
Josh_Thompson@ncsu.edu
919-515-5323
my GPG/PGP key can be found at pgp.mit.edu
Re: [mentors] release artifact question
Posted by Matt Hogstrom <ma...@hogstrom.org>.
Geronimo had similar issues where they needed to include jars from other projects so that they could have a repeatable build process. Take for instance, a customer that is trying to build the project 10 years from now (unlikely but that is the thought).
They included the tar balls for Dojo in a place called repository which contained the artifacts in question. See the following reference:
https://svn.apache.org/repos/asf/geronimo/server/tags/2.1.4/repository/org/dojotoolkit/dojo/1.0.2/
On Sep 16, 2010, at 2:12 PM, Josh Thompson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Mentors:
>
> I have a question about bundling 3rd party software in the release artifact.
> I'm planning to include the Dojo Toolkit in the artifact. It is released
> under the Academic Free License. I've done what is needed with the LICENSE
> and NOTICE files.
>
> What I can't find information about is if it should be added to subversion. I
> don't see a need to have it there. I was just planning on adding it in after
> doing the svn export of the release tagged code. However, I seem to remember
> something about the contents of the artifact needing to exactly match an
> export of the release tag.
>
> So, do I need to add the Dojo Toolkit code to subversion or not?
>
> Thanks,
> Josh
> - --
> - -------------------------------
> Josh Thompson
> Systems Programmer
> Advanced Computing | VCL Developer
> North Carolina State University
>
> Josh_Thompson@ncsu.edu
> 919-515-5323
>
> my GPG/PGP key can be found at pgp.mit.edu
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.16 (GNU/Linux)
>
> iEYEARECAAYFAkySXisACgkQV/LQcNdtPQMd5gCcDtMxyiT/8DoNbgIvKprJLKdf
> 3+UAnAkGB8WUWo48H2MH7UP8rzRMnABr
> =n/0a
> -----END PGP SIGNATURE-----