This is probably obvious to Bitbucket aficionados, but what’s the right way
for me to view a changelog?
For instance, I’m on 4.5.1.000, and I want to see what’s changed between
that and the latest 4.5.1 patch release.
…and I just figured it out, so I’ll go ahead and answer my own question:
- Start here: Bitbucket
- In the select box under the “Commits” heading, choose the “Tags” tab,
and select the current patch release you’re interested in.
- Over on the right, next to the date column, there is a tag column
(mostly empty, but some rows/commits have entries like “4.5.1.020”).
Anything on that row, down to the the commit just above the next tag
marker, are part of that release.
Maybe I’ll throw that up on the wiki.
Thanks,
Jamie
And a more handy way:
I hadn’t yet used the (Railo or) Lucee automatic updater yet, but I’m
playing with it locally.
Most of you probably know this, but some might not:
- Server Admin (/lucee/admin/server.cfm)
- Properties: Update Provider: [I’m on 4.5.1.000,
and I want to see the release–4.5.1.022–that’s going to “stable” next
week, so I’m choosing “Development releases (Bleeding Edge)”]
- Click “Update” button. (This doesn’t execute the update yet, so don’t
worry.)
- A custom changelog is displayed in the “Info” area. (I say “custom”
because it shows you the changes, starting from your revision and ending
with the eligible revision.)
Example:
Info
A patch (4.5.1.022) is available for your current version (4.5.1.000).
Version 4.5.1.022
[ LDEV-78 ] ORM doesn’t persist data in cftransactions
Version 4.5.1.021
[ LDEV-384 ] Hanging requests if debugging is enabled / Locking in ArrayImpl
Version 4.5.1.020
[ LDEV-383 ] cfhttp fails
Version 4.5.1.019
[ LDEV-292 ] CFHTTP fails over SSL with SNI
Version 4.5.1.017
[ LDEV-376 ] writable CGI Scope
Version 4.5.1.016
[ LDEV-372 ] make CGI Scope writable
[ LDEV-354 ] IsEmpty(0) returns true
[ LDEV-353 ] NPE when using a struct as an exception
[ LDEV-348 ] Invalid Cookie name causes stacktrace and can bring down
lucee/tomcat
[ LDEV-322 ] If structKeyExists() works on an Exception, so should .keyExists()
[ LDEV-47 ] Support for (element in list)
Version 4.5.1.015
[ LDEV-327 ] add frontend for request Queue
[ LDEV-338 ] declared inline datasource does not work with ORM
[ LDEV-2 ] QueryExecute generates wrong entries in the debug information
Version 4.5.1.014
[ LDEV-327 ] add frontend for request Queue
Version 4.5.1.013
Version 4.5.1.012#331 https://bitbucket.org/lucee/lucee/issue/331
cached query not disconnect from life query#23
https://bitbucket.org/lucee/lucee/issue/23 queryExecute does not
support passing arguments scope as param structure#237
https://bitbucket.org/lucee/lucee/issue/237 application.cfc
this.tag.function.output=“false” default attribute value does not
work#319 https://bitbucket.org/lucee/lucee/issue/319 mail sending is
synchronized
Version 4.5.1.011#293 https://bitbucket.org/lucee/lucee/issue/293
Listener mode modern invokes Application.cfm files#292
https://bitbucket.org/lucee/lucee/issue/292 duplicate check in
duplication get not cleaned
Version 4.5.1.010#277 https://bitbucket.org/lucee/lucee/issue/277
Request timeout fails with Java8
Version 4.5.1.009#274 https://bitbucket.org/lucee/lucee/issue/274
ThreadQueue size is off
Version 4.5.1.008#210 https://bitbucket.org/lucee/lucee/issue/210
Duplicate encoding in soap webservice
Version 4.5.1.007#222 https://bitbucket.org/lucee/lucee/issue/222
Setting request timeout to 0 throws exception#216
https://bitbucket.org/lucee/lucee/issue/216 typo “succesful” when
verifying smtp server#215
https://bitbucket.org/lucee/lucee/issue/215 queryExecute allows
invalid parameter syntax without erroring#207
https://bitbucket.org/lucee/lucee/issue/207 Error in memcached cache
after migration from Railo#204
https://bitbucket.org/lucee/lucee/issue/204 Update CFHTTP multipart
response handling to support quoted boundaries#201
https://bitbucket.org/lucee/lucee/issue/201 Make Lucee compatible
with Railo extensions#189
https://bitbucket.org/lucee/lucee/issue/189 Extension license viewer
displays white text on white background, thus it never displays#178
https://bitbucket.org/lucee/lucee/issue/178 Multipart image byte
array response doesn’t handle quoted boundary
Version 4.5.1.006#188 https://bitbucket.org/lucee/lucee/issue/188
cfhttp empty csv fails#185
https://bitbucket.org/lucee/lucee/issue/185 The Layout CFC based
CustomTag still has references to the railo package
Version 4.5.1.005#180 https://bitbucket.org/lucee/lucee/issue/180
RequestTimeout cripples 3 party code
Version 4.5.1.004#164 https://bitbucket.org/lucee/lucee/issue/164
“!” in mail message
Version 4.5.1.003#150 https://bitbucket.org/lucee/lucee/issue/150
Error executing function tests as embedded Application.cfc was missing
TestBox archive#78 https://bitbucket.org/lucee/lucee/issue/78
Services - Update: Error “server http://dev.lucee.org failed to return
a valid response. The key [APIKEY] does not exist.”#103
https://bitbucket.org/lucee/lucee/issue/103 queryGetRow() function
and Query.getRow() method#145
https://bitbucket.org/lucee/lucee/issue/145 Lucee logo and
maximize/minimize button disappear with maximised#147
https://bitbucket.org/lucee/lucee/issue/147 structKeyExists return
true for “server.railo”#118
https://bitbucket.org/lucee/lucee/issue/118 toBinary should not
throw an error when 1st arg is an empty string#136
https://bitbucket.org/lucee/lucee/issue/136 Get off of Java 7#143
https://bitbucket.org/lucee/lucee/issue/143 testcases testbox
archive not works#139 https://bitbucket.org/lucee/lucee/issue/139
Admin page broken - Remote: Security Key#126
https://bitbucket.org/lucee/lucee/issue/126 actions without text are
not processed by cfhtmlhead and cfhtmlbody#125
https://bitbucket.org/lucee/lucee/issue/125 cfhtmlhead and
cfhtmlbody ignore the id attribute#3
https://bitbucket.org/lucee/lucee/issue/3 dateDiff() method
implemented incorrectly#79
https://bitbucket.org/lucee/lucee/issue/79 Axis info messages
shouldn’t be logged#4 https://bitbucket.org/lucee/lucee/issue/4
cfhtmlhead does not work#8 https://bitbucket.org/lucee/lucee/issue/8
getID() built-in function conflicting with component functions
Thanks,
JamieOn Wed, Jul 1, 2015 at 9:52 AM, Jamie Jackson <@Jamie_Jackson> wrote:
This is probably obvious to Bitbucket aficionados, but what’s the right
way for me to view a changelog?
For instance, I’m on 4.5.1.000, and I want to see what’s changed between
that and the latest 4.5.1 patch release.
…and I just figured it out, so I’ll go ahead and answer my own question:
- Start here: Bitbucket
- In the select box under the “Commits” heading, choose the “Tags”
tab, and select the current patch release you’re interested in.
- Over on the right, next to the date column, there is a tag column
(mostly empty, but some rows/commits have entries like “4.5.1.020”).
Anything on that row, down to the the commit just above the next tag
marker, are part of that release.
Maybe I’ll throw that up on the wiki.
Thanks,
Jamie
Useful Jamie, thanks.
The available tags for 4.5.1 only seem to go up to 4.5.1.020 though.
The most recent 4.5.1.022 isn’t there for some reason.On 1 July 2015 at 14:52, Jamie Jackson <@Jamie_Jackson> wrote:
I just figured it out, so I’ll go ahead and answer my own question:
It was released to the “dev” channel on Monday apparently.
https://groups.google.com/forum/#!topic/lucee/wYz1DCWLEWM
Micha was talking about “stable” releases I think, but it’d be useful
to see logs for all releases. Maybe a BitBucket quirk which will go
away when things move to GH.On 1 July 2015 at 15:13, Jamie Jackson <@Jamie_Jackson> wrote:
I think it’s because that release hasn’t dropped yet. I’ll bet that when it
becomes an official release (next week, said Micha), it will get tagged.
You can see what is in each release via JIRA:
https://luceeserver.atlassian.net/projects/LDEV?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page&status=all
Kind regards,
Andrew
about.me http://about.me/andrew_dixon - mso http://www.mso.net - Lucee
Association Member http://lucee.orgOn 1 July 2015 at 15:32, Julian Halliwell <@Julian_Halliwell> wrote:
It was released to the “dev” channel on Monday apparently.
Redirecting to Google Groups
Micha was talking about “stable” releases I think, but it’d be useful
to see logs for all releases. Maybe a BitBucket quirk which will go
away when things move to GH.
On 1 July 2015 at 15:13, Jamie Jackson <@Jamie_Jackson> wrote:
I think it’s because that release hasn’t dropped yet. I’ll bet that when
it
becomes an official release (next week, said Micha), it will get tagged.
–
You received this message because you are subscribed to the Google Groups
“Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/CAC_5Voo1x_k80K0EZrNkje-Gq1NtaUDDGo-e75oNL7n8q-OQ_g%40mail.gmail.com
.
For more options, visit https://groups.google.com/d/optout.