On Sat, 2011-03-05 at 22:34 +0200, Gabor Szabo wrote: > hi, > > 0.82 was released on 27 February, almost a week ago. > > While it went quite well I think it would be important to collect > the thoughts of all the people involved and those not directly > involved to see how we can improve the release process. > Then I think we could start a new release in a few days. > > The release branch was created on 15 February - > http://padre.perlide.org/trac/changeset/13726 > The release was tagged on 27 February - > http://padre.perlide.org/trac/changeset/13844 > Almost 2 weeks later. > > IMHO that's too much.
That's really my fault, I'm rather distracted with things around home, so simply put, with the branch done and things like the fault with the messages.pot file it dragged on longer than it should have. > We should aim to 1 week and delay only if major > breakage was found > and needs to be fixed or tested again. That's fine by me. > > It would be probably better to know the planned release date once the > branching was done so the translators will know how to plan their time. > > Fair point. 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? > A few other issues I noticed: > > - The code was not passing all its release tests when it was branched. Yeah, that's a whoops from me, again I'll make sure we have a trunk that passes before the branch. > I'll have to change the smoke tester to run all the release tests and so > we can keep Padre clean during development. > > - We have not updated the Changes file to reflect the > improved translations as we had a freeze in the Changes file. So the Changes file gets updated on the branch? > > - We had a new translator and we have not credited him in Padre.pm > and in the About box due to the same freeze. > This is probably not such a big issue as we can always > credit him in the next release but it would be nicer to add his > name already. For me that went unnoticed because I have no idea really who the translators are.. I take the names from the changes file, or svn log now with the branch. > - There was some misunderstanding as to where to commit the translations. > We need to further explain that. Good point. When I make a branch I'll make it clearer in the emails that come out. > That's it > > What do you think? The branch wasn't too bad really.. it was good to be able to have the branch and have trunk still "busy" . I'll also branch with "Padre-" now, not "release" like last time. Pete
_______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
