Paul Harris wrote: > i assume that unstable will be merged into testing after a period of > time, once the features have been ironed out ?
Well, the 'next' branch is supposed to be a testing ground of stuff, but if they don't get attention and have some deficiencies they won't be promoted to the 'master' branch (which btw is not strictly "stable" because they can contain small new tweaks, but that obviously don't break my own laptop). So it depends, they are there as an attempt to show what things can be done, what are the ideas in progress etc. A low latency place to put things where they will not be easily forgotten. > i'd like to stay on the stable version and not be too "bleeding". But with Martin's debianization thing, that should be easier for you to test. In particular you could take a look at the patch adding a config option to avoid workspace switching, because you were upset about firefox changing the workspace for the "search" thing. > i would suggest that when changes are merged into the testing/stable > branch, someone emails the list with the new bug fixes and features > added... that way i can test them. I don't know about that, and it is not like there are many bugs fixes after all. There are small things happening here and there, you can stay updated with 'git pull' and do the testing if something new appears and report back as your motivation permits. It all pretty much depends on what everybody is doing on the list. -- To unsubscribe, send mail to [email protected].
