1301510 - Release JSS 4.3.3

Status: RESOLVED WONTFIX

(JSS Graveyard :: Library, defect)

Description

[Elio Maldonado]

This bug proposes the release of JSS 4.3.3

Comment 1

[Elio Maldonado]

Attachment: update JSS_PATCH_VERSION to 3

Update JSS_PATCH_VERSION to 3 for the JSS-4.3.3 release.

Comment 2

[Elio Maldonado]

Since we may not have the automated JSS tests enabled until next week, would it be better to do a tag to JSS_4_3_3_RC0 instead?

Comment 3

[Elio Maldonado]

(In reply to Elio Maldonado from comment #2)
> Since we may not have the automated JSS tests enabled until next week, would
> it be better to do a tag to JSS_4_3_3_RC0 instead?

Answer to my own question. After a bit of research I learned the proper way to update version numbers for JSS which is similar to what is done in NSS.  We can indeed do a tag for JSS 4.3.3 beta candidate just as is done with NSS and after discussing with Christina it's the proper thing to do. The patch I submitted is incomplete revised patch coming next.

Comment 4

[Elio Maldonado]

Attachment: JSS_PATCH_VERSION to 3 - V2

Includes additional files that were missed in the previous version.

Comment 5

[Elio Maldonado]

Attachment: JSS_PATCH_VERSION to 3 - V2

The version I intended to attach

Comment 6

[u289492]

Comment on attachment 8789882 [details] [diff] [review]
JSS_PATCH_VERSION to 3 - V2

I think it looks fine.  I do not have experience with upstream versioning practice, so I suggest additional reviewer(s).

Comment 7

[u289492]

just want to add that specifically, I'm wondering when to up the major version, minor version, or patch version.  Any definition on the practice?

Comment 8

[Elio Maldonado]

(In reply to Christina Fu from comment #7)
> just want to add that specifically, I'm wondering when to up the major
> version, minor version, or patch version.  Any definition on the practice?

major, minor, and patch versions are for major, minor, and patch releases, respectively. We haven't any major release in in many years and don't expect one any time soon. In a major release backawards compatibilty is not guaranteed. We normally do minor and patch releases. In a minor release ABI compaitluity is respected but we can introoduce to APIs. The promise is that as long as client code doesn't use the new API's it contunies to work without having to recompile or to link. I patch release on the other consists of bug fixes only and no new API are are supposed to be introduced. I know this is documented somewhere and I am looking for it.

Comment 9

[Matthew Harmsen]

Patch looks fine to me.

Questioned '#define JSS_BETA     PR_TRUE', but found out that this first release was slated to be a Beta.

Comment 10

[Elio Maldonado]

Upon consultation it was agreed that that its' best to instead release jss 4.4.0 once all downstream patches from fedora and rhel have been integrated upstream and properly tested upstream.

Comment 11

[Elio Maldonado]

Closing this bug as Bug 1322364 replaces it.