Andrea Righi wrote: > 1) use the pre-release of rsync that seems to fix the problem and tag > SystemImager 4.0.2, leaving the 4.0.0 packages as they are, let me say that I > would just proceed like the kernel guys do if there's a bug in the kernel > (just > leave all the previous released kernels "forzen" and available for download in > any case, and always release new versions in case of errors/bugs) > > 2) remove the old 4.0.0 packages from SF.net (let me say "close" them to the > users), rebuild all the packages in a build server with a kernel < 2.6.22 and > then release the new packages using the same version number: 4.0.0 > > 3) rebuild the packages in a build server with a kernel < 2.6.22 and changing > the version number to 4.0.2, leaving 4.0.0 packages as they are on SF.net > > 4) other ideas are welcome...
After few days the result of the polling seems to be the following: - 3 votes for solution #1 - 3 votes for solution #2 So, nothing changed... :-) Let me try to formulate a reasonable compromise... What do you think about tagging 4.1.0 (based on the current trunk), release 4.1.0 (unstable) and if we don't see any bug report for a week backport the 4.1.0 patches in the stable branch and tag 4.0.2? -Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ sisuite-devel mailing list sisuite-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-devel
