On Tue, Nov 18, 2008 at 2:54 PM, Linus Tolke <[EMAIL PROTECTED]> wrote:
> This means that I should make a release 0.26.1 as soon as possible with the > exact same contents as 0.26.1.beta1. If the contents are the same and it's already (mis)labelled 0.26.1, why does anything need to be done except move it to the release page? If the kit really does need to be re-built, there needs to be an easily identifiable way to distinguish it from previous build (ie it can't have the same version string). On Tue, Nov 18, 2008 at 7:16 AM, Christian López Espínola <[EMAIL PROTECTED]> wrote: > So issue 5434 should be in a new stable release soon. Are there any > other issues that people wants to see in? > > I'd advocate the idea of doing a stable release (0.26.1) with the > contents of 0.26.1-beta (AKA 0.26.1). > We can then follow with other minor releases carefully if it is needed. I think the priority should be distributing as soon as feasible the fix for issue 5434 and any other problems which are corrupting peoples projects or preventing them from opening them (I think there was a profile issue fix included in 0.26.1). If releasing 0.26.1, To clarify the impact of issue 5434, it will corrupt any file containing non-USASCII characters. That includes not only all ideographic character sets (Chinese, Japanese, Korean), but accented Western European characters, Greek, Arabic, etc, etc. This will happen the first time a project is saved and will affect both new projects and those upgraded from earlier versions of ArgoUML. If you're lucky, it'll just change the characters into something else, but most of the time it will corrupt the project in a way which makes it unreadable. Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
