Pair JIRA-configuring; I love it :) 1. Yes, comments are similarly blocked by 'regular users'. The way to think about the new 'Archived' security scheme is this: unless you are in the jira-developers group (which was designed to contain all committers across NH + all NHContrib projects), the NHLQ JIRA is 100% 'read-only'
2. Thanks for the second pair of eyes :) (fixed!) Steve Bohlen [email protected] http://blog.unhandled-exceptions.com http://twitter.com/sbohlen On Mon, Mar 21, 2011 at 9:16 AM, Patrick Earl <[email protected]> wrote: > Couple tiny things. > > 1. Does this also prevent comments from regular users? (I ask because > I'm hoping it does) > 2. You used NHQL in one place on the project description instead of NHLQ. > > Patrick Earl > > On Mon, Mar 21, 2011 at 6:47 AM, Stephen Bohlen <[email protected]> wrote: > > All: > > > > This task is now COMPLETED as follows: > > > > a new Permissions scheme called 'Archived' has been created with the > group > > 'jira-developers' replacing the permissions that were previously assigned > to > > the 'jira-users' group (this will, in effect, prevent anyone NOT an NH > dev > > from doing anything other than read-only under this permissions scheme) > > the 'Archived' Permission scheme has been applied to the NHLQ project > > the Description for the NHLQ project has been modified to reflect notice > > that the project is deprecated (http://216.121.112.228/browse/NHLQ) and > > where to go to report new issues for the NH LINQ provider if issues > persist > > after upgrading to NH3.x or later > > (http://216.121.112.228/browse/NH/component/10120) > > > > This *should* solve the issue of ppl reporting issues under NHLQ, but > since > > *most* ppl on this dev list are in the group 'jira-developers' most of us > > won't experience any change in perms when accessing JIRA. But this > should > > prevent any NEW issues from being reported there moving forward (unless > one > > of us want to report one just for fun). > > > > Let me know if there are any problems with these changes as you continue > to > > interact with JIRA. > > > > Thanks, > > > > Steve Bohlen > > [email protected] > > http://blog.unhandled-exceptions.com > > http://twitter.com/sbohlen > > > > > > On Sun, Mar 20, 2011 at 10:19 PM, Stephen Bohlen <[email protected]> > wrote: > >> > >> No, I'm behind in tasks for this weekend (which, sadly, is nearly at an > >> end <g>). I'm planning to make these edits first thing tomorrow > morning. I > >> will post a msg here once its complete just so that everyone can know > its > >> done. > >> > >> Steve Bohlen > >> [email protected] > >> http://blog.unhandled-exceptions.com > >> http://twitter.com/sbohlen > >> > >> > >> On Sun, Mar 20, 2011 at 10:14 PM, Patrick Earl <[email protected]> > wrote: > >>> > >>> Has this happened yet? I don't see any indication of this on JIRA, > >>> though I didn't actually push the "submit" button on the create issue > >>> page to see if there was an error. > >>> > >>> Patrick Earl > >>> > >>> On Wed, Mar 16, 2011 at 9:44 AM, Stephen Bohlen <[email protected]> > >>> wrote: > >>> > lol -- suppose I should read my OWN email :) > >>> > > >>> > Thanks~! :P > >>> > > >>> > Steve Bohlen > >>> > [email protected] > >>> > http://blog.unhandled-exceptions.com > >>> > http://twitter.com/sbohlen > >>> > > >>> > > >>> > On Wed, Mar 16, 2011 at 11:39 AM, Richard Brown (gmail) > >>> > <[email protected]> wrote: > >>> >> > >>> >> > ... but please let me know if anyone has any compelling reason > NOT > >>> >> > to > >>> >> > proceed ... > >>> >> > >>> >> +1 from me btw ... I only didn’t respond cos you asked if anyone > knew > >>> >> of a > >>> >> reason “not” to go ahead. > >>> >> > >>> >> > >>> >> > >>> >> From: Stephen Bohlen > >>> >> Sent: Wednesday, March 16, 2011 3:37 PM > >>> >> To: [email protected] > >>> >> Cc: Fabio Maulo > >>> >> Subject: Re: [nhibernate-development] Proposal: "ARCHIVE" NHLQ > project > >>> >> > >>> >> OK, its been several days and while we've not heard from EVERYONE on > >>> >> this, > >>> >> those that have provided input have agreed with this proposed > approach > >>> >> so > >>> >> this coming weekend I will proceed to make these changes as > described. > >>> >> > >>> >> Thanks everyone who weighed in. > >>> >> > >>> >> Steve Bohlen > >>> >> [email protected] > >>> >> http://blog.unhandled-exceptions.com > >>> >> http://twitter.com/sbohlen > >>> >> > >>> >> > >>> >> On Sat, Mar 12, 2011 at 8:14 AM, Fabio Maulo <[email protected]> > >>> >> wrote: > >>> >>> > >>> >>> agree. > >>> >>> > >>> >>> On Fri, Mar 11, 2011 at 8:36 PM, Stephen Bohlen <[email protected] > > > >>> >>> wrote: > >>> >>>> > >>> >>>> All: > >>> >>>> > >>> >>>> As a follow on to several of the suggestions over the months re: > how > >>> >>>> to > >>> >>>> avoid erroneous reporting of issues for the NHibernate LINQ > provider > >>> >>>> under > >>> >>>> the (deprecated) NHLQ project instead of under the LINQ component > >>> >>>> under NH, > >>> >>>> I am seriously considering 'archiving' the JIRA for NHLQ > >>> >>>> (effectively, > >>> >>>> changing its 'public' permissions to read-only as suggested here > >>> >>>> http://jira.atlassian.com/browse/JRA-13087 and elsewhere in > response > >>> >>>> to > >>> >>>> similar situations). Core committers would retain full edit perms > >>> >>>> under > >>> >>>> this approach, but everyone else would be reduced to read-only for > >>> >>>> the NHLQ > >>> >>>> area of JIRA. > >>> >>>> > >>> >>>> Since (nearly) all issues reported under NHLQ are being met with > >>> >>>> either > >>> >>>> "this is solved with the new LINQ provider in the core of NH3.x" > or > >>> >>>> "can you > >>> >>>> please re-post your issues under the LINQ component of the JIRA > for > >>> >>>> the core > >>> >>>> NH project?", this seems the simplest thing to do in order to > avoid > >>> >>>> any > >>> >>>> additional erroneous issue reporting under the 'wrong' JIRA > >>> >>>> project. The > >>> >>>> most recent issue opened under NHLQ > >>> >>>> (http://216.121.112.228/browse/NHLQ-99) > >>> >>>> probably also satisfies this same criteria. > >>> >>>> > >>> >>>> I can't see any reason anyone would object to this move, but > please > >>> >>>> let > >>> >>>> me know if anyone has any compelling reason NOT to proceed in this > >>> >>>> manner. > >>> >>>> Otherwise, I will proceed as outlined here early next week. > >>> >>>> > >>> >>>> Steve Bohlen > >>> >>>> [email protected] > >>> >>>> http://blog.unhandled-exceptions.com > >>> >>>> http://twitter.com/sbohlen > >>> >>> > >>> >>> > >>> >>> > >>> >>> -- > >>> >>> Fabio Maulo > >>> >>> > >>> >> > >>> > > >> > > > > >
