You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by Aaron Peeler <aa...@ncsu.edu> on 2008/11/21 16:01:07 UTC
getting started using apache tools and processes
Matt, et all mentors,
What are our next steps in getting started or ideally what are the best
practices in using the Apache processes and tools.
I'm sure one of the next immediate steps is to add our most recent VCL code
to the svn. Is there a recommended structure for the svn - branches, stable
releases, etc, that apache would like us to follow, or is that to our own
design?
Thanks,
Aaron
Aaron Peeler
OIT Advanced Computing
College of Engineering-NCSU
http://vcl.ncsu.edu
Re: getting started using apache tools and processes
Posted by Aaron Peeler <aa...@ncsu.edu>.
Sounds good - thanks.
Aaron
--On November 21, 2008 11:13:19 AM -0800 Matt Hogstrom <ma...@hogstrom.org>
wrote:
> We can create any structure we want. I propose the following which is
> consistent with a number of projects at Apache.
>
> Our SVN repository is at: https://svn.apache.org/repos/asf/incubator/vcl
>
> In that directory I created the following directories as a strawman:
>
> trunk (current development work)
> branches (place for release work, bug fixes, etc.)
> tags (directory that contains releases, this maps to released software
> so no changes should be made to releases in this tree)
> sandbox (as the name implies, funky stuff, experimentation, etc.)
>
>
> On Nov 21, 2008, at 7:01 AM, Aaron Peeler wrote:
>
>> Matt, et all mentors,
>>
>> What are our next steps in getting started or ideally what are the
>> best practices in using the Apache processes and tools.
>>
>> I'm sure one of the next immediate steps is to add our most recent
>> VCL code to the svn. Is there a recommended structure for the svn -
>> branches, stable releases, etc, that apache would like us to follow,
>> or is that to our own design?
>>
>> Thanks,
>> Aaron
>>
>> Aaron Peeler
>> OIT Advanced Computing
>> College of Engineering-NCSU
>> http://vcl.ncsu.edu
>>
>
Re: getting started using apache tools and processes
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
I imagine that once we get the goods, we might put it initially in
tags/import then copy that to trunk.
Regards,
Alan
On Nov 21, 2008, at 11:13 AM, Matt Hogstrom wrote:
> We can create any structure we want. I propose the following which
> is consistent with a number of projects at Apache.
>
> Our SVN repository is at: https://svn.apache.org/repos/asf/incubator/vcl
>
> In that directory I created the following directories as a strawman:
>
> trunk (current development work)
> branches (place for release work, bug fixes, etc.)
> tags (directory that contains releases, this maps to released
> software so no changes should be made to releases in this tree)
> sandbox (as the name implies, funky stuff, experimentation, etc.)
>
>
> On Nov 21, 2008, at 7:01 AM, Aaron Peeler wrote:
>
>> Matt, et all mentors,
>>
>> What are our next steps in getting started or ideally what are the
>> best practices in using the Apache processes and tools.
>>
>> I'm sure one of the next immediate steps is to add our most recent
>> VCL code to the svn. Is there a recommended structure for the svn -
>> branches, stable releases, etc, that apache would like us to
>> follow, or is that to our own design?
>>
>> Thanks,
>> Aaron
>>
>> Aaron Peeler
>> OIT Advanced Computing
>> College of Engineering-NCSU
>> http://vcl.ncsu.edu
>>
>
>
Re: getting started using apache tools and processes
Posted by Matt Hogstrom <ma...@hogstrom.org>.
We can create any structure we want. I propose the following which is
consistent with a number of projects at Apache.
Our SVN repository is at: https://svn.apache.org/repos/asf/incubator/vcl
In that directory I created the following directories as a strawman:
trunk (current development work)
branches (place for release work, bug fixes, etc.)
tags (directory that contains releases, this maps to released
software so no changes should be made to releases in this tree)
sandbox (as the name implies, funky stuff, experimentation, etc.)
On Nov 21, 2008, at 7:01 AM, Aaron Peeler wrote:
> Matt, et all mentors,
>
> What are our next steps in getting started or ideally what are the
> best practices in using the Apache processes and tools.
>
> I'm sure one of the next immediate steps is to add our most recent
> VCL code to the svn. Is there a recommended structure for the svn -
> branches, stable releases, etc, that apache would like us to follow,
> or is that to our own design?
>
> Thanks,
> Aaron
>
> Aaron Peeler
> OIT Advanced Computing
> College of Engineering-NCSU
> http://vcl.ncsu.edu
>