GitHub Changes and New Testing Option Available

[Michael Babker]

Hello,

Following up on our previously announced changes to our GitHub workflow, we have some exciting news to share.

First, effective now, we have changed to using the staging branch in place of master for 3.x.  New pull requests will by default go to staging, and commits from the maintainers will be pushed to staging.  Merges to master will be performed by our CI server so long as our automated test suite is passing.  Note this only affects the 3.x series, 2.5 continues to have its single branch.

Starting with the development for our next releases, the version number will be appended with a -dev string, so 3.2.2-dev reflects the current git branch for staging.  This is done to reflect the development status more accurately.

Next, we have gone back to using dated SQL deltas for any database schema changes made between releases.  We hope this will help lower the number of conflicts occurring with schema changes, especially surrounding a minor release where there are many features constantly changing the previous single file.  The date on these files should be the date committed to the repository.  So 3.2.2-2013-12-19.sql matches the current 3.2.2-dev (GitHub staging branch) schema.  If a database change is committed on January 15 of next year, the schema will increment to 3.2.2-2014-01-15.sql.  This should also help updating sites between pre-release versions as well.

For those who are not already tracking, we have been posting nightly packages at http://developer.joomla.org/cms-packages/ to test the latest and greatest with.  Before tonight, this only covered 3.x.  We have added 2.5 into this as well.

And lastly, we have made it so that testing updates to the next version can be performed at any time.  Using the nightly packages, we will provision the update component's "Testing" update server option so that it will offer the nightly downloads at any time except for when beta or release candidate packages are published near the beginning of our release phase.

[Chad Windnagle]

Wow! That's a lot of cool automation going on. Great work! 

Regards,
Chad Windnagle

--
You received this message because you are subscribed to the Google Groups "Joomla! CMS Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-cm...@googlegroups.com.
To post to this group, send an email to joomla-...@googlegroups.com.
Visit this group at http://groups.google.com/group/joomla-dev-cms.
For more options, visit https://groups.google.com/groups/opt_out.

[brian teeman]

Will this be posted here (http://developer.joomla.org/news.html) as well? Hope so.

[Vic Drover]

Well done to everyone involved! Sounds great.

--

Cheers,

Victor Drover
Founder and CEO, Anything Digital LLC (BBB Accredited)
Co-founder, Watchful.li & jInbound.com
262-309-4140
Facebook: AnythingDigital | watchfulli | JInbound
Twitter: @AnythingDig | @watchfulli | @JoomlaInbound

[Michael Babker]

Hadn't thought of it before, but consider it done now.  http://developer.joomla.org/news/576-changes-to-cms-github-repository-and-update-testing.html

[brian teeman]

Thanks Michael. I know it's confusing sometimes with so many communication channels knowing where to post information.

[brian teeman]

Kevin brought up an interesting question on the forum. What happens we have both RC and Nightly at the same time? Will it still work?

That's a good point Kevin. I didn't quite get your comment at first as my immediate response was yes of course but now I get it (I think). As both nightly and rc are on the same update channel then there will be a period of time, once an rc, is released that we will have both available. I am not sure how the system will work once we have both an rc and later nightly releases in the same stream.

One option would be to use the testing server for nightly builds and the custom server for rc builds UNTIL we can update joomla to add an RC option to the update component as well as the current testing option.

Hope I understood his concern correctly

[Bakual]

It should work going from Nightly (dev) to RC. But it will likely not show a newer dev version once you have the RC installed as the RC is considered the higher version.

[Michael Babker]

During the RC period, the Testing channel will point to the RC release unless we come up with another solution, as is being thought out I guess by this post.  The nightly build will still be published, but won't be utilized by the update server.

If we add an additional option, I'm not quite sure what we should call it.  I kind of see where this is going though (having not logged into the forums yet).  Testing could always be the nightly package then we have something like pre-release or something for official beta/RC releases.

[brian teeman]

On Friday, 20 December 2013 18:11:04 UTC, Michael Babker wrote:

If we add an additional option, I'm not quite sure what we should call it.  

I would propose changing the name of the  channel and adding a new one

Testing (nightly)

Testing (releases)

Releases => alpha, beta, rc1, rc2 etc

 

[Robert Vining]

I would probably go with 

Testing

and 

Nightly Build

as the options

[LyriC JoomliC]

Hi all!

Really exciting!

As a newbie (extension developper on JED since a little more than one year), i want to contribute, by testing, and by helping as far as i can to the Joomla! developpement, and really, after being myself lost in all the recently topics, i'm now happy to see how the community is able to keep a group entity!

Thank you !

For sure, 2014 will be a great year!
Merry Christmas and Happy New Year!

Greetings from France
Cyril Rezé