[Aldor-l] Testers

[Bill Page]

On 12/19/07, Pippijn van Steenhoven wrote:
> On Tue, Dec 18, 2007 at 10:54:53PM -0500, Bill Page wrote:
> ...
> > BTW, how do you plan to publish your changes? Would it make
> > sense to create a branch in the Aldor SVN repository to allow
> > you to post directly to the repository without affecting the current
> > main branch (trunk)?
>
> I'm not sure. The code as I have it locally, has changed quite a bit.
> I changed some APIs and macro syntaxes as well as just about
> everything that involves debugging. The differences between
> Aldor(local) and Aldor(svn) are pretty large. I'll upload a source
> tarball and people can take a look at it. Aldor.org administrators
> may then consider taking it (having royalty-free rights to do so)
> and merging it with their own or making it into a branch.
> We'll see :-)
>

I very strongly urge both you and the "aldor.org administrators" to
co-operate closely and establish your work as a branch in the aldor
repository. You should have direct write access to the respository and
be able to commit changes incrementally to that new branch.

Note: This does *not* mean simply recording the tarball that you are
about to upload somewhere in the repository but rather *first*
creating an actual branch from trunk and then applying your changes as
a delta. It does not matter so much that the changes are large and
extensive (although obviously smaller separately documented changes
are desirable).

I think a deliberate and extra effort at co-operation is important
because given the relative dissatisfaction with the APL2 licensing
conditions there is a potential that important work on Aldor could be
lost to the developer/user community or there could be very
undesirable division of labor or worse the creation of entirely
separate project (I don't want to use the 'f...' word :-). So please,
let's find a way to make this work smoothly and to everyone's
advantage.

Season's greetings to all!

Regards,
Bill Page.