[kforge-dev] next KForge version

[Rufus Pollock]

I think you are probably right that this is a better way to go rather 
than releasing a bugfix 0.13.1 (or even releasing 'over' the existing 
0.13 release files). In this case shall we try and bring forward the 
0.14 release date?

~rufus

John Bywater wrote:
> Rufus,
> 
> On reflection, I think we should stick to our singular release process, 
> go round the release loop again.
> 
> I'm fairly sure it would be better if the 0.13 release of KForge should 
> remain as documented on the list. And that new changes indicate a new 
> release, with release notes to record the changes. Otherwise it will all 
> look a bit queer, won't it?
> 
> There's no shame in making the scope narrow, to release better quality. 
> And anyway, we are sorting a number of things out which haven't been 
> thoroughly addressed.
> 
> I suggest we calmly create and announce a 0.14 release, which delivers 
> improved usability of the plugins, and improves aspects of installation, 
> configuration, and documentation. (Super keen people can always use 
> trunk.) I think that's a good scope for a minor release. Just cos we 
> fixed a few things shouldn't mean we just make a new release. Let's 
> finish the work to improve plugins, and when we're ready, release a 
> clearly much better version.
> 
> But let's not complicate the release process just now. Let's run the 
> existing release process again from the top when we've sorted the 
> plugins out properly? And in the meantime, either rest, or fix plugins?
> 
> What do you think?
> 
> Best wishes,
> 
> John.
> 
>