-
1. Re: Mark old releases in RFPL Jira as released
Hi Pavol,
I pretty much used RFPL exculsively for tracking RichFaces releases via
the release jira issue we create for each issue. When the release is
complete there are oftentimes QE related issues in the release that
prevent me from closing the RFPL version. When those issues are
resolved I do not come back to the RFPL version to close it.
Since your team makes much heavier use of the RFPL jira project for QE
purposes, I suggest you request administrative access to the RFPL
project so you can open/close issues as appropriate. Does this sound
reasonable?
Cheers,
Brian
On Fri 17 Jan 2014 05:33:26 AM PST, Pavol Pitoňák wrote:
Hi,
I noticed that several old releases are still marked as unreleased in RFPL:
4.2.4
4.2.5
4.3.3
4.3.4
Regards,
Pavol
_______________________________________________
richfaces-dev mailing list
_______________________________________________
richfaces-dev mailing list
https://lists.jboss.org/mailman/listinfo/richfaces-dev
-
2. Re: Mark old releases in RFPL Jira as released
Hi,
yes, it makes sense for me to "release" RFPL versions. It seems that I already have administrative access to the RFPL.
Versions 4.2.4 and 4.2.5 never existed. There were nine issue fixed in 4.2.4 (fixed also in 4.3.0.x) and no issues in 4.2.5. What would be the best to do with these two versions? Options are to leave it unreleased (I vote against it), mark it released (doesn't make sense), archive it (might work for 4.2.4) or delete it (might work for 4.2.5).
I released 4.3.3 and 4.3.4 in Jira.
Regards,
Pavol
-
Original Message -
Hi Pavol,
I pretty much used RFPL exculsively for tracking RichFaces releases via
the release jira issue we create for each issue. When the release is
complete there are oftentimes QE related issues in the release that
prevent me from closing the RFPL version. When those issues are
resolved I do not come back to the RFPL version to close it.
Since your team makes much heavier use of the RFPL jira project for QE
purposes, I suggest you request administrative access to the RFPL
project so you can open/close issues as appropriate. Does this sound
reasonable?
Cheers,
Brian
On Fri 17 Jan 2014 05:33:26 AM PST, Pavol Pitoňák wrote:
Hi,
I noticed that several old releases are still marked as unreleased in RFPL:
4.2.4
4.2.5
4.3.3
4.3.4
Regards,
Pavol
_______________________________________________
richfaces-dev mailing list
_______________________________________________
richfaces-dev mailing list
https://lists.jboss.org/mailman/listinfo/richfaces-dev