Re: [Gnu-arch-users] Arch use case from /. post

[Aaron Bentley]

Matthew Dempsky wrote:

> "The big problem for getting submitted code accepted is that these
> companies are usually fixing and developing on a codebase that is
> aging. For instance, Sun did numerous I18N fixes for GNOME 2.6, but by
> the time they were ready the main GNOME organization had moved on to
> 2.8. That means there is a disconnect between the two and the changes
> have to be ported forward before they will hit the main code
> branch. The same problem can happen with kernel patches and just about
> any other codebase that changes versions so quickly."
>
> --http://linux.slashdot.org/comments.pl?sid=116172&cid=9832361
>
> Seems like a problem that Arch could definitely help out with.

Arch has definitely made life bearable while maintaining a devel and 
release branch at work.  I and another developer work on the release 
branch, and I usually star-merge the changes into the devel branch 
within hours of finalizing them in the release branch.  But it only 
works well when the codebases haven't drifted too far apart.  We're 
using different string types in release and devel, so the devel version 
sometimes bears little resemblance to the release version.

Before Arch, it was cvs update -j -j, making CVS tags every time and 
keeping track of them in text files.  Ugh and triple ugh.

Aaron