On 2007-10-25, Wichert Akkerman <[EMAIL PROTECTED]> wrote: >> >>>Point taken.. that was me doing the same bad thing. Unfortunately PSC >> >>>almost forces you to either do that or create separate full releases for >> >>>each pre-release. >> >>I also consider that very unfortunate - if not broken. :-( >> >>If there is agreement on changing this (to what then?) I would be >> >>willing to lobby more for it - or maybe do it myself - as I'm about >> >>to deploy a customized PSC on one of my sides rather soon anyway. >> >There was a discussion about a while ago where various alternative >> >approaches were discussed. >> Any pointers maybe? > I have no idea. This is the start of the thread I mentioned: > http://www.nabble.com/Handling-multiple-releases-in-PSC-tf4247869s20094.html >> As I said: once we know what we want I would be willing >> to implement it. > Yay!
Most of the momentum I know about came from: http://www.openplans.org/projects/plone-products/project-home IMO the process should be: 1. Add a plip to http://plone.org/products/plonesoftwarecenter/roadmap 2. If the plip is a good idea, add it to the TODO list: https://dev.plone.org/collective/browser/PloneSoftwareCenter/trunk/TODO.txt 3. Code it up, tag, and release, where "relase" means put it on plone.org/products (and the cheeseshop, once it's an egg). 1.5-beta1 is about to go out the door, but trunk changes are welcome for 1.5-rc1 and beyond, with the goal being to ship a 1.5 that will run on a Plone 3.0 migrated plone.org. 1.0 is supposed to support 2.5.x and 2.0 is supposed to include new features, i.e. egg-i-fication. Join the fun! :-) > Wichert. > -- Alex Clark (http://aclark.net) _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
