On Fri, Sep 2, 2011 at 10:13 AM, Vladimir Avdonin <[email protected]> wrote:
> Well, I have different phylosophy - I believe no development shall > happen trunk, it shall stay clean and functional at any moment. The only > commits that shall go there should be from tested working branch. > ... > What if we do not want to go back? Breaking up things is inevitable in > process of changing. And broken period can take extended time. > Your suggestions are good for a large and highly active project staffed with professional engineers. But many of the people contributing to JSL are amateurs, and only contribute for a short period of time before moving on. We want a system that maximizes *their* productivity, and ensures their changes make it into trunk. Also bear in mind, I believe that this current burst of activity will fade to nothing. It always happened in the past, so I must assume it will happen again. With that in mind, I want a system that maximizes the productivity of this current group of contributors before they leave, and also leaves JSL in a clear and obvious state for the next group when they pick it up in a year or two. Thus I believe the simplest solution is the best for JSL. And the simplest solution is to simply encourage everyone to contribute directly to trunk. This will increase the chances that someone will damage the code, but I believe the risk of damage is insignificant to the advantages of getting everyone's code into trunk where it is immediately useable. -Bill Zwicky ------------------------------------------------------------------------------ Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev _______________________________________________ Jsynthlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
