On Wed, Mar 9, 2011 at 12:06 PM, Peter Lavender <pla...@internode.on.net> wrote:
> That's really my fault, I was not trying to point at whose fault it was. If for nothing else because the only people not making mistakes are those who don't do anything. I was just collecting thoughts. > But it's not just translators here, there is the issue of testing the branch > for usability. > > So for example, I asked a few times if anyone had tested things and the tar > balls I created of the branch, but got little response. > > So I guess my question is, should we also look at building release > candidates that I can put on my server for people to pick and test? >From the POV of configuration management I am against the releases candidates as was done this time. We should never create and distribute two tarballs with the same name as it will lead to chats like this: "The first 0.82 package" "No, the second one". "Were there more?" In short it will be unclear what is in a package called 0.82. If we we want release candidates we should give them distinctive names. As least a the name of the tarball but probably also inside in the files. We can do something like that but I don't see a lot of advantages in that. At least not in our 0.xx releases. Gabor _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
