Release Notes for 4.5.1.000

[Juan Aguilar]

Did I miss the release notes for 4.5.1.000 or do I have to look through the commits with the 4.5.1.000 tag (https://bitbucket.org/lucee/lucee/commits/tag/4.5.1.000)?

Thanks.

[Andrew Dixon]

Micha posted information about the release here:

https://groups.google.com/forum/#!msg/lucee/OQOICdzNZyo/h2ESdEp3flQJ

Kind regards,

Andrew

http://about.me/andrew_dixon

On 11 February 2015 at 21:53, Juan Aguilar <jeag...@gmail.com> wrote:

Did I miss the release notes for 4.5.1.000 or do I have to look through the commits with the 4.5.1.000 tag (https://bitbucket.org/lucee/lucee/commits/tag/4.5.1.000)?

Thanks.

--
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+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/81be1451-a056-4e66-9d66-7e02ac54b085%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Juan Aguilar]

Ah. Thanks. I was searching for 4.5.1.000 and not for "New release". Growing pains, I guess.

Thanks again,

Juan

[AJ Mercer]

will release notes be put on bitbucket / wiki?

On 12 February 2015 at 05:53, Juan Aguilar <jeag...@gmail.com> wrote:

Did I miss the release notes for 4.5.1.000 or do I have to look through the commits with the 4.5.1.000 tag (https://bitbucket.org/lucee/lucee/commits/tag/4.5.1.000)?

Thanks.

--

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+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/81be1451-a056-4e66-9d66-7e02ac54b085%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

AJ Mercer
<webonix:net strength="Industrial" /> | <webonix:org community="Open" />
http://twitter.com/webonix

[Adam Cameron]

On Thursday, 12 February 2015 13:35:19 UTC+13, AJ Mercer wrote:

will release notes be put on bitbucket / wiki?

Indeed.

I'm not so familiar with BitBucket. If one was to look for release notes for a given release, would it be on this page:

https://bitbucket.org/lucee/lucee/commits/tag/4.5.1.000

(or equiv for the given version)

?

Is there scope there for any narrative notes where simply a summary of tickets fixed is not the complete detail for a release?

-- 

Adam

[Andrew Dixon]

I don't think BitBucket has that scope, it would need to linked into a proper bug tracker, e.g. JIRA, which of course as an open source project would be possible for free from Atlassian. The BitBucket built-in bug tracker is extremely limited because of course Atlassian want to sell people a JIRA licence!!!

Kind regards,

Andrew

http://about.me/andrew_dixon

--
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+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/0efd604e-6d18-49e7-9052-2aef2669652e%40googlegroups.com.

[Michael van Leest]

Why not add a releasenotes file to the root of the project and add the information of each fix/ticket to the file (like a lot of projects have)? 

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/CAG1WijUSL7wf1TnHp9pmPosxRq93EtJyX0GJ5gwz9jxKtGW3TA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--
Sent from Gmail Mobile

[Michael Offner]

We have a free license for jira and we plan to move to the full version asap, biggest problem for me is that you can not set "fixed version" with the current lite version, but I'm also thinking that is not accurate anyway, then that suggests that you know the next version...

I was also thinking to set a tag for every bug fix that is based on a ticket.

ATM we only have the link to a certain ticket in the commit message, but setting a tag for every issue fixed, would it make possible to read out the fixed by version dynamically via jgit.

Micha

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/CAG1WijUSL7wf1TnHp9pmPosxRq93EtJyX0GJ5gwz9jxKtGW3TA%40mail.gmail.com.