joomla-framework
joomla-framework copied to clipboard
joomla
Document release procedure
So what do we need to do for a release?
- Liaise with marketing for new major releases 4 weeks prior to release; 2 weeks prior to a minor release.
- Prepare JCM article if there is anything noteworthy to share with a little more detail.
- Tag the joomla-framework repository
- Run tagaliser to update release notes
- Run repo sub-split. Packagist.org will update automatically.
- Post announcement on www.joomla.org. See standard template below
- Tweet announcement from
@JoomlaFramework - Post announcement on framework mailing list http://groups.google.com/group/joomla-dev-framework
- Add link to Google+ community https://plus.google.com/communities/103500906097842801714
- Add link to Facebook page https://www.facebook.com/JoomlaFramework
Standard template for a release:
Joomla Framework X.Y.Z Released
Version X.Y.Z of the Joomla Framework has just been released. All packages have been updated and are available on Packagist.org. Here are some highlights:
- {add me}
The full release notes for this version can be found at https://github.com/joomla/joomla-framework/releases/tag/X.Y.Z
Thanks to everyone who helps make the Joomla Framework possible. If you are interested in finding out more about the Joomla Framework, please visit framework.joomla.org.
Liaise with marketing for new major releases 4 weeks prior to release. (Minor releases 2 weeks, Mainly so CMS users are not downloading the Framework) (Developers) Tag repository (Developers)Run tagaliser to update release notes (Developers)Run repo sub-split (Developers)Do release announce on www.joomla.org - what's the format going to be? (marketing) Communication announcement (as needed) Joomla.org auto tweets announcements (marketing) can schedule social @Joomlaplatform when and how JCM? Facebook Google+ Twitter
@eddieajau - I shared with you the doc we're working on for the 3.2.1 release, a much shorter and cleaned up version of the template we've been using for CMS releases. I imagine that could give a framework for what we'd like to cover and go from there. The announcement really doesn't need to be anything special, just enough to let folks know it's there.
For comparison, Symfony's last maintenance release announcement - http://symfony.com/blog/symfony-2-3-8-released
So can the actual release announce just be done with a cookie cutter:
Joomla Framework X.Y.Z Released
Version X.Y.Z of the Joomla Framework has just been released. All packages have been updated and are available on Packagist.org. Here are the highlights:
- {add me}
The full release notes for this version can be found at https://github.com/joomla/joomla-framework/releases/tag/X.Y.Z
Thanks to everyone who help make the Joomla Framework possible. If you are interested in finding out more about the Joomla Framework, please visit framework.joomla.org.
If we keep that short and sweet we can do "What's new in Joomla Framework X.Y.Z" in either the JCM or as a press release?
I'm fine with cookie cutter simple personally but would still suggest adding things like new packages or major changes when appropriate. Otherwise, that definitely gets to the point and prevents duplicated effort.
Edited the main issue to fill in the Facebook link and use the correct Twitter handle, otherwise looks good to me.
https://plus.google.com/communities/105495219615562222470 https://plus.google.com/109167715749846214365/posts Few more social accounts we can post to. Looks good
Rather than posting everywhere uniquely can we not just use dlvr.it and have it all automated?
Depends on the strategy behind it. We do have separate twitter handles, Facebook pages, subdomains, anaylitcs and more. G+ is also offically verified already. We need set up additional metrics to see what impact our social accounts are making. We can also ask for volunteers to help with the framework accounts, and provide them a strategy & guidelines.
j.org social media is reliable only if it's automated or specifically requested.
