[Xerte-dev] Re: New Build

[Pat Lockley]

> 
>> 
> 
>> I get the feeling this is just a growing pain, but we could do with
>> some thoughts on say
>> 
>> What will tag / branch 1.9 be?
>> 
> 
> 1.9 should be a branch - as you work in branches. Tags should be static and unchanging - so e.g. the 1.9.0 release would be a tag, but work would probably continue in the 1.9 branch as you fix bugs - eventually leading to a 1.9.1 release/tag

Yep I get what the branch is as a concept but not what the work will be - so swapping all queries could be the goal, but who makes the call?

Internationalisation made sense to me as a step - something I felt I could do. Database abstraction layers doesn't really feel as nice.



> 
>> What sort of coding standards are there (the only thing really I would
>> say is text strings for internationalisation are upper case - but some
>> of the commits are indent changes
> 
> That's mostly me. My editor will reindent most stuff for me, and I find it easier to read if it's not consistent

Yep, alls good. I meant more should I aim for something? 


> 
>> - so are we going drupal like? I
>> don't mind what we do - it just makes sense for people looking to
>> commit changes they know it'll work. Once we got a commit for the PHP
>> header change for the export code, but I never committed it because it
>> broke Nottingham's export function. This isn't a big deal, but the
>> idea of nightly build, or a test version before approval makes sense?
> 
> You're almost straying into Continuous Integration territory. For that to work you need unit tests in place, and your code base isn't really setup to support them

Yep. Was about to mumble about selenium or jenkins. Agree the code is miles off, but does it offer scope for a 1.9 or next step. Am convinced people only like drupal as it supports this kinda stuff.


> 
>> 
>> If everyone uses bugfixes.txt as well that helps a lot, so all fixes
>> are explained simply and listed for people to use. That way everyone
>> can be on the most up to date version without worrying about anything.
>> I know the SVN does it, as does the RSS feed - but it's not obvious or
>> tied to the install in any place.
>> 
> 
> bugfixes.txt?

There used to be a bugfixes.txt in the zip, which sounds like a changelog.txt

Suggest we add a version.txt and a changelog.txt to the zip in future then?

Just making sure the process is a little smoother in future.

Just thoughts

Pat