On Wed, Aug 15, 2012 at 6:53 AM, Oliver Sims
<oliver.s...@simsassociates.co.uk> wrote:
> I've found ooGuide files here:
>
> https://svn.code.sf.net/p/oorexx/code-0/ooDialog/trunk/examples/userGuide/ex
> ercises/
>
> https://svn.code.sf.net/p/oorexx/code-0/ooDialog/branches/4.2.0/doc/oodguide
> /
>
> I'd like to commit some of Exercise07 for the oodGuide. But are we still

Hi Oliver.

It should be relatively easy to keep straight, if you just remember
that trunk is where *new* development is done.

Typically, in our process, code is *branched* when we are about to
release a version.  Ideally, the code in a branch would not be changed
unless it was to fix a bug found in the beta cycle.

With that in mind, Exercise07 is new development so it should go in:

... code-0/ooDialog/trunk/examples/userGuide/exercises

The text in the user guide for exercise 07 is new text so it should go in:

... code-0/docs/trunk/oodguide

> keeping a 4.1.0 / 4.2.0 split?
> If so, is the examples folder for 4.1.0 or 4.2.0?

Well yes, there will always be a 4.1.0 / 4.2.0 split.  But, there is
no user guide in ooDialog 4.1.0.

There is also a 4.2.0 / trunk split.  In trunk, the version number is
not a hard and fast number, but it will always be higher than the
released, or about to be released, version.  For ooDialog, the next
version is likely to be 4.2.1.

Note that you should not commit using https://  You should read the
tortoiseSVN guide pointed to in the SourceForge ticket I mentioned
yesterday to see how to use tortoiseSVN to commit using svn+ssh.

--
Mark Miesfeld

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to