Changelog weirdness

[Jesse Glick]

Maybe I just don't understand how the release process works, but I think something is broken. changelog.html contains a section for 1.333, which has not been released
that I can see, and all of these entries are also contained under 1.332 (as well as a couple others, in a separate list). Meanwhile, there is a "trunk" section where I
would presume the 1.333 fixes ought to be.

Furthermore, it claims that #4760 was fixed in 1.332, which is not true - I just confirmed that both downloaded hudson.war (marked as 1.332 in its manifest) and the Maven
hudson-core-1.332-sources.jar lack the fix (@ExportedBean on RepositoryBrowser).


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[mindless]

weirdness this week probably caused because 1.332 was an out-of-cycle
release.
hopefully Kohsuke will clean up the duplicates and get items under the
right release before 1.333.

but in general, on wednesdays when trunk is copied to RC branch you'll
see that new section for the not-yet-released version be created.. any
changes going into trunk from that point will be in the following
release (e.g. 1.334 right now).

    - Alan


Jesse Glick wrote:

> Maybe I just don't understand how the release process works, but I
> think something is broken. changelog.html contains a section for
> 1.333, which has not been released that I can see, and all of these
> entries are also contained under 1.332 (as well as a couple others, in
> a separate list). Meanwhile, there is a "trunk" section where I would
> presume the 1.333 fixes ought to be.
>
> Furthermore, it claims that #4760 was fixed in 1.332, which is not
> true - I just confirmed that both downloaded hudson.war (marked as
> 1.332 in its manifest) and the Maven hudson-core-1.332-sources.jar
> lack the fix (@ExportedBean on RepositoryBrowser).
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Kohsuke Kawaguchi-2]

Jesse Glick wrote:
> Maybe I just don't understand how the release process works, but I think something is broken. changelog.html contains a section for 1.333, which has not been released
> that I can see, and all of these entries are also contained under 1.332 (as well as a couple others, in a separate list). Meanwhile, there is a "trunk" section where I
> would presume the 1.333 fixes ought to be.

I'm not exactly sure how a duplicate happened, but I removed them ---
1.332 should have just 3 fixes.

> Furthermore, it claims that #4760 was fixed in 1.332, which is not true - I just confirmed that both downloaded hudson.war (marked as 1.332 in its manifest) and the Maven
> hudson-core-1.332-sources.jar lack the fix (@ExportedBean on RepositoryBrowser).
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
Kohsuke Kawaguchi
Sun Microsystems                   http://weblogs.java.net/blog/kohsuke/