Learn More





DNN Community Blog

The Community Blog is a personal opinion of community members and by no means the official standpoint of DNN Corp or DNN Platform. This is a place to express personal thoughts about DNNPlatform, the community and its ecosystem. Do you have useful information that you would like to share with the DNN Community in a featured article or blog? If so, please contact .

The use of the Community Blog is covered by our Community Blog Guidelines - please read before commenting or posting.

DNN Nightly Builds

MoonThe DNN Platform team has been very busy lately.  Not only have we been working on the next DNN release, which is expected to be released later this month, but we have also been working on making our work more transparent.  With the recent move to GitHub it is now easier than ever to see what is being checked into the code.

Of course, having access to code is great if you are a developer, but if you’re not a developer then you probably don’t have access to the tools to compile and package a DNN release so you can test out the latest changes.  Recently, the platform team started making our latest builds available from our website on the Nightly Builds page.  Now everyone has access to the latest DNN builds so they can see what new features, enhancements and bug fixes are coming in the next release.  We plan to further enhance our nightly build page to provide full access to our nightly build archives beginning with 7.1.2.  This is a work in progress and we’ll let you know once the project is complete.

With the impending release of DNN 7.2.0, we also looked to update our naming standards for our build packages to conform with the new branding announced this past summer.  Beginning with 7.2.0, DNN packages will now use the following naming convention “DNN_Platform_{version}_{package type}.zip”.  If you have custom installation scripts or other automated processes that rely on the naming convention of our packages, then you should update those before the final release.  You can already see the new naming in place with our current nightly builds.


Daniel Gilleland
Awesome to see the new changes & switch to GitHub.

Any chance on a blog post expounding the intent on the various GitHub branches? Or at least some sort of summary to guide would-be contributors from the community?

For example:
- master - This branch is for commits accepted into the currently released version (e.g.: 07.01.03)
- development - This branch is for development work around minor versions and build versions of the current release (e.g.: 07.01.xx, or 07.02.xx)
- 72_release/72beta1 - This branch is for development on the next major or minor version to be coming out


In the short history of the DNN Platform on GitHub, I've seen some branches come and go (which can make upstream fetches a bit confusing). So I'm also wondering (just thinking out loud here) if a more standardized scheme for naming branches might be useful. How about this?

- master - This branch is for the currently released version (e.g. 07.01.03). The most recent tag is the last published version (07.01.03) while commits after that are slated for the next build release (07.01.xx)
- nextMinor - This branch is for accepted commits slated for the next minor release (07.xx.00)
- nextMajor - This branch is for accepted commits slated for the next major release (xx.00.00)

To make merging easier and handling of bug-fixes/community contributions more "atomic", contributors should make their own branches on their development machine and try to focus on a single issue/bug. Then they can do a merge back into their cloned copy of the appropriate branch (such as "nextMinor"), issue a pull-request, and (hopefully) simplify the work of those DNN employees who are managing merges/pull-requests on the official repo.

Just some thoughts.
Daniel Gilleland Saturday, November 09, 2013 12:29 PM (link)

Comment Form

Only registered users may post comments.


2sic Daniel Mettler (124)
Aderson Oliveira (15)
Alec Whittington (11)
Alex Shirley (10)
Andrew Nurse (30)
Anthony Glenwright (5)
Antonio Chagoury (28)
Ash Prasad (21)
Ben Schmidt (1)
Benjamin Hermann (25)
Benoit Sarton (9)
Beth Firebaugh (12)
Bill Walker (36)
Bob Kruger (5)
Brian Dukes (2)
Brice Snow (1)
Bruce Chapman (20)
Bryan Andrews (1)
cathal connolly (55)
Charles Nurse (163)
Chris Hammond (203)
Chris Paterra (55)
Clinton Patterson (28)
Cuong Dang (21)
Daniel Bartholomew (2)
Dave Buckner (2)
David Poindexter (3)
David Rodriguez (2)
Doug Howell (11)
Erik van Ballegoij (30)
Ernst Peter Tamminga (74)
Geoff Barlow (6)
Gifford Watkins (3)
Gilles Le Pigocher (3)
Ian Robinson (7)
Israel Martinez (17)
Jan Blomquist (2)
Jan Jonas (3)
Jaspreet Bhatia (1)
Jenni Merrifield (6)
Joe Brinkman (269)
John Mitchell (1)
Jon Henning (14)
Jonathan Sheely (4)
Jordan Coopersmith (1)
Joseph Craig (2)
Kan Ma (1)
Keivan Beigi (3)
Ken Grierson (10)
Kevin Schreiner (6)
Leigh Pointer (31)
Lorraine Young (60)
Malik Khan (1)
Matthias Schlomann (15)
Mauricio Márquez (5)
Michael Doxsey (7)
Michael Tobisch (3)
Michael Washington (202)
Mike Horton (19)
Mitchel Sellers (28)
Nathan Rover (3)
Navin V Nagiah (14)
Néstor Sánchez (31)
Nik Kalyani (14)
Peter Donker (52)
Philip Beadle (135)
Philipp Becker (4)
Richard Dumas (22)
Robert J Collins (5)
Roger Selwyn (8)
Ruben Lopez (1)
Ryan Martinez (1)
Salar Golestanian (4)
Sanjay Mehrotra (9)
Scott McCulloch (1)
Scott S (11)
Scott Wilkinson (3)
Scott Willhite (97)
Sebastian Leupold (80)
Shaun Walker (237)
Shawn Mehaffie (17)
Stefan Cullmann (12)
Stefan Kamphuis (12)
Steve Fabian (31)
Timo Breumelhof (24)
Tony Henrich (3)
Torsten Weggen (2)
Vicenç Masanas (27)
Vincent Nguyen (3)
Vitaly Kozadayev (6)
Will Morgenweck (37)
Will Strohl (163)
William Severance (5)
Try Evoq
For Free
Start Free Trial
a Demo
See Evoq Live
Need More Information?