Re: [Codenarc-developer] 0.11 release planning thread
Brought to you by:
chrismair
Menu
▾
▴
Re: [Codenarc-developer] 0.11 release planning thread
|
From: <chr...@wa...> - 2010-11-10 14:37:24
|
Absolutely. Hamlet DArcy <ham...@ca...> 11/10/2010 09:23 AM To chris mair <chr...@wa...> cc Cod...@li... Subject Re: [Codenarc-developer] 0.11 release planning thread Would you mind keeping track of your renames/moves and just sending me a heads up on them? Thanks, -- Hamlet D'Arcy ham...@ca... LOL. Good, I'm glad you prefer the lightweight release. I've still got some reorg to do (moving/renaming), so let's stick with a full release for Sun/Mon. Thanks for doing the first pass at the change log. That new rules list is pretty damn impressive! We also need to call out the need for Groovy 1.7. I can't check in stuff from work, so go ahead and check it in yourself. I'll have some edits later. Chris Hamlet DArcy <ham...@ca...> 11/10/2010 09:02 AM To chris mair <chr...@wa...> cc Cod...@li... Subject Re: [Codenarc-developer] 0.11 release planning thread Let's stick to lightweight releases. I hate branching too. I have the change log and a blog post all ready to go. Changelog is attached. I'll check it in tonight from home or you can make edits now and check it in yourself, whatever. I'd like to release the blog post /before/ the announcement to the mailing lists so have have some extra documentation to reference. I can get my javadoc and documentation reviewed tonight. It's your call. I'd love to release a BETA/RC tonight and full release Sunday/Monday. Or can wait for full release. Either way we get a full release soon and that's always resulted in a happy ending for me. And yes, that's a full release joke in that last sentence. -- Hamlet D'Arcy ham...@ca... Ok. In general, I have been preferring "lightweight" releases -- no branching; just roll changes/fixes into next release; and do next release sooner if necessary. But we can consider this a special case, since it is time-constrained. I'll plan on doing a 0.11-RC1 release, and we can create a branch. Is the weekend ok for that? When do you need it? Chris Hamlet DArcy <ham...@ca...> 11/10/2010 01:25 AM To Chris Mair <chr...@ea...> cc Cod...@li... Subject Re: [Codenarc-developer] 0.11 release planning thread Hmmm, I'll work on the CHANGELOG.txt file and javadoc in AstUtil. That way no new rules get checked in today. Perhaps it is best to build and upload 0.11 RC1 or Beta1 and branch the codebase. Then we have time to clean up false positives and issues while still allowing early adopters to check out the new work (and help with the bug reports!) -- Hamlet D'Arcy ham...@ca... Hamlet, In addition to the items in your list, I typically: A) Create a snapshot release and run that against several large Groovy projects at work, and examine the violations. In almost every release that has ended up revealing an issue or two -- often a false negative or false positive in a new rule. B) Run the new code version against the open source projects (Grails, Griffon, Gradle) and pull in the resulting reports. C) Deploy to the Maven Central Repo after the release D) Tag the project version in SVN I will plan to do all of the above. I will also do #3 (Grails plugin) from your list - usually a a few days after the release. You are more than welcome to do #2, #4 (I do not have Gradle commit rights) and #5. For #6 (email announcements), I was intending on collaborating with you. For #0 (Change log), if you want to do a draft version in the "CHANGELOG.txt" version that would be great, but not required. I will have a few additions of my own. To be honest, I am struggling to keep up with all of the recent additions/changes (though I am absolutely NOT complaining!!!). I don't have a lot of time to work on this each day. It will take me at least a few days to catch up and get my own changes done before the release. Are you pretty much done with your changes? Thanks a lot. Chris -----Original Message----- From: Hamlet D'Arcy [mailto:ham...@gm...] Sent: Tuesday, November 09, 2010 2:57 PM To: Cod...@li... Subject: [Codenarc-developer] 0.11 release planning thread Chris, You're the owner, so it is of course up to you to run the 0.11 release the way you want. As a list of todos, we need to: 0. Create the Changelog 1. Build and upload new version 2. Update Griffon plugin (i have commit rights and can do this) 3. UPdate Grails plugin (do you have commit rights?) 4. Update Gradle plugin (do you have commit rights?) 5. Publish a blogpost/page with more info about all the new rules (i can do this) 6. Send email announcements to groovy, griffon, grails, & hackergarten lists Which do you need the most help with? What is missing? -- Hamlet D'Arcy ham...@gm... ---------------------------------------------------------------------------- -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev _______________________________________________ Codenarc-developer mailing list Cod...@li... https://lists.sourceforge.net/lists/listinfo/codenarc-developer ------------------------------------------------------------------------------ The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev _______________________________________________ Codenarc-developer mailing list Cod...@li... https://lists.sourceforge.net/lists/listinfo/codenarc-developer ------------------------------------------------------------------------------ The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev_______________________________________________ Codenarc-developer mailing list Cod...@li... https://lists.sourceforge.net/lists/listinfo/codenarc-developer ForwardSourceID:NT000CE31E ForwardSourceID:NT000CE392 ForwardSourceID:NT000CE39E |
