My experience is that using trunk for development is very feasible and makes
"migration" to the next stable release VERY simple (and incremental).

Check which working revision you have before doing an svn update on your
trunk checkout. Then you can always go back to this revision if the latest
and greatest fails.

Of course, Thomas, you are correct, that following the weekly announcements
(which I do) and reading the commit messages (which I usually don't) makes a
lot of sense. So far I got away with what I am doing.

And yes, for projects deployed at a customers' site we use a stable QX
release, just to be sure.

Cheers,
Fritz

On Thu, 6 Oct 2011, thron7 wrote:

> There is still a chance that trunk might be instable for a couple of
> days, e.g. when we're implementing complex changes that require
> different places to be modified.
>
> You should really think if you *need* it. Planned features are in the
> qooxdoo roadmap and can also be tracked checking the bugzilla issues
> assigned to the next minor release (1.6 currently).
>
> If you decide to work with trunk you should at least make sure you read
> and understand every weekly we post on Fridays. User-visible changes in
> trunk are announced there, and you need to follow those if you want your
> project to keep functioning. Better still keep an eye on the commit
> messages. Don't come whining because some change caught you off guard!
>
> T.
>
> On 10/05/2011 08:04 PM, Fritz Zaucker wrote:
>> In my experience trunk is stable most of the time.
>>
>> Cheers,
>> Fritz
>>
>> On Thu, 6 Oct 2011, Phyo Arkar wrote:
>>
>>> I am thinking should i stick with 1.5 or go Trunk for an inhouse site.
>>>
>>> What are the new features that have in trunk and that would be in 1.6 ?
>>>
>>> Or should i wait for 1.6 ?
>>>
>>> I am more and more addicted to Qooxdoo after i am getting used to it.
>>> and eager to test new stuff whats gonna be in 1.6.
>>>
>>> ------------------------------------------------------------------------------
>>> All the data continuously generated in your IT infrastructure contains a
>>> definitive record of customers, application performance, security
>>> threats, fraudulent activity and more. Splunk takes this data and makes
>>> sense of it. Business sense. IT sense. Common sense.
>>> http://p.sf.net/sfu/splunk-d2dcopy1
>>> _______________________________________________
>>> qooxdoo-devel mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>
>>>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>

-- 
Oetiker+Partner AG              tel: +41 62 775 9903 (direct)
Fritz Zaucker                        +41 62 775 9900 (switch board)
Aarweg 15                            +41 79 675 0630 (mobile)
CH-4600 Olten                   fax: +41 62 775 9905
Schweiz                         web: www.oetiker.ch

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to